From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] editing device_table_dev.txt
Date: Sun, 24 Feb 2013 19:11:00 +0100 [thread overview]
Message-ID: <877glxbn0r.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20130224182620.2283ceb3@skate> (Thomas Petazzoni's message of "Sun, 24 Feb 2013 18:26:20 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>> Turns out that mdev still does device node creation. Makes me
>> wonder if I'm not mistaken about udev as well... I just remember
>> hearing that device node creation was removed when DEVTMPFS was
>> introduced.
Thomas> Yes, I think you got the thing wrong: udev and mdev are still
Thomas> creating the device nodes. Of course, they might have already
Thomas> been created by devtmpfs, but I don't think it is a
Thomas> requirement. At least, devtmpfs is definitely not a requirement
Thomas> for mdev to work (except in Buildroot, in which we made the
Thomas> decision that if mdev is to be used, then devtmpfs support must
Thomas> be there).
And the main reason for this is that you need a writable /dev and basic
device nodes before mdev starts up, and the simplest way of getting this
is using devtmpfs.
What mdev/udev buys you over pure devtmpfs is the possibility of custom
rules (names/permissions/programs executed).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-02-24 18:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 23:37 [Buildroot] editing device_table_dev.txt John Stile
2013-02-21 10:14 ` Stefan Fröberg
2013-02-21 10:21 ` Stefan Fröberg
2013-02-21 10:23 ` Baruch Siach
2013-02-21 10:32 ` Stefan Fröberg
2013-02-21 22:57 ` Arnout Vandecappelle
2013-02-21 23:07 ` Stefan Fröberg
2013-02-21 23:24 ` Arnout Vandecappelle
2013-02-21 23:32 ` Stefan Fröberg
2013-02-23 9:30 ` Arnout Vandecappelle
2013-02-23 11:18 ` Stefan Fröberg
2013-02-24 17:26 ` Thomas Petazzoni
2013-02-24 18:11 ` Peter Korsgaard [this message]
2013-02-24 17:24 ` Thomas Petazzoni
2013-02-21 23:14 ` Arnout Vandecappelle
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=877glxbn0r.fsf@dell.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