From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] device_table & /dev/shm
Date: Sun, 26 Jun 2011 12:17:54 +0200 [thread overview]
Message-ID: <87mxh47v71.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110626032236.GA17733@tarshish> (Baruch Siach's message of "Sun, 26 Jun 2011 06:22:37 +0300")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
Hi,
>> 1. I can see the generic device_table.txt and it includes a /dev/shm
>> node. I can also see the /dev structure in output/target and it
>> matches the generic device_table.txt. But, ... when I build the jffs2
>> and load it on my MPC8323 target, what I see in /dev does not include
>> /dev/shm. In fact it is significantly different. So, my first question
>> is:
>>
>> "What besides generic/device_table.txt can determine the contents of
>> /dev on an MPC8323 target?"
Baruch> Do you have devtmpfs mounted on /dev? If so, devtmpfs takes
Baruch> over the content of /dev, and hides the device nodes and
Baruch> directories from your device table.
If so, it would be better to use the 'Dynamic using devmtpfs only'
device table option to not waste jffs2 space on device nodes you are not
going to use anyway.
We might need to add a mkdir -p /dev/shm in inittab like we already do
for /dev/pts, as those are not device nodes and hence do not get created
by devtmpfs.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-06-26 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-25 18:29 [Buildroot] device_table & /dev/shm Charles Krinke
2011-06-25 23:40 ` Khem Raj
2011-06-26 3:22 ` Baruch Siach
2011-06-26 10:17 ` Peter Korsgaard [this message]
2011-06-26 17:51 ` Charles Krinke
2011-06-27 3:32 ` Baruch Siach
2011-06-27 10:12 ` 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=87mxh47v71.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