On Sun, 2020-09-27 at 14:37 -0500, DJ Lucas via blfs-support wrote: > > On 9/27/2020 6:45 AM, Alexey Orishko via blfs-support wrote: > > Hi guys, > > > > Every time I use mkinitramfs I get a warning on the screen: > > Creating initrd.img-5.8.11... ln: failed to create symbolic link > > '/tmp/initrd-work.dIMxI8Ugai/bin/sh': File exists > > done. > > Image created is fully functional. > > > > I added ls commands in the script to check the reason before ln > > command: > > ls /tmp/initrd-work.dIMxI8Ugai/bin/sh > > -rwxr-xr-x 1 root root 3785752 Sep 27 13:39 /tmp/initrd- > > work.dIMxI8Ugai/bin/sh > > ls /bin/bash > > -rwxr-xr-x 1 root root 3785752 Sep 5 21:44 /bin/bash > > > > Both sh and original bash are the same. Do we really need command > > below? > > line 136: ln -s bash $WDIR/bin/sh > > > > /Alexey > > > > I ran into this when writing the modular mkinitramfs script that I am > working on and forgot about it. I believe the correct fix is to > remove 'sh' from $binfiles (let it create the link and not waste the > tiny bit of space in the archive). >
Looks like I've added that recently (in May, as I've been reminded privately). Not sure why... And some other parts of the change look like an inadvertent commit, and were reverted a few days later. But as DJ said, it'd be better to remove sh from $binfiles, and keep the link. Let me fix that. Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
