From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] devtmpfs and initramfs
Date: Wed, 20 Jul 2011 12:52:08 +0200 [thread overview]
Message-ID: <874o2h2pif.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <201107201057.48006.arnout@mind.be> (Arnout Vandecappelle's message of "Wed, 20 Jul 2011 10:57:47 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> > #!/bin/sh
>> > # devtmpfs does not get automounted for initramfs'es
>> > /bin/mount -t devtmpfs devtmpfs /dev
>> > exec /sbin/init $*
>> >
>> > Unless BR2_ROOTFS_DEVICE_CREATION_STATIC is enabled.
>>
>> Sorry, but this solution smells just like my socks. I think wk can find a
>> better one :)
Arnout> Yeah, I also would prefer not to proliferate the number of
Arnout> ways that the init process is influenced...
I don't see what there is to dislike. With this, the non-standard
behaviour of initramfs'es is nicely self contained within the initramfs
support code, and nothing else needs to know about it. There's nothing
to tweak, and it just works out of the box (tm), no matter what init
implementation or custom inittab is used.
You could argue that the shell overhead is a bit of a turn down, but
this is no worse than a S01mountall init script.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-07-20 10:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 10:22 [Buildroot] devtmpfs and initramfs Arnout Vandecappelle
2011-07-19 10:33 ` Peter Korsgaard
2011-07-19 11:23 ` Arnout Vandecappelle
2011-07-20 7:44 ` Diego Iastrubni
2011-07-20 8:01 ` Peter Korsgaard
2011-07-20 8:03 ` Arnout Vandecappelle
2011-07-20 8:15 ` Peter Korsgaard
2011-07-20 8:48 ` Diego Iastrubni
2011-07-20 8:57 ` Arnout Vandecappelle
2011-07-20 10:52 ` Peter Korsgaard [this message]
2011-07-20 11:00 ` Arnout Vandecappelle
2011-07-20 17:41 ` Peter Korsgaard
2011-07-20 15:10 ` Arnout Vandecappelle
2011-07-20 15:29 ` Peter Korsgaard
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=874o2h2pif.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox