[yocto] Dumping sysvinit

Mike Looijmans mike.looijmans at topic.nl
Mon Sep 21 04:48:29 PDT 2015


On 21-09-15 12:48, Andy Pont wrote:
> Hi Mike,
>
>>> Back to plan A then, trying to figure out how to get Busybox init and
>> mdev as the defaults in the image.
>>
>> Create your own distro, here's an example that uses mdev:
>>
>> https://github.com/topic-embedded-products/meta-
>> topic/blob/master/conf/distro/tiny.conf
>
> Thanks for pointing me in the direction of this.  I have cloned it and used
> it as the basis of my distro, tweaked it a bit and it is starting to behave
> how I want.  There are a few anomalies that I haven't managed to figure out
> yet...
>
> Despite having VIRTUAL-RUNTIME_initscripts = "" the root file system still
> contains /etc/rcX.d directories
>
> On other embedded Linux projects that boot using Busybox init the
> /etc/init.d directory contained the individual service start and kill files
> e.g. S50-dropbear and K50-dropbear but I can't see how to make Yocto
> populate this directory in that form.
>
> Thoughts and guidance from anyone would be much appreciated!

I didn't go as far as attempting to get rid of initscripts as well. I just 
patched the initscripts to remove the things I did not want in a 
do_install_append.

Many recipes will create /etc/rcX.d entries to start/stop things.



Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans at topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail








More information about the yocto mailing list