Re: Bug#576309: installation-reports: [pt_BR] A mistake in grub-pc configuration phase
tags 576309 pending
On Sat, Apr 03, 2010 at 09:35:03AM -0300, Eriberto wrote:
> 2010/4/3 Christian PERRIER <firstname.lastname@example.org>:
> > - the original English talks about "extended partition" which seems to
> > have been translated to "partição estendida" in the installer.
> Right. But you can't put data into an extended partition and because
> it I am suggesting to use logical instead of extended. I think the
> word "extended" can confuse the users.
Well. Each logical partition is actually contained within an extended
partition (despite how it's sometimes presented), and technically, GRUB
is installed to the extended boot record which is *outside* the logical
partition in the same way that the master boot record is outside any
individual primary partition. This may help (and the topic is certainly
confusing in various directions):
> > What you suggest implicitly is to mention that "sdc5" might be either
> > an SCSI or SATA partition *in the original string*. That seems correct
> > but needs to be discussed with the D-I team.
> > Indeed, nowadays, "sdc<n>" is o longer SCSI only so that mimght need
> > rephrasing in several places.
> I agree with your idea. But think that newbies may not know about it
> and a purpose of the d-i is to be very easy to all. So I think the
> SATA word can be added to description as an extra help to new users.
> It is modern because SATA is a recent technology. It is relevant as
> additional information to users that don't know SCSI-SATA concepts.
> The intent is update the description to make the GRUB installation
> more friendly.
Given that most disk devices nowadays use the sd* naming, and that this
is actually dependent not on PATA vs. SATA but on whether the kernel
driver uses the old IDE stack or the new libata stack (a concept I
definitely do not think should be introduced in user-visible text at
installation time!), I think it would be better to simply drop the IDE
vs. SCSI text as obsolete and to use /dev/sd* throughout.
I've committed this change, and would welcome feedback before it's
Author: Colin Watson <email@example.com>
Date: Sat Jul 30 10:06:52 2011 +0100
Update grub-installer/bootdev text to avoid GRUB device naming that changed between GRUB Legacy and GRUB 2, and to use libata-style device naming since that is more accurate for most people (closes: #576309).
diff --git a/debian/changelog b/debian/changelog
index 1c93c1b..ba38f66 100644
@@ -1,3 +1,11 @@
+grub-installer (1.66) UNRELEASED; urgency=low
+ * Update grub-installer/bootdev text to avoid GRUB device naming that
+ changed between GRUB Legacy and GRUB 2, and to use libata-style device
+ naming since that is more accurate for most people (closes: #576309).
+ -- Colin Watson <firstname.lastname@example.org> Sat, 30 Jul 2011 10:06:22 +0100
grub-installer (1.65) unstable; urgency=low
* Add mipsel/loongson-2f support, covering the Lemote YeeLoong (closes:
diff --git a/debian/grub-installer.templates b/debian/grub-installer.templates
index 8762b0c..a9a53b1 100644
@@ -77,15 +77,14 @@ _Description: Device for boot loader installation:
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.
+ The device should be specified as a device in /dev. Below are some
+ - "/dev/sda" will install GRUB to the master boot record of your first
+ hard drive;
+ - "/dev/sda2" will use the second partition of your first hard drive;
+ - "/dev/sdc5" will use the first extended partition of your third hard
+ - "/dev/fd0" will install GRUB to a floppy.
Colin Watson [email@example.com]