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

Bug#502446: marked as done (debian-installer: grub-installer is not updated for grub-pc introduction)

Your message dated Sat, 01 Jan 2011 11:56:04 +0000
with message-id <1293882964.2418.0.camel@eeepc.Belkin>
and subject line 
has caused the Debian Bug report #502446,
regarding debian-installer: grub-installer is not updated for grub-pc introduction
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
502446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502446
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debian-installer
Version: rc2
Severity: important

rc2 comes with grub-pc in its initramfs /pool directory.  So d-i team
decided to offer not only grub (grub legacy) but also grub-pc (grub 2).
Good for you.

  grub-installer_1.32_i386.udeb
  grub-pc_1.96+20080512-1_i386.deb
  grub_0.97-39_i386.deb 

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:

Template: grub-installer/bootdev
Type: string
Description: Device for boot loader installation:
 You need to make the newly installed system bootable, by installing
 the GRUB boot loader on a bootable device. The usual way to do this is to
 install GRUB on the master boot record of your first hard drive. If you
 prefer, you can install GRUB elsewhere on the drive, or to another drive,
 or even to a floppy.
 .
 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);
  - "(hd0,2)" or "/dev/hda2" will use the second partition of your
    first IDE drive;
  - "(hd2,5)" or "/dev/sdc5" will use the first extended partition of
    your third drive (SCSI here);
  - "(fd0)" or "/dev/fd0" will install GRUB to a floppy.

This should be easy to do for all languages and reduce confusion.

Question is how to impliment it without breaking grub legacy.  Maybe you
create "Template: grub2-installer/bootdev" and adjust script based on
boot loader used.

I think this is one of the root cause of problem people are reporting
such as: 501942.

The other issue may be around 30_os-prober script in grub-pc package.  I
need to check more but this is less problematic since at least main OS
will boot from right boot sector.  

(If I am pedantic, I can say that "/dev/sdc5" may not be the first
extended partition but simply 5th partition in GPT.  But this issue can
be ignored since it is unlikely to cause any major cofusion.)

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
fixed in grub-installer 1.58.
See #581687

-- 
Melhores cumprimentos/Best regards,

Miguel Figueiredo
http://www.DebianPT.org

--- End Message ---
Reply to: