From: Mike Looijmans <mike.looijmans@topic.nl>
To: <andy.pont@sdcsystems.com>
Cc: yocto@yoctoproject.org
Subject: Re: Dumping sysvinit
Date: Mon, 21 Sep 2015 13:48:29 +0200 [thread overview]
Message-ID: <55FFEE8D.40001@topic.nl> (raw)
In-Reply-To: <00a001d0f45b$09ff9350$1dfeb9f0$@pont@sdcsystems.com>
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@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
prev parent reply other threads:[~2015-09-21 14:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 11:16 Dumping sysvinit Andy Pont
2015-09-15 13:53 ` Mark Hatle
2015-09-15 16:03 ` Andy Pont
[not found] ` <55f84188.e17c420a.cd394.2235SMTPIN_ADDED_BROKEN@mx.google.com>
2015-09-15 16:27 ` Trevor Woerner
2015-09-16 7:44 ` Burton, Ross
2015-09-16 9:24 ` Andy Pont
[not found] ` <55f9358a.44f2440a.38b16.7e0cSMTPIN_ADDED_BROKEN@mx.google.com>
2015-09-16 10:02 ` Burton, Ross
2015-09-16 14:13 ` Andy Pont
2015-09-17 7:16 ` Mike Looijmans
2015-09-21 10:48 ` Andy Pont
2015-09-21 11:48 ` Mike Looijmans [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55FFEE8D.40001@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=andy.pont@sdcsystems.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.