From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] editing device_table_dev.txt
Date: Fri, 22 Feb 2013 01:07:51 +0200 [thread overview]
Message-ID: <5126A8C7.2000009@petroprogram.com> (raw)
In-Reply-To: <5126A675.2060308@mind.be>
22.2.2013 0:57, Arnout Vandecappelle kirjoitti:
> On 21/02/13 11:32, Stefan Fr?berg wrote:
>>>>> >>>Also kernel .config file should also have CONFIG_DEVTMPFS and
>>>>> DEVTMPFS
>>>>> >>>as 'y'.
>>>> >>Sorry, that should have been CONFIG_DEVTMPFS=y and
>>>> CONFIG_DEVTMPFS_MOUNT=y
>>> >Kernel version 2.6.30 is too old for that.
>>> >
>>> >baruch
>>> >
>> It is ?
>> Damn, then the only options are mdev and udev.
>
> I'm afraid that mdev and udev no longer work with old kernels that
> don't support the DEVTMPFS option...
>
> mdev and udev don't create device nodes; they only do something
> configurable when a hotplug event happens.
>
What you mean that mdev or udev does not create device nodes ???
If older kernels don't support devtmpfs like Baruch
said then who does that device node creation if not the mdev or udev
when event happens ???
> That said, you can create custom mdev/udev rules to create device
> nodes. But it's all manual - and much simpler to just create the
> device nodes manually.
>
for mdev it's just a single file, /etc/mdev.conf (I can even copy-paste
it here, it's not that long and will cover 99% of needs).
for udev it punch of rules found under /lib/udev/rules.d and yes, it can
get really tedious to play games with those files if some device node is
not created or
is not created with right permissions or whatever.
> Regards,
> Arnout
>
Regards
Stefan
/etc/mdev.conf
# null may already exist; therefore ownership has to be changed with command
null root:root 666 @chmod 666 $MDEV
zero root:root 666
full root:root 666
random root:root 444
urandom root:root 444
hwrandom root:root 444
grsec root:root 660
kmem root:root 640
mem root:root 640
port root:root 640
# console may already exist; therefore ownership has to be changed with
command
console root:tty 600 @chmod 600 $MDEV
ptmx root:tty 666
pty.* root:tty 660
# Typical devices
tty root:tty 666
tty[0-9]* root:tty 660
vcsa*[0-9]* root:tty 660
ttyS[0-9]* root:root 660
# alsa sound devices
pcm.* root:audio 660 =snd/
control.* root:audio 660 =snd/
midi.* root:audio 660 =snd/
seq root:audio 660 =snd/
timer root:audio 660 =snd/
# input stuff
event[0-9]+ root:root 640 =input/
mice root:root 640 =input/
mouse[0-9] root:root 640 =input/
ts[0-9] root:root 600 =input/
#
#sr[0-9] root:cdrom 660 *ln -sf $MDEV cdrom
sr[0-9] root:root 660 *ln -sf $MDEV cdrom
next prev parent reply other threads:[~2013-02-21 23:07 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 [this message]
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
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=5126A8C7.2000009@petroprogram.com \
--to=stefan.froberg@petroprogram.com \
--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