From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] Howto change group of /dev/snd when using devtmpfs
Date: Fri, 24 Mar 2017 08:52:19 +0100 [thread overview]
Message-ID: <1490341939.3829.1.camel@embedded.rocks> (raw)
In-Reply-To: <8bf1cfe0-1811-d0b9-69f6-f26877a95f06@mind.be>
Hi Arnout,
On Thu, 2017-03-23 at 21:38 +0100, Arnout Vandecappelle wrote:
>
> On 23-03-17 18:22, J?rg Krause wrote:
> > Hi,
> >
> > I need some help to get the group changed for "/dev/snd" when using
> > devtmpfs. By default, "/dev/snd" and subnodes have the following
> > settings:
> >
> > """
> > # ls -l /dev/snd/
> > total 0
> > crw-------????1 root?????root??????116,???0 Jan??1??1970 controlC0
> > crw-------????1 root?????root??????116,??16 Jan??1??1970 pcmC0D0p
> > crw-------????1 root?????root??????116,??25 Jan??1??1970 pcmC0D1c
> > crw-------????1 root?????root??????116,??33 Jan??1??1970 timer
> > """
> >
> > I'd like to change the group to audio.
>
> ?That's exactly what mdev and (e)udev are meant for. devtmpfs creates
> device
> nodes automatically but only with defaults (default names, default
> user/group,
> default permissions). If you want to change anything, you need a
> helper.
>
> ?Of course, you can also write a script as /sbin/hotplug. But then I
> wonder why
> not use mdev - it hardly increases the busybox size.
Thanks! I tried mdev before, but it didn't work. After some digging I
found that the mdev.conf in Buildroot is outdated, because the syntax
changed?[1] in Busybox 1.23.
Strange, that nobody noticed this for two years...
[1] http://lists.busybox.net/pipermail/busybox/2015-February/082297.htm
l
J?rg
prev parent reply other threads:[~2017-03-24 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 17:22 [Buildroot] Howto change group of /dev/snd when using devtmpfs Jörg Krause
2017-03-23 20:38 ` Arnout Vandecappelle
2017-03-24 7:52 ` Jörg Krause [this message]
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=1490341939.3829.1.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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