[Bug 385053] [NEW] upgrade-from-grub-legacy writes to MBR even if the instance of grub it is replacing isn't there

[Andrew Starr-Bochicchio]

Public bug reported:

Binary package hint: grub2

I run a tri-boot: Ubuntu (jaunty) , Ubuntu+1 (karmic), Vista. I like to
have a configfile entry for the development version in the stable
version's menu.lst. So my grub instance for karmic wasn't actually on
the MBR. On running upgrade-from-grub-legacy on karmic, I was surprised
to see the words "Writing to Master Boot Record" come up.

We probably shouldn't write to MBR if the instance of grub being
upgraded isn't already there.

If this isn't practical, the user should be offered a choice to abort
the operation after being informed what is about to be done.

ProblemType: Bug
Architecture: i386
Date: Tue Jun  9 00:15:08 2009
DistroRelease: Ubuntu 9.10
Package: grub2 1.96+20090523-1ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-8.9-generic
SourcePackage: grub2
Uname: Linux 2.6.30-8-generic i686

** Affects: grub2 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug i386

-- 
upgrade-from-grub-legacy writes to MBR even if the instance of grub it is replacing isn't there
https://bugs.launchpad.net/bugs/385053
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs