[PATCH] Re-enable busybox init

Richard Maw richard.maw at codethink.co.uk
Wed Oct 16 17:04:57 BST 2013


On Wed, Oct 16, 2013 at 04:25:01PM +0100, Lars Wirzenius wrote:
> On Tue, Oct 15, 2013 at 11:55:40AM +0100, Richard Maw wrote:
> > Repo: git://git.baserock.org/delta/busybox.git
> > Ref:  baserock/richardmaw/S9245/init
> > SHA1: 655dd910318f239f291302196296a5b9a4ab6081
> > Land: origin/baserock/build-essential
> > 
> > This re-enables busybox init, so a custom write extension with a system
> > not including foundation is bootable with a reasonable init.
> 
> With this change, will the busybox chunk artifact end up providing
> /sbin/init? If so, I'd like to avoid that.

No. I expected it to have done so, but it appears to have not.

Even if it did, the symlinks would be replaced by systemd.

> I am in favour, however, of enabling pretty much everything in busybox,
> but only providing symlinks to the busybox binary for a subset of
> them. This would allow configuration extensions, for example, to add
> symlinks when needed.

We could configure busybox to install all its symlinks in /bin and /sbin,
then anything which replaces a busybox version of a command with a more
featured one could be installed in /usr/bin or /usr/sbin.



More information about the baserock-dev mailing list