Bug#545064: initramfs-tools: "update-initramfs" fails to include "/lib/libc.so.6" and "/lib/libm.so"
[ keep bug report on cc, this is not a private conversation, thanks ]
On Sun, 06 Sep 2009, Christoph Franzen wrote:
> Am Sat, 5 Sep 2009 17:32:30 +0200 schrieb maximilian attems
> <max@stro.at>:
>
> Hello, your native language seems to be german like mine, so if you
> want to know something specific which might be hard to explain, we can
> speak german as well to make things more clear.
mapping the tld to the native language of it's owner is likely faulty.
> On Fri, Sep 04, 2009 at 08:11:10PM +0200, Christoph Franzen wrote:
> > >
> > > Whenever a new RAM disk is created (for instance with
> > > "update-initramfs -u -k all"), the above mentioned "libc" files are
> > > missing in the image.
> >
> > no evidence was brought forward, post the output of
> > sh -x mkinitramfs -o /dev/null
>
> You'll find the requested output at the end of this message.
>
> I've taken a look into the image with "midnight commander" before I
> posted the bug report, among others I found the following file:
>
> /boot/initrd.img-2.6.26-2-686.cpio.gz#ucpio/lib
> *klibc--IOwh0VR87LX1LY95rmnFLc1vuY.so
>
> but no "libm.so" and no "libc.so.6" (and no symlinks with these names).
fishy indeed.
> I found a different behaviour when booting depending on busybox or
> busybox-static being installed, so I test this first:
>
> # dpkg -s busybox-static
> Package: busybox-static
> Status: install ok installed
> [...]
> Architecture: i386
> Source: busybox
> Version: 1:1.10.2-2
> Replaces: busybox
> Conflicts: busybox
> [...]
> # dpkg -s busybox
> Package: busybox
> Status: purge ok not-installed
> [...]
>
> I had a backup of the ramdisk image for some 2.6.x (x<26) kernels, the
> only 2.6.26 was this BPO kernel:
>
> # uname -a
> Linux bormo 2.6.26-bpo.1-686 #1 SMP Sat Sep 20 16:54:19 UTC 2008 i686 GNU/Linux
>
> I've chosen to boot this one, and I did not want to reboot my
> server for this test with another older Etch kernel, but I can assure
> you that the failure happens independently from the kernel version
> whether it is an "official" one or not.
>
> However, I can try to recreate RAM disks for any of the following if you
> want:
>
> # ls -l /boot/vmlinuz-2.6.*
> -rw-r--r-- 1 root root 1260371 24. Dez 2007 /boot/vmlinuz-2.6.18-5-686
> -rw-r--r-- 1 root root 1261443 27. Dez 2008 /boot/vmlinuz-2.6.18-6-686
> -rw-r--r-- 1 root root 1359600 4. Dez 2007 /boot/vmlinuz-2.6.22-3-686
> -rw-r--r-- 1 root root 1360112 13. Feb 2008 /boot/vmlinuz-2.6.22-4-686
> -rw-r--r-- 1 root root 1455736 5. Jun 2008 /boot/vmlinuz-2.6.24-1-686
> -rw-r--r-- 1 root root 1456344 26. Dez 2008 /boot/vmlinuz-2.6.24-etchnhalf.1-686
> -rw-r--r-- 1 root root 1484416 28. Jun 2008 /boot/vmlinuz-2.6.25-2-686
> -rw-r--r-- 1 root root 1506512 13. Mär 23:36 /boot/vmlinuz-2.6.26-1-686
> -rw-r--r-- 1 root root 1506064 14. Aug 07:03 /boot/vmlinuz-2.6.26-2-686
> -rw-r--r-- 1 root root 1505520 21. Sep 2008 /boot/vmlinuz-2.6.26-bpo.1-686
>
> In fact, any RAM disk I created after december/january has been faulty,
> and I think to have found evidence that the problem is the last update
> of "initramfs-tools" in january or february to 0.92o.
what did you change at that time?
> + final_destination=/tmp/mkinitramfs_zWmdAH//sbin/modprobe
> + '[' -L /tmp/mkinitramfs_zWmdAH//sbin/modprobe ']'
> + ln -s /sbin/modprobe /tmp/mkinitramfs_zWmdAH//sbin/modprobe
> + '[' n = y ']'
> ++ ldd /sbin/modprobe
> ++ sed -e '
> /\//!d;
> /linux-gate/d;
> /=>/ {s/.*=>[[:blank:]]*\([^[:blank:]]*\).*/\1/};
> s/[[:blank:]]*\([^[:blank:]]*\) (.*)/\1/'
> + for x in '$(ldd ${source} 2>/dev/null | sed -e '\''
> /\//!d;
> /linux-gate/d;
> /=>/ {s/.*=>[[:blank:]]*\([^[:blank:]]*\).*/\1/};
> s/[[:blank:]]*\([^[:blank:]]*\) (.*)/\1/'\'' 2>/dev/null)'
> ++ sed -e 's#/lib/\(tls\|i686\).*/\(lib.*\)#/lib/\2#'
> ++ echo /usr/local/lib/i686/cmov/libc.so.6
> + nonoptlib=/usr/local/lib/libc.so.6
you seem to have a funny place for your local libc package
what shows belows?
dpkg -l libc6
Reply to: