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

Bug#608486: release notes §4.6.1 (expected removals): grub-legacy

On Fri, Dec 31, 2010 at 05:37:47AM -0600, Jonathan Nieder wrote:
> grub-pc 1.98+20100527-1 and later conflict with grub-legacy.  grub
> 0.97-58 and later depend on grub-pc.  Therefore upgrades from lenny
> with "grub" installed result in grub-legacy being removed, as planned.
> Is this worth a mention in the "expected removals" section[1] or
> "obsolete packages" section?

grub-legacy didn't exist in lenny - that binary package was introduced
in grub 0.97-54 - so no packages will be removed as a result of this

> Advice (precautions) for users upgrading?  Pitfalls?

Looking through the release notes, the main thing I notice is that we
offer advice on getting GRUB to boot using LABEL=, which is
unfortunately not well supported by GRUB 2 right now
(http://bugs.debian.org/568084).  That said, perhaps that section
(boot-hangs) is no longer needed since GRUB 2 uses UUIDs for root= by

In any event, the boot-hangs section needs to be entirely revised for
GRUB 2.  I can offer technical advice if needed, but I think the main
work required is essentially editorial: for example, is this section
worthwhile at all for squeeze?

There is an "Update to GRUB 2" section in SVN, marked as
condition="fixme".  Here's an initial attempt.  I removed the
"Arch-specific?" question because the Debian GRUB Legacy package only
existed on amd64 and i386 (well, and hurd-i386, but it doesn't seem to
be covered by the release notes anyway).  I made a small tweak to
prepare-initramfs too.

(Style note: I would advise preferring "GRUB 2" over "GRUB2", for
consistency with upstream documentation.)

Index: en/upgrading.dbk
--- en/upgrading.dbk	(revision 7980)
+++ en/upgrading.dbk	(working copy)
@@ -247,7 +247,7 @@
     settings for <systemitem
     role="package">initramfs-tools</systemitem> now generate an
     initramfs that is too large for <acronym>LILO</acronym> to load. Such users should
-    either switch to <systemitem role="package">grub</systemitem>, or
+    either switch to <systemitem role="package">grub-pc</systemitem>, or
     edit the file
     <filename>/etc/initramfs-tools/initramfs.conf</filename>, changing
     the line <programlisting>MODULES=most</programlisting> to read
@@ -1844,14 +1844,28 @@
-<!-- TODO: Arch-specific? -->
-<section id="update-grub" condition="fixme" arch="amd64;i386">>
-<title>Upgrade to GRUB2</title>
+<section id="update-grub" arch="amd64;i386">
+<title>Upgrade to GRUB 2</title>
-Describe the steps required to be done remove Grub's chain-loading.
-There is a good resource to document the upgrade at
+During the upgrade, you will normally have been offered the option to
+"chainload" GRUB 2: that is, to keep GRUB Legacy as the primary boot loader
+but to add an option to it to load GRUB 2 and then start your &debian;
+system from that.  This allows you to verify that GRUB 2 works on your
+system before committing to use it permanently.
+Once you have confirmed that GRUB 2 works, you should switch to using it
+properly: the chainloading setup is only intended to be used temporarily.
+You can do this by running <command>upgrade-from-grub-legacy</command>.
+The GRUB Manual has <ulink
+more information</ulink> on the changes between GRUB Legacy and GRUB 2, some
+of which may require changes to complex configurations.  If you have not
+modified your boot loader configuration, you should not need to do anything


Colin Watson                                       [cjwatson@debian.org]

Reply to: