On 9/9/26 15:45, Benjamin Drung wrote:
Ubuntu is shipping busybox-static by default (the ubuntu-standard
depends on it). Archaeology found the reason for it:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/505887
Summary from the bug: If e.g. libc is broken a stock ubuntu system can
currently not be booted. With busybox-static installed on the system,
users could boot with "init=/bin/busybox sh" to be able do recovery.
But for this, wouldn't it be better to boot with rd.break to stop at the
end of the initrd? Then users have full access to their system (they
could chroot into it), but still be able to use all the working tools
inside the initrd?
Personally I don't see value of having busybox-static in initrd at all.
And yes, when initrd contains busybox binary, that one can be used to
explore the system in case of some problem. Again, even there, it is
much, much more common to use some live media to boot and do stuff from
there, having all tools available.
I'd switch back to regular busybox in this case.
And I never liked that busybox-static in ubuntu initrd.
BTW, in order to do that others are proposing (renaming binary to
busybox-static and dropping the initrd hook), we should switch to
regular busybox in ubuntu first :)
Thanks,
/mjt
