Re: baselayout-2, busybox and uclibc
Hi,
I just want to give some feedback how far I'm with this. The base system
is quite minimal, only busybox, uclibc, and baselayout-2 is used.
Installation of every dependency of baselayout-2 is "blocked" in
/etc/portage/profile/package.provided. The system is booting quite fast
even with slow bios (did not use stop watch, but it is below 10 secs
including bios, which takes more than 3 secs). I use now busybox init
with special boot script to get it running with gentoo runlevels. There
seems to be a bug with bb init and PPID of processes (I will post this
on bb list), but it is not serious (at least I think so). As I wrote
earlier, a correct entry in fstab for rootfs is important (option
noauto), otherwise there will be an error message or even a broken
double mount on /. Consolefont and keymap is set with bb tools (keymap
file was created with bb dumpkmap). One error I overlooked up until 3
days ago was with checking the file systems. baselayout-2 expects
fsck.ext2 (e.g. for my boot partition), but bb provides e2fsck. There
seems also to be a bug with bb grep, which I will post on bb list, too
(try busybox grep -Fow usbfs /proc/filesystems). I'm using now a modular
kernel, because I plan to use lirc in the future, which provides kernel
modules. To be sure to have correct configuration files for modules
(e.g. /etc/modules.d/*), you have to run update-modules from
module-init-tools, which is a bash script. This command is also called
by the modules init script. Since I do not have bash in my embedded
system, calling this script results in an error. Therefore I have to run
it in my build system (linked my embedded /etc to my build /etc).
One thing I'm still working on is proper use of mdev. Thanks to
alpine-baselayout from Natanael, I have now a better idea how to do this.
(Continue reading)
RSS Feed