I ve been investigating the Ext4 filesystem [1]. The main factor that is driving me to Ext4 at the moment is fsck times. I have some systems running Ext3 on large filesystems which I need to extend. In most cases Ext3 filesystems have large numbers of Inodes free because the relationship between the number of Inodes and the filesystem size is set when it is created, enlarging the filesystem increases the number of Inodes and apart from backup/format/restore there is no way of changing this. Some of the filesystems I manage can t be converted because the backup/restore time would involve an unreasonable amount of downtime. Page 11 of the OLS paper by Avantika Mathur et al [2] has a graph of the relationship between the number of Inodes and fsck time. Ext4 also has a number of other features to improve performance, including changes to journaling and block allocation. Now my most important systems are all virtualised. I am using Debian/Lenny and RHEL5 for the Dom0s. Red Hat might back-port Ext4 to the RHEL5 kernel, but there will probably never be a supported kernel for Debian/Lenny with Ext4 and Xen Dom0 support (there may never be a kernel for any Debian release with such support). So this means that in a few months time I will be running some DomUs which have filesystems that can t be mounted in the Dom0. This isn t a problem when everything works well. But when things go wrong it s really convenient to be able to amount a filesystem in the Dom0 to fix things, this option will disappear for some of my systems, so if virtual machine A has a problem then I will have to mount it s filesystems with virtual machine B to fix it. Of course this is a strong incentive to use multiple block devices for the virtual machine so that a small root filesystem can be run with Ext3 and the rest can be Ext4. At the moment only Debian/Unstable and Fedora have support for Ext4 so this isn t a real issue. But Debian/Squeeze will release with Ext4 support and I expect that RHEL6 will also have it. When those releases happen I will be upgrading my virtual machines and will have these support issues. It s a pity that Red Hat never supported XFS, I could have solved some of these problems years ago if XFS was available. Now for non-virtual machines one factor to consider is that the legacy version of GRUB doesn t support Ext4, I discovered this after I used tune2fs to convert all filesystems on my EeePC to Ext4. I think I could have undone that tune2fs option but instead decided to upgrade to the new version of GRUB and copy the kernel and initramfs to a USB device in case it didn t boot. It turns out that the new version of GRUB seems to work well for booting from Ext4. One thing that is not explicitly mentioned in the howto is that the fsck pass needed to convert to Ext4 will not be done automatically by most distributions. So when I converted my EeePC I had to use sulogin to manually fsck the filesystems. This isn t a problem with a laptop, but could be a problem with a co-located server system. For the long term BTRFS may be a better option, I plan to test it on /home on my EeePC. But I will give Ext4 some more testing first. In any case the Ext3 filesystems on big servers are not going to go away in a hurry.

• [1] http://ext4.wiki.kernel.org/index.php/Ext4_Howto
• [2] http://ols.108.redhat.com/2007/Reprints/mathur-Reprint.pdf

It took some time since last Photo uploader release, but it's not dead an now comes new release. It mostly just fixes imageshack interaction and moves development to Git on Gitorious. News in this release:

• Fixed grabbing URL from imageshack.
• Fixed defaults to not open browser.
• Default to imageshack.us service.

In September, the Debian GRUB maintainers took a step further in the long way of deprecating grub in favour of grub2. From my personal point of view, grub2 is not the way to go. Mostly because of these reasons:

• I don't have systems using a non-ext 3,4 filesystems.
• I don't have use for any of the grub2 advanced features.
• I don't want to wait another few seconds until grub2 has been loaded.
• I don't want to learn yet another theme-ing mechanism for bootloader splashes and menu structures.
• I don't want to use a different bootloader project, regardless from which media I boot (iso, usb-hdd, netboot).

Back in Juli, when I was listening to the talk of Giacomo Catenazzi at DebConf 9 about bootloaders in Debian (high (618MB), low (110MB)), I was reminded that I really should getting EXTLINUX splittet out of Debians syslinux packaging and made available as an alternative bootloader within Debian. Last week I hacked together an initial working version and uploaded it to experimental. Note that the two comands extlinux-install and update-extlinux do not have all the safety belts yet, the theme-ing mechanisms are not integrated yet (I'll upload a syslinux-themes-debian soon), and that the layout of the generation of the config files in /boot/extlinux may could change (debian-wise, not upstream-wise). For me, it works already well though, I'm using it on my main desktop and notebook. If you want to help finding bugs or submitting wishlist bugs for additional stuff to be added, and recovering from an unbootable system is not a problem for you, you're welcome to try it out:

	# apt-get install -t experimental extlinux syslinux-common
	# sed -i -e 's ^postinst_hook =.*$ postinst_hook = update-extlinux ' \
		-e 's ^postrm_hook =.*$ postrm_hook = update-extlinux ' \
		/etc/kernel-img.conf
	# mkdir -p /boot/extlinux
	# update-extlinux
	# extlinux-install DEVICE

Update: Rather than having /etc/kernel-img.conf modified by users, bootloader packages should add symlinks to their update scripts to /etc/kernel/postinst.d and /etc/kernel/postrm.d. Uploaded new version to experimental. Thanks maks for mentioning it.

savs seemed to agonise about posting it but I think his Top 10 crimes of Developer Engagement is spot on even if it might not be as amusing as Aral Balkan s similar message. I think it applies to my recent RFID development work too: the public information is fluffy and you have to hunt or reverse-engineer most of the technical info, the supplier websites are painful and there s almost no interaction. In the past, I d been factoring in something between 50 and 100% extra time when our co-op needed to coordinate with unknown non-co-ops. With RFID hardware work, it was well over 300% when I last calculated it and that s even though there was one pretty helpful RFID supplier. This sort of nonsense is painful, slows development massively, could kill useful technologies at birth and re-emphasises my commitment to use Open Standards as much as reasonable. Have other people got similar horror stories to share? Can we get savs s Top 10 Crimes under the noses of some high-profile people?

Now that I'm not letting the cat out of the bag (I bought these as gifts) I can write a review. The use case was pretty simple: I thought it'd be a cool Christmas present for our parents to give them something Internet-enabled that would give them regular updates on their grandchild (when he/she arrives). I was thinking a picture a day type of thing. So I hunted around for a WiFi-enabled digital picture frame, and found the iGala being sold pretty much exclusively by ThinkGeek. The reviews seemed pretty good. I know WiFi-capable frames have been around for a few years, but they always seemed to be pretty lacking in terms of WiFi functionality. Like they wouldn't do any security, or they'd only do WEP. This particular product claimed to do the whole gamut, including WPA2. The fact that it was a touch screen and ran Linux also made it appealing. So I ordered a couple of them for a few weeks before we headed to Australia, with the intention of making sure that they'd work. Here's the highlights. WPA2 didn't work (nor did WPA) Despite the software on the frames claiming to be able to talk WPA2, the frame would not associate with my Linksys WRTU54G-TM. I had to drop it all the way back to WEP to get it to connect. For me, this was the most disappointing failure. I bought the product specifically on the strength of its claim that it supported WPA2, and it just didn't work. It was also pretty impossible to debug the failure. I downloaded the latest firmware update, and that added additional settings for TKIP or AES when selecting WPA2, but neither option helped. The automatic updates are brain-dead Speaking of downloading firmware updates, the latest firmware that I downloaded and installed on the frames added automatic over-the-air firmware updates. Nice enough feature, except for the implementation. The frame tried to make an HTTP GET request for a non-existent file, every 6 seconds. So the frequency of checking alone is totally ridiculous, but couple with this the fact that it's making a GET request (this is what $DEITY invented the HEAD request for, people!) and the website has a "friendly" 404 Not Found page that weighs in at a little over 10 Kb. By my calculations, that's nearly 150 Mb of failed update checking traffic a day. Taking these frames to a backward country like Australia, where ISP users still have monthly quotas, gives the frame a pretty horrendous running cost in terms of traffic. Not to mention the outbound bandwidth requirements for the server hosting the updates. Crikey, the mind boggles. I'd have thought checking once a day and on power on would be perfectly sufficient. Transitions are unavoidable It may be just me, but I hate cheezy transitions. Digital picture frames tend to come with a myriad of them, but they all look cheap. It's impossible to tell the frame to just change the picture, it has to use at least one transition effect all the time. It defaults to randomly choosing from all the available ones. At least you can tone it down to just one. Automatic on/off time I liked that it was possible to configure operating times. No need to have the thing chewing power 24x7. It just seems to turn off the backlight outside of the programmed operating hours, so it's still doing the lame uber-frequent and bandwidth-intensive checking for updates even when it's "off". Photo check frequency is configurable Another nice feature was the ability to check for new photos at varying intervals. What I wanted for my parents was to just update once a day, so they'd get a new photo every day (assuming we put a new one in the Picasa web album that it's checking). This was very doable, and coupled with the automatic on/off time, means they should wake up to a new photo every day (that we change it). Built in photos are a bit too sticky There's 3 or 4 in-built photos as part of the firmware. If there's nothing accessible or available online, it'll cycle through these. Somewhat annoyingly, you need to have at least two photos in your online source for it to stop wanting to incorporate the stock photos in the mix. The workaround is to put the same photo in the online album twice, so you don't realise it's switching between two images. Lame, but it works... Touch screen UI was adequate Given the alternative user interface for digital picture frames is a little IR remote control and some dinky menus, the iGala was nice to configure. A full on-screen QWERTY keyboard pops up for entering WEP/WPA/WPA2 keys and configuring the Picasa/Flickr connections. Fairly responsive support The main near-showstopper for me was the lack of advertised WPA2 support. I emailed the Aequitech support folks quite a bit during my "evaluation" period. They got back to me fairly quickly most of the time and wanted to know exact details of my setup so they could reproduce it in the lab. They'd be well served having an actual ticketing system, instead of hiding behind an email address, as it made it hard to keep track of the multiple issues I was raising with them. It's written in Lua?! I have no familiarity with Lua, other than I know of its existence as a programming language. I'm curious as to what their motivation was for this language choice. All of the Lua code shipped in the complete firmware refresh ZIP files is bytecode. I have no idea if it's possible to decompile it. The CPU architecture would appear to be a Blackfin based on the few compiled binaries included in the full firmware. Easy to update Prior to the new update "functionality" I've already railed against, it was pretty easy to update. Download a ZIP file and a shell script, put them in the root directory of a USB key, and plug it into the frame and stand back. The updates don't seem to cryptographically verified (even the over-the-air ones), so I wonder if it's possible to break into the frame by way of a cleverly crafted "update". I have no idea what breaking into the frame would buy you. I don't know what sort of computing power they have. Conclusion I still think the iGala is a reasonable, if somewhat immature product. If the software is going to be actively worked on, and the support people continue to be responsive, then I think it's got good potential. For the price, I expected a more polished product, though. I received an email from their support people shortly after returning from Australia saying that they'd fixed the WPA2 problem. Unfortunately I had no intention of trying to remotely talk my parents through how to reconfigure their access point or the frame (interestingly WPA2 didn't work with their Linksys WAG54G2 either, so I'd love to know what WPA2 devices it was tested with), so it's 128-bit WEP until I next go to Australia.

This weekend while I was on Guatemala just a few hours before to give a talk, my acer one decided to suddenly shut down, I tried to started again, remove the battery, plug the charger, etc, I actually even tried to boot it with some liv-usb distro, but the netbook keep shutting down a few seconds after boot I m still not sure what happend to the computer, it could be the motherboard or the HDD, I still have to check if it can be fixed Sadly, this was my main computer, I always used for almost everything, even for task when building a package tooked 50 minutes :p, but I m lucky since I did not loose any senssitive data (in case the problem is the HDD), and I still have other computers where I can work, but I still need to get used to a bigger screen/keyboard.

Just got back from Tokyo a few hours ago: I had an opportunity to give my 'Introduction to High-Performance Computing with R' tutorial / lectures (for which previous slides can be found here). This was an all-day talk at the Institute for Statistical Mathematics at their new site in Tachikawa in the greater Tokyo area, thanks to an invitation by Junji Nakano. Lisa and I turned this into a brief one-week trip to Kyoto and Tokyo, and we had a truly wonderful time on what was our first visit to Japan. I should blog some more about it, but now I will give in to the jet lag and catch up on some sleep...

Yesterday, we managed to inspect the property that was for sale that we'd discovered. I think you could best describe it as a renovator's delight that's had a bit of work done on it. The kitchen is pretty new. The bathrooms are pretty good. There's some cracking around the place, and the floating floor looks like it's a bit of a dodgy job. That said, it definitely had potential, and for the asking price, assuming it wasn't structurally unsound, was something we could see ourselves doing up and flipping when we finally move back to Australia. So our agent told us we needed to get pre-approved for finance as the next step, and hooked us up with a mortgage broker, who was able to see us today. She said that pre-approval would be no problem, and we got what seemed to be a ridiculously good rate for a 5 year adjustable rate mortgage. Our agent called us back tonight and told us that there was another offer on the table for less than the asking price, and that the property had been red-tagged. It would appear that none of the modifications had permits. He's going to check with the city tomorrow to find out exactly what the nature of the red-tagging is all about, and what would be involved to get the property un-red-tagged, but I've got that feeling that it's going to be better to just walk away from it at this stage. So that's how we've spent our weekend. Speculating on real estate.

Now that there is some content here, I added myself to the Planet Debian blog aggregator. Sorry for my weird head image, the shadow looked much better in Gimp. I ll have to correct that on another day Thanks to Holger Levsen for pointing me at the wiki entry which describes how a Debian developer can add himself to the Planet.

Remember Vitacilina? A small aggregation library I wrote last year to be intended to replace Planet on Planeta Linux? Well, it never quite replaced it but it achieved some level of stability since I was using it for a number of tasks at work. So, during this long holiday weekend, I received a notification that the Request To Package bug I had filled against the Work-Needing and Prospective Packages in Debian has already been taken care of and the library had been uploaded. Of course, I could have made this myself a long time ago, but at the time it was simpler and faster just to hope someone else would do it at some point. So, Dario did it. He packaged it and uploaded version 0.1 under the umbrella of the Debian Perl Group. Hurray! But then I realized that Alexandr Ciornii had implemented some nice changes to Vitacilina back in September that I never got to include or release as a CPAN distribution. And so I just did. I've uploaded 0.2 to CPAN and you can fetch it with cpanf Vitacilina or wait for the Debian Perl folks to update it

I got a new computer at home a week ago and finally got around to assemble all the parts. Which wasn t as easy as expected, especially fitting the CPU cooler was a hard fight. Specs For the curious, here are the specs:

CPU

AMD Phenom II X4 965 (4 3.4 GHz)

Mainboard

MSI 790GX-G65

Graphics

ATI Radeon HD 3300 (on-board)

RAM

8 GB, DDR3

Hard drives

2x SATA 1.5 TB (by Western Digital)

Ubuntu installation For testing and having a first look, I installed Ubuntu karmic koala (amd64). Installation went like a breeze, everything was detected and worked out of the box. Well, kind of graphics performance was dreadful. Which was kind of expected. Debian installation I originally thought about using Debian only inside virtual machines or change roots. Still, Ubuntu does not really feel like the real thing . So I went to install Debian, aiming at a sid/unstable installation. The first boot using the official squeeze snapshot netinst image (Binary-1 20091128-11:21) went fine. Up to the first prompt: No input was possible. Probably a problem with the USB keyboard I had connected (Logitech wireless). Out of curiosity I tried the graphical installer, which did not even get so far. It was stuck in an endless loop trying to start an X11 server. So I dug for a PS/2 connected keyboard and had more luck. I got to the point where the installer searches for the CD-ROM drive. As I did not want to dismantle my old system yet, I used an external USB DVD/RW drive. This was not detected by the installer so I was unable to continue installation. I guess, the NIC driver was also on the disc so no ethernet either. Today I installed the DVD burner into the tower and had more luck. It still amazes me how easy it is to create my default storage setup using d-i (LVM on RAID). However, the installer failed to reread the partitions after I created two on each drive, interestingly telling me about /dev/sda2 being busy. Perhaps a left-over swap partition from the Ubuntu install? Anyway, after running fdisk manually and writing the same partition table again, I was able to continue. The remaining d-i steps went fine, with just a nuisance: I was asked for the console font setting twice. And I had no idea what it was asking of me, AFAIK UTF-8 should be fine for all possible uses. I selected # Latin1 and Latin5 western Europe and Turkic languages. Not that I will see the console unless Xorg fails to run After having the base system running, I rebooted without selecting any more software, partly because I knew that the resync on md1 will need restarting after booting into the new system. The new system booted fine and I called aptitude to install build-essential, Xorg and both KDE and Gnome desktops. This pulled in MySQL via akonadi-server (ouch!) and I was asked for a MySQL root password. Seriously, I don t care, this is a desktop system. I tend to forget the password anyway and the last time, root was able to reset it. So I just hit Enter, leaving no password set. This lead to the installation asking me two more times for the password, which really sucks given that the server is only used by Akonadi for whatever reason and the last time I looked, it creates its own MySQL configuration. Albeit my old system is 8 years old, the new system still seemed slower. Which of course is due to disk latencies, given that /dev/md1 was being synchronized in the background. Anyway, I was eager to test the desktop experience and started gdm. X came up fine, but again I had no mouse and no keyboard (USB mouse, keyboard connected as well as PS/2 keyboard). I also was unable to switch to a VT, so I logged in remotely and rebooted the new system. After the reboot, hal obviously picked up the input devices and X11 worked fine now. At this point, I stopped as the sunday almost passed already. Summary: Debian installation still needs some improvements I think. Maybe our distribution is just too stable, after all my last install is 3 years back due to a disk crash Relevant Debian bugs

• #558679: My installation report with some logs included.
• #558681: Nagging about MySQL root password.
• #558686: Failure to reload partition table.
• #545933: No USB keyboard support
• #315553: Installation from optical drive on usb fails (but this is for kernel 2.4)
• #558691: No keyboard and mouse after fresh installation of xserver-xorg.

So this is in some sense a nadir for shell scripting. 2 lines that do something out of 111. Mostly cargo-culted from cowpoke by ron, but much less fancy. rsbuild foo.dsc should do the trick.

#!/bin/sh
# Start a remote sbuild process via ssh. Based on cowpoke from devscripts.
# Copyright (c) 2007-9 Ron  <ron@debian.org>
# Copyright (c) David Bremner 2009 <david@tethera.net>
#
# Distributed according to Version 2 or later of the GNU GPL.
BUILDD_HOST=sbuild-host
BUILDD_DIR=var/sbuild   #relative to home directory
BUILDD_USER=""
DEBBUILDOPTS="DEB_BUILD_OPTIONS=\"parallel=3\""
BUILDD_ARCH="$(dpkg-architecture -qDEB_BUILD_ARCH 2>/dev/null)"
BUILDD_DIST="default"
usage()
 
    cat 1>&2 <<EOF
rsbuild [options] package.dsc
  Uploads a Debian source package to a remote host and builds it using sbuild.
  The following options are supported:
   --arch="arch"         Specify the Debian architecture(s) to build for.
   --dist="dist"         Specify the Debian distribution(s) to build for.
   --buildd="host"       Specify the remote host to build on.
   --buildd-user="name"  Specify the remote user to build as.
  The current default configuration is:
   BUILDD_HOST = $BUILDD_HOST
   BUILDD_USER = $BUILDD_USER
   BUILDD_ARCH = $BUILDD_ARCH
   BUILDD_DIST = $BUILDD_DIST
  The expected remote paths are:
  BUILDD_DIR  = $BUILDD_DIR
  sbuild must be configured on the build host.  You must have ssh
  access to the build host as BUILDD_USER if that is set, else as the
  user executing cowpoke or a user specified in your ssh config for
  '$BUILDD_HOST'.  That user must be able to execute sbuild.
EOF
    exit $1
 
PROGNAME="$(basename $0)"
version ()
 
    echo \
"This is $PROGNAME, version 0.0.0
This code is copyright 2007-9 by Ron <ron@debian.org>, all rights reserved.
Copyright 2009 by David Bremner <david@tethera.net>, all rights reserved.

This program comes with ABSOLUTELY NO WARRANTY.
You are free to redistribute this code under the terms of the
GNU General Public License, version 2 or later"
    exit 0
 
for arg; do
    case "$arg" in
        --arch=*)
            BUILDD_ARCH="$ arg#*= "
            ;;
        --dist=*)
            BUILDD_DIST="$ arg#*= "
            ;;
        --buildd=*)
            BUILDD_HOST="$ arg#*= "
            ;;
        --buildd-user=*)
            BUILDD_USER="$ arg#*= "
            ;;
        --dpkg-opts=*)
            DEBBUILDOPTS="DEB_BUILD_OPTIONS=\"$ arg#*= \""
            ;;
        *.dsc)
            DSC="$arg"
            ;;
        --help)
            usage 0
            ;;
        --version)
            version
            ;;
        *)
            echo "ERROR: unrecognised option '$arg'"
            usage 1
            ;;
    esac
done
dcmd rsync --verbose --checksum $DSC $BUILDD_USER$BUILDD_HOST:$BUILDD_DIR
ssh -t  $BUILDD_HOST "cd $BUILDD_DIR && $DEBBUILDOPTS sbuild --arch=$BUILDD_ARCH --dist=$BUILDD_DIST $DSC"

<object height="344" width="425"><param name="movie" value="http://www.youtube.com/v/0Bmhjf0rKe8&amp;hl=en_US&amp;fs=1&amp;"><param name="allowFullScreen" value="true"><param name="allowscriptaccess" value="always"><embed allowfullscreen="true" allowscriptaccess="always" height="344" src="http://www.youtube.com/v/0Bmhjf0rKe8&amp;hl=en_US&amp;fs=1&amp;" type="application/x-shockwave-flash" width="425"></embed></object> I am normally not so keen on GMO but if you managed to Clone/GMO/Tweak-Feline-DNA to make one of these for me, a one that stays so youthfully cute, I might be open to such modification.

<object height="344" width="425"><param name="movie" value="http://www.youtube.com/v/0Bmhjf0rKe8&amp;hl=en_US&amp;fs=1&amp;"><param name="allowFullScreen" value="true"><param name="allowscriptaccess" value="always"><embed allowfullscreen="true" allowscriptaccess="always" height="344" src="http://www.youtube.com/v/0Bmhjf0rKe8&amp;hl=en_US&amp;fs=1&amp;" type="application/x-shockwave-flash" width="425"></embed></object> I am normally not so keen on GMO but if you managed to Clone/GMO/Tweak-Feline-DNA to make one of these for me, a one that stays so youthfully cute, I might be open to such modification.

xm list grep <VMName>
xm block-list <VMName_Number>
xm block-detach <VMName_Number> <VMName_Vdev> -f
xm block-attach <VMName_Number> file:///iso/disk.iso \
hdc:cdrom r

My primary workstation is a 3 and a half year old Dell XPS M1710 laptop and it is getting old the 320 Gb hard drive is getting small and slow, the 3 Gb or RAM (expanded from 2 Gb) look too small and screen is turning brown in one corner. Also dead or dying: keyboard (after cat+coffee incident), built-in speakers, battery, power adapter (twice replaced), DVD writer (rads but does not write any more) and fans (one replaced, one getting louder by the week). Also the video card is a bit slow for nowadays needs. So I set aside some money and started considering the options. In short, I could get another laptop OR get a regular computer for the same price but with twice the power. After considering all the laptop options up to 1000LVL, I decided to get a regular computer and if/when I ll need to travel I ll either take one of the old laptops with me or get a new netbook. Now comes the fun part choosing the components! So far my choices are as follows:

• 1080p LCD/TN monitor with a built-in DVB-T TV receiver, around 23 around 180 LVL (comparable options without the TV receiver are around 50 LVL cheaper, getting an extra digital TV in the house is a nice extra)
• Intel Core i5 processor and a corresponding motherboard from ASUS with 4 RAM slots and 1 video card slot (I like ASUS hardware and the TurboBoost technology of i5 sounds a very nice alternative to buying a high-Ghz dual core setup) 125 LVL + 80 LVL
• NVidia 250GTS video card (for my WoW raiding fun) 60 LVL
• 2*2Gb of DDR3 1600 KINGSTON RAM with lifetime warranty, leaving 2 slots for expansion later 60 LVL
• 1 Tb HDD (Samsung Spinpoint F3 HD103SJ got great scores in recent digital times reviews) 55 LVL
• Chieftec 500W PSU and case (good experience with them so far and good reviews) 70 LVL
• Blueray player with DVD-RW (why not at this price?) 60 LVL

And that is it a great setup that will last me a few years for around 700 LVL and it will have more partial upgradability than my laptop that I paid twice as much 3 years ago. Any tips? Did I miss anything? Is it likely that anything in the above list will cause me any trouble in latest Ubuntu/Debian installations? Update: got all of the above, except 500 Gb HDD of the same kind (faster, cooler, but higher price per Gb) and no Blueray (no drive in LV at the moment and did not want to wait a few weeks). The results are good, but I wish I would have gone with a 5 LVL more expensive video card that has a quieter cooler. Now I am buying a separate video card cooler for around 20 LVL that will be both more efficient and much quieter than the stock cooler I have Zalman VF1000 is the model. Has not arrived yet. P.S. It looks like updating a post in WP, automatically bumps it back into the Planet feed. Sorry

The RFC editor has finally released

• K. Murchison, Ed., C. Lindsey, D. Kohn: Netnews Article Format. RFC 5536, November 2009.
• R. Allbery, Ed., C. Lindsey: Netnews Architecture and Protocols. RFC 5537, November 2009.

They obsolete the venerable RFC 1036 (Standard for Interchange of USENET Messages) from December 1987. The new RFCs are the work of the IETF working group USEFOR, chartered November 1997 and concluded March 2009. I ve heard it was not quite the longest lived IETF working group ever. (I personally missed the group by a couple of months, since I started following Netnews and NNTP standardization in April, due to Alue.) Both RFCs are on the Standards Track, currenlty as Proposed Standards. In my opinion, they are a huge improvement over both RFC 1036 and son-of-1036 (which will probably be published as a Historic RFC real soon now).

Once there was a project called Debian and a Ganneff.... (unfortunately in German only....)

22:20 < cb> Das ist doch voll die Arbeit Maintainer zu werden :-). Ich geb
gew nschte Pakete immer nur weiter an einen der da sowieso schon den Kernel
betreut :-)
22:21 < Ganneff> es is nur viel arbeit wenn du keinen schimmer hast
22:22 < cb> ja ich hab nur das seepferdchen *g*
22:22 < Obilan> Knusper: ja sicher ist es das
22:22 < Knusper> kopf -> tisch
22:22 < cb> Knusper, wenn du die verwaisten pakete findest siehst du auf
der gleichen seite auch die links wie man maintainer wird
22:22 < Knusper> die hab ich gefunden
22:22 < cb> zumindest hab ich das das letzte mal dort gesehen
22:24 < Ganneff> wnpp?
22:24 < Knusper> aber man brauch dann schon leute, die einen "hoffieren"
22:26 < Ganneff> du brauchst erstmal die ahnung nen paket zu bauen.
22:26 < Ganneff> dazu siehe new maint guide
22:26 < Ganneff> dann brauchste nen sponsor. dazu gehe zur mentors liste
22:26 < Ganneff> dann machste mit dem eh weng rum (also normal so
paketuploads via dem)
22:26 < Ganneff> und hast da halt schon dein maintenance krams.
22:27 < Ganneff> irgendwann is der sponsor angekotzt von dir und dem
laufenden arbeit generieren
22:27 < Ganneff> der tritt dich dann dass du mal DM anf ngst.
22:27 < Ganneff> das machste dann, und jemand anders tritt dir deine pakete
als dmua zurecht, nachdem du in nem keyring irgendwo steckst.
22:27 < Ganneff> und dann kannste denn krampf selbst hochladen. aber nix
andres.
22:27 < Ganneff> irgendwann willste was andres. und willst das auch noch
ohne son doofen sponsor
22:28 < Ganneff> dann versuchste dich an DD
22:28 < Knusper> ahhhhhh
22:28 < Ganneff> dazu musste dir nen advocate suchen
22:28 < Ganneff> der is  blicherweise einer dem du vorher im prozess
laufend auf den wecker fielst
22:28 < Ganneff> und er deswegen den nm leutz sagt "oh gott, befreit mich
bloss von dem"
22:28 < Ganneff> die machen das dann, aber sie wollen dir mal etwas
schmerzen zur ckgeben
22:28 < Ganneff> desdewegen wirste viele fragen beantworten m ssen
22:29 < Ganneff> und wie beim t v das auto musste hier deine pakete nochmal
vorstellen und checken lassen
22:29 < Ganneff> und dann nochmal fragen beantworten
22:29 < Knusper> thx...
22:29 < Ganneff> irgendwann gehst du dann mit den antworten den nm leuten
so auf den geist dass die dem frontdesk sagen "meine kacke, den wolle mehr
nit mehr sehen, schickts den dochma zu den DAMs, die hamms verdient"
22:30 < Ganneff> und die machen das dann meist. ausser sie m gen dich nich.
dann darfste nochma fragen beantworten
22:30 < Ganneff> bei den dams darfste nur warten. die testen deine geduld
22:30 < Ganneff> irgendwann langweilen die sich aber
22:30 < Ganneff> und dann kriegste pl tzlich mail
22:30 < Ganneff> OH MEIN GOTT. EIN NEUER DD.
22:30 < Ganneff> ende
22:30 < Ganneff> kapitel 2:
22:30 < cb> sch ne beschreibung
22:30 < Ganneff> du machst ne zeit als dd rum
22:30 < Knusper> LOL
22:30 < Ganneff> votest durch die gegend
22:30 < Ganneff> l dst pakete umher
22:30 < Ganneff> machst bugs in stable
22:30 < Ganneff> gibts dem security team arbeit
22:31 < Ganneff> sprich - du gehst allen auf den sack. denn das is was ein
dd macht. muss ja schliesslich auch spass machen.
22:31 < Ganneff> aber irgendwann, also irgendwann, da wird das langweilig
22:31 < Ganneff> und dann verschwindeste mal ne zeit.
22:31 < Ganneff> weil du weisst - da gibts noch son team. das brauch auch
arbeit
22:31 < Ganneff> die suchen so leute die weggehen und sich verstecken
22:31 < Ganneff> nennt sich mia. die suchen.
22:31 < Ganneff> vielleicht finden die dich ja auch.
22:32 < Ganneff> dann kommste zur ck und machst mal wieder etwas arbeit f r
security/stable/sonstwen
22:32 < Ganneff> oder nicht, aber das is langweilig, da fliegste einfach.
22:32 < Ganneff> wennde dann gar keinen bock mehr hast und ne l ngre pause
willst
22:32 < Ganneff> dann gehste und machst eien auf emeritus
22:32 < Ganneff> das sind die rentner, die alten s cke, die sich
zur cklehnen und  ber die versuche der neuen lachen die sich grad von den
sponsoren qu len lassen
22:33 < Ganneff> ende kap. 2, ich hab keinen bock mehr. (jaja, emeritus)

Cheers to #debian.de on freenode

I do not really understand why they don't support this themselves, but Google Analytics will not track keywords for Google image search. Instead it just shows up as "referrer". A site I'm webmaster for, Swing and the City, gets a lot of image search exposure (funnily for an image that is gone since August, Google also needs to work on their index, too), so it was a bit odd to have images.google.com show up as top referrer but not "organic search".Here's the code I use to fix this:

var r=document.referrer;
if(r.search(/images.google/)!=-1 && r.search(/prev/)!=-1) 
 var e=new RegExp("images.google.([^\/]+).*&prev=([^&]+)");
 var m=e.exec(r);
 pt._addOrganic("images.google","q",true);
 pt._setReferrerOverride("http://images.google."+m[1]+unescape(m[2]));
 ;
pt._addOrganic("maps.google","q",true);
pt._addOrganic("forestle.org","q",true);
pt._trackPageview();

Note that image search is more complicated than the maps and forestle search engines I also add for keyword tracking. The original query is encoded in the "prev" parameter, and the easiest (or only?) way to get working tracking is to use the ReferrerOverride function of analytics.Note: this is not a straight copy & paste, since I use this code in a compressed and encoded (for injection into the page via DOM ops) form. So no guarantee of syntax completeness. You'll need to adjust it to your variable naming anyway (I use "pt" instead of "pageTracker"). This is just to show you the use of unescape on the "prev" parameter for this purpose.