Bug#419378: marked as done (linux-image-2.6.18-4-xen-vserver-amd64: Can't update LILO: kernel image too big)
Your message dated Sun, 15 Apr 2007 17:40:40 +0200
with message-id <20070415154040.GA8557@wavehammer.waldi.eu.org>
and subject line Bug#419378: linux-image-2.6.18-4-xen-vserver-amd64: Can't update LILO: kernel image too big
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)
--- Begin Message ---
Package: linux-image-2.6.18-4-xen-vserver-amd64
Version: 2.6.18.dfsg.1-12
Severity: grave
Justification: renders package unusable
I installed this kernel image and received the following warning from LILO
(current stable version 1:22.6.1-9.3):
LILO: kernel image "/boot/vmlinuz" too big
Regardless of what I did, I couldn't get LILO to properly prepare the
kernel to be booted by it.
So I installed linux-image-2.6.18-4-amd64, version 2.6.18.dfsg.1-12,
and this one works properly with LILO.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (990, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-amd64
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
--- End Message ---
--- Begin Message ---
On Sun, Apr 15, 2007 at 02:24:55PM +0200, Ralf G. R. Bergs wrote:
> I installed this kernel image and received the following warning from LILO
> (current stable version 1:22.6.1-9.3):
Xen kernels needs to be loaded by xen. Also they don't create vmlinuz on
there one. No bug, closing.
Bastian
--
I've already got a female to worry about. Her name is the Enterprise.
-- Kirk, "The Corbomite Maneuver", stardate 1514.0
--- End Message ---
Reply to: