From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] devtmpfs and initramfs
Date: Wed, 20 Jul 2011 10:57:47 +0200 [thread overview]
Message-ID: <201107201057.48006.arnout@mind.be> (raw)
In-Reply-To: <CALR4fELkEBNtLS2WYXVkLkpttsMrzbHb04i+KZS+wfp3_TwMzQ@mail.gmail.com>
On Wednesday 20 July 2011 10:48:28, Diego Iastrubni wrote:
> > We could, or adjust initramfs.mk to add a small shellscript as /init
> > rather than just a symlink:
> >
> > #!/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 :)
Yeah, I also would prefer not to proliferate the number of ways that the init
process is influenced...
That said, the inittab solution isn't that good either. I guess there is a
reason why all distros have an S01mountall...
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
next prev parent reply other threads:[~2011-07-20 8:57 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 [this message]
2011-07-20 10:52 ` Peter Korsgaard
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=201107201057.48006.arnout@mind.be \
--to=arnout@mind.be \
--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 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.