Hi, > does initramfs-tools boot with BUSYBOX=no in initramfs.conf?
Well, I don't know! Indeed, with BUSYBOX=no in initramfs.conf, initrd.img generation fails: root@longspeak:/# dpkg-reconfigure linux-image-3.0.0-1-mckinley Running depmod. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.0.0-1-mckinley /bo ot/vmlinuz-3.0.0-1-mckinley update-initramfs: Generating /boot/initrd.img-3.0.0-1-mckinley mv: cannot stat `/tmp/mkinitramfs_Z30F2f/bin/sh.shared': No such file or directo ry E: /usr/share/initramfs-tools/hooks/klibc failed with return 1. update-initramfs: failed for /boot/initrd.img-3.0.0-1-mckinley with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.0.0 -1-mckinley.postinst line 774. This is with initramfs-tools 0.99, as currently shipped in Testing. The same error occurs with source code currently in git. > according to your aboves statement it might not as the shared klibc > dash and not the static dash might end up in the initramfs? > see ls /usr/lib/klibc/bin OK, here's where the 199144 bytes bin/sh exec comes from (size matches /usr/lib/klibc/bin/sh exec). Thanks for pointing this out. More on this later... >> Applying patch proposed in bug #628374 (initramfs-tools: Recent >> changes to hooks break busybox in initrd) to revert changes on busybox >> hook doesn't help. >> >> Simply reverting commit 8f8299d9ba017d2a5af853a52be37ee50c89fac2 from >> initramfs-tools v0.99 source code doesn't help either as resulting >> initramfs-tools binaries generate initrd.img failing to boot system >> with kernel panic, probably because of >> post-8f8299d9ba017d2a5af853a52be37ee50c89fac2 commits. >> >> The problem is still present in current initramfs-tools git repository. > > are you sure? Well, yes, I'm sure that the generated initramfs is unbootable. That being said, I've bisected the first bad commit. It's also possible that following commits fixed this issue, but other ones make it appear again, maybe with a different root cause. > relevant apt source line is: > deb http://jenkins.grml.org/debian initramfs-tools main > > please test that one, thank you. Still unbootable initramfs with this one. And initrd.img creation fails with the same error than with 0.99 and git with BUSYBOX=no in initramfs.conf. However, with BUSYBOX=yes, initrd.img can be generated successfully. If I look at its content, ls -l bin/ gives: -rwxr-xr-x 1 root root 199144 Aug 17 22:05 busybox lrwxrwxrwx 1 root root 7 Aug 17 22:05 sh -> busybox Is it expected that bin/busybox in initramfs is in fact a copy of /usr/lib/klibc/bin/sh and not /bin/busybox? Indeed, ls -l on my system gives: -rwxr-xr-x 1 root root 1320720 Jul 25 16:17 /bin/busybox -rwxr-xr-x 1 root root 199144 Jul 27 17:32 /usr/lib/klibc/bin/sh Hope this helps, Émeric -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caa9xbm4iyey0dausjfhtvkis-fy9uqebm12g4mykuwoljpx...@mail.gmail.com
