On Fri, 7 Apr 2006 22:44:41 +0200 maximilian attems wrote:
> On Fri, Apr 07, 2006 at 09:58:07PM +0100, David Jarvie wrote:
> > On Friday 07 April 2006 20:30, maximilian attems wrote:
> > > On Fri, Apr 07, 2006 at 08:51:12PM +0100, David Jarvie wrote:
> > >
> > > if grub is around lilo isn't run.
>
On Friday 07 April 2006 21:44, maximilian attems wrote:
> kernel-package wants to drop ability to run lilo on the postinstall.
> grub is the _default_.
>
> update-initramfs can easily check for an lilo.conf and warn in those cases.
A warning (preferably in the form of a prompt which must be acknow
Processing commands for [EMAIL PROTECTED]:
> severity 361270 important
Bug#361270: Upgrade of initramfs-tools made kernel unbootable with lilo
Severity set to `important'.
> tags 361270 moreinfo
Bug#361270: Upgrade of initramfs-tools made kernel unbootable with lilo
There were no tag
severity 361270 important
tags 361270 moreinfo
stop
On Fri, Apr 07, 2006 at 04:43:26PM +0100, David Jarvie wrote:
>
> Upgrading initramfs-tools yesterday caused the current kernel 2.6.15-1
> to become unbootable, apparently because the upgrade process regenerated
> initrd.img-2.6.15-1-k7. The upg
Package: initramfs-tools
Version: 0.59b
Severity: critical
Justification: breaks the whole system
Upgrading initramfs-tools yesterday caused the current kernel 2.6.15-1
to become unbootable, apparently because the upgrade process regenerated
initrd.img-2.6.15-1-k7. The upgrade process should have
5 matches
Mail list logo