Multiboot installs bootloaders clobber. Why
I've been helping a friend who wants a multi-boot machine to test OpenSuse 10.x, Zenwalk, and Xubuntu (as well as something from Redmond, WA) on the thing.
Of all of those (the WA thing doesn't count, of course), only Zenwalk didn't quietly clobber the existing bootloader. Xubuntu and OpenSuse didn't even bother to ask where I wanted the boot loader installed. OpenSuse found and added the others to its grub config, Kanotix just found and mounted the others' parbreastions. Zenwalk uses lilo, asks where it should be installed, and even lets you avoid installing a bootloader. None of the others offered any choice in the matter.
I would prefer these things to, at most, *augment* an existing boot loader's config IFF that can be done correctly. OpenSuse got that mostly right, which I should be thankful for, but why are they all insisting on replacing each other? I think that's pretty rude; the sort of behaviour I expect from commercial OS's, not Free Software.
Over the weekend, I had a running process, according to "ps aux", by USER root and the job was "sshd accepted". It was...
Bottom line, if I find this annoying, what would my Mom think if she tried this? Back to Redmond, obviously. Ptheh!
Now I suppose I'll run off to the Grub maintainers' site and rag on them a bit, and fire off a few blasts to the various distro's sites.
-- Any technology distinguishable from magic is insufficiently advanced.
Linux groups from Newsgroups