Busybox #101
Busybox #101
Conversation
sixtyfourktec
force-pushed
the
busybox
branch
2 times, most recently
from
c9c7fa7 to
b2e352c
Compare
sixtyfourktec
force-pushed
the
busybox
branch
2 times, most recently
from
03758c9 to
f6fbf54
Compare
jkloetzke
left a comment
jkloetzke
left a comment
There was a problem hiding this comment.
I was wondering what the full enumeration of the allowed CONFIG_INIT values looks like. Obviously, it is at least sysvinit and systemd. I vaguely remember that we discussed that there might be differences between busybox and "full" sysv-init. Would it make sense to allow something like sysvinit/sysv and sysvinit/busybox and match in the recipes to sysvinit/*?
Don't try to make modifications to base files if the user didn't expressed its indent to do so. This removes the defaults of those options.
Done. I added a new "init" class dealing with this. I guess later on for e.g. systemd we will need this anyway. |
This creates a basic Linux directory/files setup using the merged /usr approach.
Add more options on how the config is gathered. Bring this in line with e.g. the linux kernel, where you could specify a custom package with a defconfig or a busybox defconfig or the standard defconfig. Note, the creation of debugging symbols now depends on the BASEMENT_DEBUG variable. If set, the CONFIG_DEBUG option is set automatically. Also only regenerate the .config if the source config has changed.
Also switch to explicit "if" statements, because otherwise we may miss some errors.
If udhcpc is enabled add a default script which does a basic config.
If the inittab feature is enabled, add a default one.
If enabled put some default init scripts into /etc/init.d.
Add some helper functions for dealing with different init systems. Right now only sysvinit from the sysv and busybox package are supported. Later we will add more, like systemd.
Also add a minimal /etc/network/interfaces file, so that ifupdown is happy when started.
|
Thanks! |
2 participants
No description provided.