Hi FYI,

I was playing with Restore DC Visuals on the hijack menu the other day when, following a reboot, the player (just the player software itself - seemingly playing a track but in fact not, no menu response, but hijack/kernel were alive and I could kill the player if I got in a ctrl-c early enough following a reboot before it started opening its database files) became stuck. It could no longer remount /dev/hda4 re-writeable either without blocking pretty much forever, although the filesystem was marked clean. I was able to remove and test the disk, at which point in my frustration, I simply reformatted it and re-installed. The disk seemed perfectly ok on a desktop Linux box.

Not yet had time to look, but I'm assuming that hijack uses the config file in /drive0/var/config and does some file related system calls directly from in-kernel. I don't see how that could have broken the filesystem, but perhaps some state was saved that caused the player software to become unhappy.

Just an FYI.

Jon.