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

Bug#472698: marked as done (initramfs-tools: fails to boot with busybox 1:1.9.2-1)

Your message dated Thu, 27 Mar 2008 05:26:38 -0700
with message-id <20080327122638.GH5297@ryukin.fglan>
and subject line initramfs-tools: works fine with busybox 1:1.9.2-2
has caused the Debian Bug report #472698,
regarding initramfs-tools: fails to boot with busybox 1:1.9.2-1
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

472698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472698
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.91e
Severity: important

i'm not sure if this should be filed on busybox or initramfs-tools.
maybe it should even be RC, as it can make at least some systems

when booting with two different systems (one using boot=nfs the other
using boot=local an an lvm root) they both fail with messages saying
various tools could not be found (mount, printf, tr, mknod and others):

 /scripts/init-top/framebuffer: line 100: mknod: not found
 /init: line 157 printf: not found

downgrading busybox to the version in testing (1.1.3-5) and regenerating
the initramfs images works around the problem. i'm not positive, but i
think it was working fine with whatever version of busybox was in
unstable on 2008-03-19.


live well,

--- End Message ---
--- Begin Message ---
tested with the new busybox 1:1.9.2-2, and everything works fine.

live well,

--- End Message ---

Reply to: