This bug was fixed in the package grub-installer - 1.49ubuntu9
---
grub-installer (1.49ubuntu9) lucid; urgency=low
* Ask grub-installer/only_debian at high priority again (LP: #47135).
Originally, in Warty, we ensured that this question wouldn't be visible
by default to supp
** Changed in: grub-installer (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: grub-installer (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
Installation of GRUB to MBR should always be confirmed
https://bugs.launchpad.net/bugs/47135
You received this bug not
** Branch linked: lp:~ubuntu-core-dev/grub-installer/ubuntu
--
Installation of GRUB to MBR should always be confirmed
https://bugs.launchpad.net/bugs/47135
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubunt
I can confirm the behaviour Ryan experienced: I applied a normal update
which included an update to grub (not sure whether via update manager or
synaptic) and it overwrote the MBR. Updates shouldn't break the system.
Also like Mark Warriner I use BootitNG which embeds its own code in the
MBR and a
This error still occurs in Ubuntu 10.04 (Lucid Lynx) Beta 1.
--
Installation of GRUB to MBR should always be confirmed
https://bugs.launchpad.net/bugs/47135
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubun
Ignore that; sorry, the order got swapped and I jumped to conclusions.
--
Installation of GRUB to MBR should always be confirmed
https://bugs.launchpad.net/bugs/47135
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
I just applied updates, through the update manager, and it overwrote the
MBR on a new disk I had installed for VMware. Please ask in any instance
like this.
--
Installation of GRUB to MBR should always be confirmed
https://bugs.launchpad.net/bugs/47135
You received this bug notification because y
I've nominated this bug for Karmic 9.10.
Reasons why I think this issue should be addressed:
1. Special boot managers or important data stored in the first track of the
hard disk can be overwritten by the automatic installation of GRUB. For
example, an Extended MBR (used by BootIt NG) is com
Given the current focus on installer QA, can this be addressed for
Januty 9.04?
--
Installation of GRUB to MBR should always be confirmed
https://bugs.launchpad.net/bugs/47135
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bug
Can this be considered in the upcoming Intrepid 8.10 and Hardy 8.04.2
releases?
To clarify, we would like to see the original Debian and Ubuntu
behaviour restored, with the initial dialog box asking if it is OK to
install GRUB to the MBR, followed by the optional second screen asking
where to inst
rpolach,
The bug you reported (#97174) applies to ubiquity: the graphical installer on
the Desktop CD. This bug (#47135) applies to the text mode installer on the
Alternate Install CD and Server CD.
--
Installation of GRUB to MBR should always be confirmed
https://bugs.launchpad.net/bugs/47135
minimal solution (and least controversial) filled separately at
https://bugs.launchpad.net/ubuntu/+bug/97174
--
Installation of GRUB to MBR should always be confirmed
https://bugs.launchpad.net/bugs/47135
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direc
I think we should have confirmation on where to install GRUB in all
cases, due to the reasons I outlined previously. This is also the
simplest and lowest risk change.
I would love to see this fixed in Feisty...
--
Installation of GRUB to MBR should always be confirmed
https://bugs.launchpad.net
I thing the reasonable solution would be that installation process
asks for confirmation on rewriting MBR at least when another *non-windows*
system on disk partitions is detected... because this case means:
1) those another systems are probably linux/bsd/... systems and there
is probably already g
I would like to re-open this discussion.
I think always confirming GRUB install to MBR in standard mode of the Alternate
Install CD (Debian Installer) is the most appropriate action for the following
reasons:
1. Avoids overwriting data or boot manager programs that might be stored in the
MBR or
15 matches
Mail list logo
