Re: [PATCH] add drivemap support to 30_os-prober.in and use UUIDs

[Felix Zielcke <fzielcke@z-51.de>]

Am Montag, den 08.06.2009, 12:54 +0200 schrieb Vladimir 'phcoder'
Serbinenko:
> On Sun, Jun 7, 2009 at 5:55 PM, Pavel Roskin<proski@gnu.org> wrote:
> > On Sun, 2009-06-07 at 17:37 +0200, Felix Zielcke wrote:
> >> Attached patch uses `prepare_grub_to_access_device' to set the root in
> >> the generated entrys.
> >> And it adds drivemap to the chainload ones, if root isn't (hd0).
> >>
> >> The Debian grub-installer adds map only with Dos and Windows, should I
> >> do the same or is it okay to do it for all?
> >
> > Perhaps it would be better to avoid it when it's not needed.  But it may
> > be tricky to determine what bootloader we are using.
> >
> > Let's do it always and eliminate the cases where it's harmful or
> > definitely useless.
> Drivemapping isn't good per se. It's more like unfortunate need.
> However it should always be safe to drivemap because AFAIK no OS
> relies on particular drive ordering except 0x80 being booting drive.
> However this entry will fail unless my drivemap fix is incorporated

os-prober currently prints `chain' on FreeDOS, QNX4, Windows, MS-DOS,
Solaris, Minix and Dell Utility Partition 
Solaris probable won't need it but for Minix and QNX4 (I don't even know
what this is) I don't know.
FreeDOS probable needs it too or not?
So better just use it always and if someone says it can't boot because
of drivemap we can change it for that OS.
-- 
Felix Zielcke