Bug#535513: daily fails to generate ramdisk because / not mounted
* Martin Michlmayr <tbm@cyrius.com> [2009-07-02 22:39]:
> I just tried a daily image on ARM and it failed because the ramdisk
> cannot be generated. Apparently this is because / is not mounted in
> the chroot.
The reason this only shows up on ARM is because it uses MODULES=dep
for initramfs-tools to generate the ramdisk and in this case
initramfs-tools looks for the root device; for MODULES=most (the
default) it just puts everything in the ramdisk.
I made a successful installation with
base-installer/initramfs-tools/driver-policy=most
and I guess you can reproduce this problem with =dep on x86.
I don't know why root is no longer mounted in the chroot (it was in
lenny and until recently in the daily images). Would busybox be
responsible for this or where should this bug be reassigned to?
--
Martin Michlmayr
http://www.cyrius.com/
Reply to: