On 09/15/12 18:23, lee wrote:

Can't we have a boot manager which is independent of the installed OSs?
Grub kinda does its own thing already, and if there was something like a
standardised API through which OSs could tell the boot manager how they
are to be booted, we would install the boot manager as the first thing
and only once.  Then we could install as many OSs (or at least Linux
versions that comply with the standard) as we like, each of them telling
the boot manager how to boot them.  You wouldn't have the problem you
have now anymore.
All of this can be implemented with grub (grub2 at least). And one of the
approaches, is to have (main) grub config, which loads OS-specific ones. The
main grub config should only know where to find OS-specific ones and should
_not_ be updated by update-grub from any OS. The os-specific ones, on the
other hand, should be updated by update-grub from corresponding OS. The
main config must be updated either manually, or by some other method (using
standardized API, as you said). Anyway, this is exactly what described in
article i mention earlier. And may be it's a bit complicated, but it works.

What if you install a tiny minimal Linux version only to get grub
installed and exclusively use that version of grub for booting?  The
Debian installer and the package management would have to be fine
without installing or updating grub, and you would have to boot into
your minimal version to update grub from there.  Is that possible?


Grub from this minimal linux should somehow figure out which OS root
corresponds to which kernel, or where to find /boot corresponding to some
OS. Default grub2 scripts can't do this (at the time, when i have checked).


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5054d0bf.7070...@gmail.com

Reply via email to