As promised here is the patch for 2.6.24-rc1. It should also work with rc2 but I haven't tested it myself yet. Debugging also changed. I now use pr_debug for output. This means you need to compile the modules with "-DDEBUG" to get the debug output.

NB: As always, this code works for me, if you find any bugs or have fixes please contact me.

Ok, after finding out rather late that the rtsp patch did not work with 2.6.22, I downloaded 2.6.23-rc2 and ported it yet again. As always you can find the code here. I really hope that this patch will survive 2.6.23-final.

NB: As always, this code works for me, if you find any bugs or have fixes please contact me.

Since some changes happened to the netfilter code in 2.6.22 a new version of the rtsp patch is online. Big thanks go out to Jan Engeldhardt who really helped me getting this patch done in such a short time.

The location of the patch is still the same so go and grab it.

NB: As always, this code works for me, if you find any bugs or have fixes please contact me.

Since I always hated my CGI set-up here I took the plunge and tried to get pyblosxom running with WSGI. This is more or less a short HOWTO that shows how I did it. I am not sure if this is the best way to do it but it works for me.

Requirements:

  • WSGI

    This comes bundled with the latest python releases, if yours is older the easiest solution is to use easy_install. Just download and install it if you haven't done yet and then call

easy_install wsgiref

Setup:

Put mp_wsgi_handler.py, wsgi_app.py and your config.py in the same directory. Follow the directions in the wsgi_app.py file and put the <Location> entries in your httpd.conf file. Here it is once more. Do not forget to change PythonPath so all the required files are found.

<Location /weblog>
      PythonDebug Off
      SetHandler python-program
      # set PythonPath to the folders containing the files.
      PythonPath "['/path/to/mp_wsgi_handler', '/path/to/wsgi_app']+sys.path"
      PythonHandler mp_wsgi_handler::wsgi_handler
      # This should be the same as the Location above
      PythonOption ApplicationPath /weblog
      PythonOption application wsgi_app::application
</Location>

That's it you can now access your blog on your server via /weblog. But what if you do not want to use http://<servername>/weblog everytime?

I wanted to do exactly that. My first try was to change

<Location /weblog>

to

<Location />

This more or less worked, but since mod_python now took all requests I was not able to serve static files. I reverted the change and added some .htaccess entries instead.

.htaccess:

RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d [OR]
RewriteCond %{REQUEST_URI} ^/$
RewriteRule ^(?!weblog)(.*)$ /weblog/$1 [QSA,L]

So what are these entries doing?

If the request is not an existing file or directory

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d [OR]

OR it is the base url

RewriteCond %{REQUEST_URI} ^/$

rewrite it to /weblog but only if it isn't already /weblog

RewriteRule ^(?!weblog)(.*)$ /weblog/$1 [QSA,L]

Difficult yes, working yes, solveable in a better way maybe but I do not know how. :)

If you have any questions or comments do not hesitate to ask me.

An update to this site is really needed but in the mean time I proudly present my stab at linux kernel hacking. I ported the rtsp conntrack module to the new 2.6.20 netfilter API. I mostly did it because I need it to watch the Apple screencasts that appear every now and then.

So without much further ado I present the patch for the latest kernel releases.

NB: This code works for me, it might open a huge security hole on your firewall or kill your cat.

So Apple unveiled their new line of intel based computers and the world took a deep breath and said ahhhhh and ohhhhhh. In February their new Macbooks are available and support for ProApps will follow in March. Life is good, life is well people are tempted to say now but I beg to differ. There are several reasons why I think Apple should get their act together.

  • Quicktime

    Hey guys what is wrong with QT7. Apart from not being very stable it is sheer luck if streaming is working.

    • Dialup

      I am one of the two guys in Europe that still uses dialup to connect to the WWW. Streaming with quicktime? HAH. Despite the fact that Quicktime allows to select 56kbit upload speed, playing movies via the internet is not working at all. You either get no sound are the picture is missing, you really have to be luck to get a stream working at all.

    • Stability

      Version 7 really is not stable at all. Random freezes dodgy playback and discussion lists full with user questions/problems.

  • ProApps

    Don't get me started. Every release seems to be a russian roulette where you don't know if your Application will work or not. Since I use the software just for fun and do not earn money with it, I don't really care but others get into serious trouble because of this problems.

I do not want to bash Apple at all, but right now it looks like that they have shifted its focus. They are more interested in selling ther iPods and other consumer equipments than releasing proper sofware. A few years ago you could always say "Hey, use the ProApps, they are stable and QA is done for every release". Now I would tell them to wait after a patch has been released, read through the discussion list, wait some more, do a backup, install the update and pray. The problem is that a Version that was working prefectly could get completely screwed up with the next update.

So please wake up Apple, get your act together and fix those bugs.

Life has made several turns in the last few weeks and I am not in the mood to write about it ....yet. Nonetheless I still feel the urge to keep you, the reading protagonist, up to date.

Currently I am muddling around with a cunning idea to have a vent for my bogged down mind. I am still in the planning stage but a rough plan has already been plotted out in my mind. The idea is quite simple, I'll just try to write a page per week or even more easier, I'll try to write at least once a week not counting the words sentences or thoughts. The question that is still open, will it be a journal or a story. Well, I am a lousy journal writer as you have been seen but writing stories....... we will see.

Why I want to do this? Quite simple I don't want to get a work induced, thought related, personal meltdown. Writing should help me keep my mind in a pattern that's more or less structured. I know that this will not stop my now frequent brain farts but at least it should provide an entertaining read for you.

Since this "project" should help me think in a more structured way it will also be necessary to follow some predefined, simple rules. As soon as I have a clear understanding of what they should be, I'll post them here.

I recently played around with the folksonomy plugin just to notice that it does not really like the $relatedstories and $relatedtags variables. Digging around in the code I saw that something fishy was happening with the way the folksonomy table got created. I tried to understand what happened there exactly but failed miserably. But yesterday I had an aha moment. Martin really, really helped my figuring out

  • What the code is supposed to create
  • Why I did not work as expected
  • Rewrite it in a way that it actually works

So after some hacking we got it working again. Without further ado take a look at the entries and phear the power of related stories.

I stil need to find a nicer CSS layout but hey I still have a few days of my holidays left to fix it.

So I did what a had to do and revived my 3 year old pyblosxom layout. After some fiddling around with some div's I think it is ready to be looked at. What do you think? This is the first day of my holidays so expect more to come, or not.