Bug#271699: marked as done (kernel-image-2.4.26-1-686: update does not run lilo)
Your message dated Fri, 14 Oct 2005 17:38:57 +0900
with message-id <20051014083857.GB19862@verge.net.au>
and subject line kernel-image-2.4.26-1-686: update does not run lilo
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 14 Sep 2004 16:22:40 +0000
>From glisse@stedding.loria.fr Tue Sep 14 09:22:40 2004
Return-path: <glisse@stedding.loria.fr>
Received: from stedding.loria.fr (localhost.localdomain) [152.81.8.164]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1C7G4m-0008E3-00; Tue, 14 Sep 2004 09:22:40 -0700
Received: from glisse by localhost.localdomain with local (Exim 4.34)
id 1C7G4H-0003IV-7X; Tue, 14 Sep 2004 18:22:09 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Marc Glisse <glisse@stedding.loria.fr>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: kernel-image-2.4.26-1-686: update does not run lilo
X-Mailer: reportbug 2.63
Date: Tue, 14 Sep 2004 18:22:09 +0200
Message-Id: <E1C7G4H-0003IV-7X@localhost.localdomain>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: kernel-image-2.4.26-1-686
Version: 2.4.26-6
Severity: wishlist
I had kernel-image-2.4.26-1-686 installed, and it got updated by a simple
apt-get upgrade. Then I got a very long message about how important it
was to reboot immediatly. I think it might be a good idea to at least add
a clear warning that people still using lilo should run lilo before
rebooting, because the upgrade leaves the machine in an unbootable state
for them. Not running lilo when you install a new kernel is not too bad,
but when you replace an existing one...
By the way, I know that grub is now the default bootloader for debian,
which I believe is great.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing'), (70, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-686
Locale: LANG=fr_FR, LC_CTYPE=fr_FR
Versions of packages kernel-image-2.4.26-1-686 depends on:
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii initrd-tools 0.1.74 tools to create initrd image for p
ii modutils 2.4.26-1 Linux module utilities
-- no debconf information
---------------------------------------
Received: (at 271699-done) by bugs.debian.org; 14 Oct 2005 08:55:22 +0000
>From horms@koto.vergenet.net Fri Oct 14 01:55:22 2005
Return-path: <horms@koto.vergenet.net>
Received: from koto.vergenet.net [210.128.90.7]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EQLLV-0008QM-00; Fri, 14 Oct 2005 01:55:22 -0700
Received: by koto.vergenet.net (Postfix, from userid 7100)
id A376A34031; Fri, 14 Oct 2005 17:54:49 +0900 (JST)
Date: Fri, 14 Oct 2005 17:38:57 +0900
From: Horms <horms@debian.org>
To: 271699-done@bugs.debian.org
Cc: 328424-quiet@bugs.debian.org
Subject: kernel-image-2.4.26-1-686: update does not run lilo
Message-ID: <20051014083857.GB19862@verge.net.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Cluestick: seven
User-Agent: Mutt/1.5.11
Delivered-To: 271699-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
This is now being handled as #328424
--
Horms
Reply to: