[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#502446: debian-installer: grub-installer is not updated for grub-pc introduction



Hi,

Otavio asked me to comment on this.

Notice that I maintain grub/grub2, not grub-installer. In fact, my
recommendations as grub maintainer are often dismissed here, so take
this with a grain of salt.

On Thu, Oct 16, 2008 at 11:41:22PM +0900, Osamu Aoki wrote:
> 
> But if you do, you must take care critical diffrences of these 2
> programs.
> 
> For /dev/hda3, grub legacy used (hd0,2) while grub 2 use (hd0,3).
> 
> The template file in grub-installer needed to be updated not to mislead
> users.  Template: grub-installer/bootdev needs to be updated 
>  "(hd0,1)" --> "(hd0,2)"
>  "(hd2,4)" --> "(hd2,5)"
> as:

It's not critical, and I don't think it's worth it.  It just affects a template
description, and this particular problem is hopefully going away post-Lenny as
soon as GRUB Legacy is completely deprecated.

#473401 OTOH has a real effect in end usability, and should be taken into
consideration for Lenny.

>  The device can be specified using GRUB's "(hdn,m)" notation, or as a device
>  in /dev. Below are some examples:
>   - "(hd0)" or "/dev/hda" will install GRUB to the master boot record
>     of your first hard drive (IDE);

This paragraph leads user to think there's a 1:1 correspondence between GRUB
drives (which are enumerated by BIOS) and Linux devices (which are enumerated
by Linux itself).  However, it's really a game of gambling.  E.g. "/dev/hda"
is "(hd0)" _most of the time_, but not always.

This is something we already solved in GRUB 2 (by using UUIDs).

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



Reply to: