Skip to content

grand unified failure

When trying to re-install GRUB: # grub-install /dev/sda1
The file /boot/grub/stage2 not read correctly.
...but the intertubes saved my day, when I came across: # grub
grub> root (hd0,0)
grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 17 sectors are embedded.
Running "install /boot/grub/stage1 (hd0) (hd0)1+17 p (hd0,0)/boot/grub/stage2 /boot/grub/menu.lst"...
grub> quit
However, I still don't know why grub-install doesn't work anymore.

rpc.idmapd woes

Bug #87382 bit me: # mount -t nfs4 sheep:/nfs4 /mnt/nfs4
Warning: rpc.idmapd appears not to be running.
All uids will be mapped to the nobody uid
...although rpc.idmapd was running (on the client). Now I have to: /bin/pidof rpc.idmapd > /var/run/ But the real question is: why does mount(1) bother for pidfiles, rather than checking for functionality?

s9y dev

Enjoying s9y-dev, clicking on various links gave: Parse error: parse error, unexpected t_endif in ... This blogentry helped: setting the blog's style to something else than "Default-PHP" (like "Serendipity 3.0") made the errors go away.

having fun with mozilla plugins

Tracking development snapshots of Mozilla Firefox can be fun, especially when the thing almost always (sic!) behaves like a friggin' -final, which is a good thing. However, this means of course that plugins have to keep up with the pace set by this development, which is hardly possible for all available plugins. My favourite plugin, Flashblock, says: Works with: Firefox 1.4.1 – 3.0a7 But 3.0a8 is already out! Let's try something then:
# wget --no-check-certificate # mkdir fb && cd fb && unzip ../flashblock* # sed -ie 's/3\.0a7/3.0a9/' install.rdf # zip -9r ../flashblock- *
Now install this new .xpi - if we're lucky, that's all it took to change. If not, RTFS :-\

apt-get segfaults

While installing a box, it happened that apt-get would segfault upon upgrade or install. Suspecting memory issues first, we tried quite a few things, before coming across a blogentry: a corrupt pkgcache was to blame. One should simply remove it and start over again:
cd /var/cache/apt rm pkgcache.bin srcpkgcache.bin
Unfortunately, we didn't save the corrupt files, so we cannot even open a bug.