On 2008-02-06 16:02 +0100, Daniel Baumann wrote: > landing in the initramfs means, that the system was not beeing able to > mount the rootfs. > > that translates to one or more of the three following things: > > * you lack either unionfs-modules or aufs-modules, matching the kernel > you're booting.
packages.txt from the root of binary.img: ii aufs-modules-2.6.22-3-486 2.6.22+0+20071105-9 ii linux-image-2.6.22-3-486 2.6.22-6 > > * you lack squashfs-modules, matching the kernel you're booting. also from packages.txt: ii squashfs-modules-2.6.22-3-486 2.6.22+3.2r2-9 ii linux-image-2.6.22-3-486 2.6.22-6 > > * you're using aufs but have not specified union=aufs as bootparam, > or you're using unionfs but have not specified union-unionfs as > bootparam. I did try booting with union=aufs to no avail since live-initramfs is the default: ii live-initramfs 1.110.7-1 > > (in casper, unionfs is default; in live-initramfs, aufs is default, > so in your case, i would just state it explicit to be on the safe > side) I suspect that something changed between builds (I did have this working - but I made changes to the files that get copied to config/chroot_local-includes but that /shouldn't/ affect it). I will start tracking packages.txt between builds. -- Nick Golder _______________________________________________ debian-live-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-live-devel
