update grub + 2 ubtuntu installs with shared /boot

[Gary W. Swearingen]

Philip Lawatsch <philip at lawatsch.at> writes:
> Gary W. Swearingen wrote:
>> Philip Lawatsch <philip at lawatsch.at> writes:
...
> Geeeee.
> As a long time (happy) slackware user I can honestly tell you that your
> image of slackware users is pretty wrong.
> I only abandoned slackware because of Pats, well, too 'conservative'
> policy regarding packages (kernel, glibc etc). And the drop of gnome
> (kde is still included though) was the final reason to leave (see?
> Slackware users want shiny desktops too).

I'm not convinced, and your GNOME comment sure didn't help your
argument.  I've seen too many comments on BSD lists recommending
Slackware for it's simplicity, less things to have to learn, etc.
And believe it or not, there are a significant number of people
who don't use GNOME/KDE or even X at all, either for servers or
desktops.

> Yes, will do that. Perhaps I'll one day have time to hack update-grub to
> do what I want :)

You wanted one /boot to keep things simple.  I hope you don't think
you need extra partitions for these directories.  You just use them as
normal directories in the two "/" partitions.  I don't see how that's
any less simple than having two OSes to share a third partition.

Even if you were to hack update-grub, I'd still want to let each OS
keep it's /boot in the "/" partition.  That seems simplest or at least
the least problematic.  Getting your custom update-grub to handle
other OSes could be done without mixing kernels from multiple OSes in
one /boot; update-grub could search all Linux partitions for kernels
or you could have one /grub partition with the grub files and a custom
file with info about all kernels that update-grub maintains.


An easy (but rather ugly) kludge would be to have menu.lst boot
"part-P-kernel-K", where P = hda2, hda9, hdb1 (say) and and K = 1, 2,
3 (say) and then have a script which copies (or renames) the
just-installed kernel files so your single menu.lst needn't be
changed.