Comment 3 for bug 495423
Revision history for this message
| Felix Zielcke (fzielcke) wrote Re: [Bug 495423] Re: update-grub writes MBR without prompt or backup | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Am Montag, den 14.12.2009, 13:45 +0000 schrieb Adrian Wilkins:
>
> A dist-update from Jaunty to Karmic doesn't upgrade grub to grub2
> (AFAIK), so why should a fresh install be different and upgrade the
> version of grub?
Well Ubuntu choose the way to use GRUB 2 for new installs, but to not
change the GRUB version for updates from jaunty (or older versions).
This is more safe because GRUB Legacy supports some setups like dmraid
which GRUB 2 didn't support at all, when karmic was released. And in
these cases grub-installer still installs GRUB Legacy.
The package grub-pc itself asks via Debconf for the device it should run
grub-install onto.
But this value gets preseeded by grub-installer on new installs, with
the device where it installs GRUB to.
If you want to change or remove it run: `sudo dpkg-reconfigure grub-pc'
But if the package gets upgraded and update-grub generates a grub.cfg
which isn't 100% compatible with the GRUB version in /boot/grub and
embeding area then maybe you can't boot. That's why we implemented this.
--
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer