BusyBox Strikes Again?
On Thursday 03 April 2008 05:39:13 Marco Amadori wrote:
> > mount()
> > {
> > # can loop mount files, klibc's mount cannot without first binding
> > # file to loop (block) device node with losetup
> > /bin/busybox mount "${@}"
> > return "${?}"
> > }
>
> I was hit yesterday by this bug too and...this is not the case of loop
> mounting; the "debug:" message above is misleading (and in fact the problem
> is not mounting the /dev/loop0 on //filesystem.squashfs, which is mounted,
> but mounting a tmpfs), I'm debugging exactly that and I will report a fix
> soon in a to be published git branch.
>
loop mounting is just one example to highlight that klibc-utils/mount
is -ne to busybox/mount.
Another example is readlink, where klibc don't support -f option.
This may not even be the cause of this _specific_ bug, but I mention it anyway.
Thanks, Kel.
Reply to: