[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#369966: marked as done (kernel-image-2.6: Unusable initrd.img is generated when /dev/null is a regular file)

Your message dated Fri, 2 Jun 2006 12:53:44 -0700
with message-id <20060602195343.GD9869@mauritius.dodds.net>
and subject line Bug#369966: kernel-image-2.6: Unusable initrd.img is generated when /dev/null is a regular file
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: kernel-image-2.6
Severity: grave
Justification: renders package unusable

When the configuration creates the initrd.img file it seems to copy the 
/dev/null to the cramfs file. But if the system contains a wrong 
/dev/null the generated initrd.img is unusable.

The problem seems to be in the fact that some of the scripts in the 
initrd.img relies on /dev/null and if that isn't a device they fail 
aborting the boot process (kernel panic attempting to kill init or 
something like that).

I know that /dev/null should be a device and I don't know how it became
a regular file, but the initrd.img should be created with a proper 
/dev/null device even when the system have a bogus one. That's because
the system can work (with small glitches) but the kernel won't boot
if the initrd.img contains it.

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-3-k7
Locale: LANG=es_AR, LC_CTYPE=es_AR (charmap=ISO-8859-1) (ignored: LC_ALL set to es_AR)

--- End Message ---
--- Begin Message --- 
On Fri, Jun 02, 2006 at 12:16:47PM -0300, Salvador E. Tropea wrote:
> Package: kernel-image-2.6
> Severity: grave
> Justification: renders package unusable

> When the configuration creates the initrd.img file it seems to copy the 
> /dev/null to the cramfs file. But if the system contains a wrong 
> /dev/null the generated initrd.img is unusable.

> The problem seems to be in the fact that some of the scripts in the 
> initrd.img relies on /dev/null and if that isn't a device they fail 
> aborting the boot process (kernel panic attempting to kill init or 
> something like that).

> I know that /dev/null should be a device and I don't know how it became
> a regular file, but the initrd.img should be created with a proper 
> /dev/null device even when the system have a bogus one. That's because
> the system can work (with small glitches) but the kernel won't boot
> if the initrd.img contains it.

I don't think this is a bug at all, except in your broken system.  It's not
reasonable to expect all packages to work around a completely broken
/dev/null.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: