From: Pavel Roskin <[EMAIL PROTECTED]>
Subject: Re: Support for "map" without arguments
Date: Wed, 15 Dec 1999 10:27:53 -0500 (EST)
> 1) I expected that the "map" command affects the way how GRUB itself
> recognises the drives.
There is a good reason why GR
Hello, OKUJI!
> > I'm trying to understand why "map" doesn't work for me.
>
> Give me more detailed information. What did you do and what
> happened?
Well, it seems that I used to expect too much from that command before I
looked at the code.
1) I expected that the "map" command affects the
From: Pavel Roskin <[EMAIL PROTECTED]>
Subject: Support for "map" without arguments
Date: Thu, 9 Dec 1999 00:21:37 -0500 (EST)
> I'm trying to understand why "map" doesn't work for me.
Give me more detailed information. What did you do and what
happened?
Jeff Sheinberg writes:
> You can make grub use late binding - this is what the `d' flag is
> for. So if you want to use a grub that has been installed with
> the `d' flag after you physically changed the drive number - you
> just boot your emergency grub boot flo
Pavel Roskin writes:
>
> Also it seems that the mapping is only activated when
> chainloader is used and it has no effect on GRUB itself. Should
^^^^
> it be fixed or documented?
>
IMO, this is a feature, not a bug. This is what the map command
is for.
Hello!
I'm trying to understand why "map" doesn't work for me.
A side effect of my efforts is the attached patch.
It makes it possible to examine the mapping table before it is activated.
"map" without arguments will show the mapping table.
ChangeLog:
* stage2/builtins.c (map_func): if
