On Wed, 2008-07-23 at 00:09 +0200, Robert Millan wrote: > On Tue, Jul 22, 2008 at 06:01:41PM -0400, Pavel Roskin wrote: > > On Tue, 2008-07-22 at 23:37 +0200, Robert Millan wrote: > > > > > > Suppose that we don't have device.map. Then I don't need to add entries > > > > for temporary devices. Also, I won't be able to create a cross-drive > > > > configuration by accident, simple because it won't be allowed by > > > > default. > > > > > > But we could have device.map _and_ a fallback mechanism for when there's > > > no match (e.g. give it a "(dummy0)" drive). > > > > > > I even STR I implemented that in some patch. > > > > The problem was that the reliable information was called "dummy" and > > used as fallback, whereas the unreliable information was used by > > default. > > None of it was intended to be reliable for anything. It was simply a way of > making GRUB non-util code handle system devices that haven't been registered > in device.map, like a temporary USB disk.
The boot driver information from BIOS should be considered as more reliable than guess by a userspace program how BIOS might see the drives. There are known buggy BIOSes, but we know how to work it around. -- Regards, Pavel Roskin _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
