On Sat, Aug 28, 2010 at 11:14:46PM -0500, Moshe Yudkowsky wrote:
> Ben,
>
> Thank you for your attention to this bug.
>
> I have to wonder: let's say I have both grub and lilo packages, and I
> have in the past used one or the other... how will this new policy play
> out? I'd think that I'd have to make a choice in /etc/alternate, or dpkg
> configure, rather than have the loaders battle it out.
I met Colin Watson last night and he said that he (as GRUB maintainer)
and Daniel Baumann (as syslinux maintainer) had discussed doing something
like this. I hope that for the release after 'squeeze' we will have a
proper policy for this.
Right now, to disable LILO you must remove its configuration file
/etc/lilo.conf. For GRUB there isn't such an issue because it doesn't
need to write to the boot sector after its configuration is updated.
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
