I know most of you don't care about my alpine fetish, but this goes out to my fellow alpine users :-)

Pine was almost dead for years and likely because of that I never reconsidered optimising my mail-usage. With alpine's rebirth I have been busy improving my daily overload of personal messages.

As a fervent user of tabs in my browser, this article caught my attention. It explains in great detail all the different changes and improvements to Firefox that affect its memory usage.

At some point you start to wonder how it could have gotten this worse, but it usually takes a big swing in one direction to get corrective actions and a joint focus on what was neglected.

RHEL 5.2 beta is released and many interesting features and software updates are expected.

It is very unusual for software to be updated (instead of bugfix backports) in a Red Hat Enterprise distribution (or CentOS for that matter) but there are exceptional cases where this makes more sense than the alternative.

Red Hat has decided that for desktop applications they can make that exception, meaning Red Hat and CentOS desktop users (me!) will soon be able to use a recent Firefox, Thunderbird or OpenOffice.

Since 10 years I am praying for a much more convenient email program, one that understands my relation with incoming mail and incoming folders. Let me explain...

I get lots of mails from different sources. Some are addressing me, others have me in Cc:. Some are from mailinglist that are very important to me (because I am responsible for answering), others I just want to follow up if I have some time. My email-client however treats all these mails the same way.

The CentOS project is looking for more slogans that may end up on promotional material (eg media, flyers, posters or stickers). We already collected a few funny, ironic, sarcastic or even distasteful ones.

Feel free to visit our Slogans wiki page for a good laugh or rude offenses and add your own slogan by sending them to this thread.

It is a common problem with packagers. Developers release a package 0.4, then release a 0.5a (or 0.5pre1 or 0.5rc1) and then release the stable 0.5. Of course, when packaging you have to foresee such problems and maintain a proper upgrade path from 0.4 to 0.5pre1 to 0.5rc1 and to 0.5. Often that means finding the meaning of a release string.

Since I started contract work for a new customer and have been offered a Windows Thinkpad to connect to the internal network, I have been looking at ways to make my life more comfortable. Putty is now my window to the world work so let's look at how I can make Putty nicer to work with.

PS: Some of these options work equally well for Putty on Linux, put there is little use for that combination.

...with love.

Would it be too much to ask if new Drupal releases could be announced on Freshmeat ? The current Drupal Freshmeat-record is out of date (last updated 3 may 2006) and still refers to 4.7.0.

Having a seperate branch for both the 4.7.x and 5.x stable releases as well as the 6.x development releases would be great. Links to release notes and downloads would be superb ! And a short description of the changes gain you additional karma points.

LinuxWorld Expo Brussels this year will take place on wednesday 19 and thursday 20 March 2008 in Brussels Kart Expo. Last year's edition was lacking any Open Source cooperation and this year the organisers acknowledged the benefit of an Open Source pavilion on the LinuxWorld exhibition.

Having this Open Source pavilion allows us (the Open Source community) to showcase some technologies and communities on an exhibition floor that is primarily dominated by sales and marketing people and that is aiming towards the business world.

Today I experienced a problem with Drupal's one time URL behaviour when resetting your password. I am a fan of the way Drupal does this, which I think is much better than most sites are handling password resets.

However in this particular case Drupal's solution failed to work. What happens is that the transparent proxy is making a connection to the URL (that I got by mail) and then does a second request that is actually going back to the browser. In a log, it looks like this: