Hi Ben,
Ben Hutchings wrote:
> > /etc/kernel/postinst.d/initramfs-tools:
> > update-initramfs: Generating /boot/initrd.img-4.19.0-4-686-pae
> > cp: failed to access '/var/tmp/mkinitramfs_URATxd//usr/bin/touch': Too many
> > levels of symbolic links
> > E:
On Wed, 2019-05-08 at 00:27 +0200, Axel Beckert wrote:
> Hi,
>
> > cp: failed to access '/var/tmp/mkinitramfs_mSMoqa//usr/bin/busybox': Too
> > many levels of symbolic links
> > E: /usr/share/initramfs-tools/hooks/zz-busybox failed with return 1.
>
> I'm having a very similar issue which makes
Hi,
> cp: failed to access '/var/tmp/mkinitramfs_mSMoqa//usr/bin/busybox': Too many
> levels of symbolic links
> E: /usr/share/initramfs-tools/hooks/zz-busybox failed with return 1.
I'm having a very similar issue which makes me think that this is a
more generic issue and not necessarily
Hi Ben,
> > Any ideas? Sounds very usrmerge related... Setting severity to
> > "important" as I'm a little worried to reboot. :)
After the aforementioned purge-and-reinstall I rebooted and everything
appears to be fine. :)
> The file copying function it uses knows how to copy symlinks along
On Fri, 2018-12-07 at 09:43 +0100, Chris Lamb wrote:
[...]
> $ sudo update-initramfs -u -k all -v
[...]
> Calling hook zz-busybox
> Adding binary-link /bin/busybox
> Adding binary /usr/bin/busybox
> cp: failed to access '/var/tmp/mkinitramfs_mSMoqa//usr/bin/busybox':
Hi Chris,
> Well your symlink in /bin was dated 2018-11-26 17:23.
Ah, good spot!
> Your purge/reinstall could well fix it, just double-check you haven't
> ended up with *both* /bin/busybox and /usr/bin/busybox. You should have
> only the former and should be able to safely remove
On 07/12/2018 12:27, Chris Lamb wrote:
> tags 915830 + moreinfo
> severity 915830 normal
> thanks
>
> Chris Lamb wrote:
>
>> Well, I did attempt a usrmerge on this system; did it perhaps break
>> halfway through?
>
> Purging and re-installing busybox fixed this for me; shall I close
> this bug?
Processing commands for cont...@bugs.debian.org:
> tags 915830 + moreinfo
Bug #915830 [busybox] busybox: cp: failed to access
'/var/tmp/mkinitramfs_h8da2B//usr/bin/busybox': Too many levels of symbolic
links
Added tag(s) moreinfo.
> severity 915830 normal
Bug #915830 [busybox] busybox: cp:
tags 915830 + moreinfo
severity 915830 normal
thanks
Chris Lamb wrote:
> Well, I did attempt a usrmerge on this system; did it perhaps break
> halfway through?
Purging and re-installing busybox fixed this for me; shall I close
this bug?
(Downgrading and tagging for now...)
Regards,
--
Hi Chris,
> This is odd. The busybox package ships only a /bin/busybox binary, so
> I'm surprised to see your symlink to /usr/bin/busybox and the binary in
> there. Do you have any idea where that came from?
Well, I did attempt a usrmerge on this system; did it perhaps break
halfway through?
On 07/12/2018 08:43, Chris Lamb wrote:
> If it helps:
>
> $ ls -l /usr/bin | grep busybox
> -rwxr-xr-x 1 root root 654,048 2018-07-13 05:19 busybox
>
> $ ls -l /bin | grep busybox
> lrwxrwxrwx 1 root root 16 2018-11-26 17:23 busybox ->
Package: busybox
Version: 1:1.27.2-3
Severity: important
Hi,
Since a few days ago I am getting:
$ sudo update-initramfs -u -k all -v
Available versions: 4.18.0-2-amd64
Execute: /usr/sbin/update-initramfs -u -k "4.18.0-2-amd64" -b /boot -v
Keeping
12 matches
Mail list logo
