make-jpkg cannot create packages for Java 6 update 10 or newer, to fix this, edit /usr/share/java-package/sun-j2sdk.sh.

Add this stanza:

       "jdk-6u"[0-9][0-9]"-linux-x64.bin") # SUPPORTED
            j2se_version=1.6.0+update${archive_name:6:2}${revision}
            j2se_expected_min_size=130
            found=true
            ;;

right after

        "jdk-6u"[0-9]"-linux-x64.bin") # SUPPORTED
            j2se_version=1.6.0+update${archive_name:6:1}${revision}
            j2se_expected_min_size=130
            found=true
            ;;

Then try again, should be golden.

I found these things useful in getting a usable system:

• Reenabling the quick launch bar
• Restoring underlined key shortcuts
• Changing back to oldskoolclassic Alt-Tab

There is no facility to clear it, but possibly doing the above, then removing it again, could clear the cache.. Didn’t try it – just disabled it. My resolvers are on the local network so they can cache it for me – this way they ‘ll actually have something to do

However, I don’t really like the laptop for much else than sitting in front of TV chatting or surfing a bit, so for serious work I really want my desktop…

Still had an Athlon X2 board lying around, with some PCI Express slots, CPU, RAM, etc, so decided to build this in – after all, my offboard RAID controller should be OK to take along to a new system, no INACCESSIBLE_BOOT_DEVICE for me!

However… the ARC-1200 is not compatible with the A8N-SLI Premium… board simply doesn’t boot if you put it in any of the PCIe slots. So I took an 8-port PCIe Areca from the spare parts, as that could read my RAID on the disks at least; but this lead to INACCESSIBLE_BOOT_DEVICE because the PCI ID’s of the 2_port and the 8-port weren’t the same.

My wif’s PC to the rescue, put both Areca’s in, with the disks connected to the 2-port, this allowed me to install the 8-port’s drivers in Windows, then moved it all back to my own temporary PC… Yes, no stop 7B … but stop 7E?!

The machine booted in safe mode, so I was on the right track, and after some googling and fiddling, turns out you can’t down/upgrade easily from an Intel to an AMD CPU, as you will get the 7E stop.

Details are here – I didn’t get the info from this page (seeing as it talks about Virtual PC), instead clicked through on some forums, but it contains the solution none the less. Disabling the IntelPPM driver makes the crash go away (as is to be expected, this is an AMD CPU after all).

Had to reactivate Windows again but that was no biggie.. hope it will still reactivate when I have an RMA board..

I use this RSS feed in an application and am pretty fed up trying to keep up with their flying shit implementation of RSS. I can’t imagine everyone goes to their site every once in a while and updates their RSS reader to yet another new location. Am I missing the point of RSS? I thought it was fire and forget… Sigh.

My wife however found a nice deal a few weeks ago: if you buy the 2 year subscription to Linux+ magazine (for 49.99 EUR) you get a Tuxdroid as a welcome gift! That’s essentially a Tuxdroid for 50 euro with free shipping and with a free 2 year magazine as well Mine’s on the way, thanks to my wife who gave it to me as a gift – already received 2 issues and they’re interesting (read a chapter about forensics cd’s today).

ERROR: fping (‘/usr/bin/fping -C 1 localhost’) could not be run: localhost address not found

After digging around somewhat (this worked fine when run on the commandline) turns out my /etc/hosts was chmodded 700 instead of 744. Weird, but this meant only root could resolve it. What I don’t understand is why this did not work – my resolvers also return 127.0.0.1 for the “localhost” query.

Anyway, if you get this error, check if the smokeping user can resolve localhost too

As Kris would say, it was some sort of DNS problem…

cannot authenticate to server relay.mx.mydomain[123.123.123.169]: no mechanism available

If you forget smtp_sasl_security_options =, you would get the following error:

cannot authenticate to server relay.mx.mydomain[123.123.123.169]: no worthy mechanisms available

Note the small but important difference: worthy. All Google hits on this problem tell you to allow PLAIN if you get the “worthy” error, except I already did, and this was not the error. #postfix couldn’t help either Dug somewhat further…

The missing key? The libsasl2-modules package is also needed, not only libsasl2 (restart Postfix after installing). Tada.