From: Cinder <cinder@linuxwaves.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] /dev/snd/seq access mode and permission
Date: Fri, 17 Aug 2012 01:54:34 -0700 [thread overview]
Message-ID: <20120817015434.A25AFA4C@m0005299.ppops.net> (raw)
Hi, how do I make changes to permissions and access mode of device nodes persistent? At the moment I have to chown and chmod the /dev/snd/seq node every boot to make it accessible to my user. the other nodes are fine. Here's the output of ls -l /dev/snd/
total 0
drwxr-xr-x 2 root root 60 Aug 17 18:44 by-path
crw-rw----+ 1 root audio 116, 12 Aug 17 18:44 controlC0
crw-rw----+ 1 root audio 116, 11 Aug 17 18:44 hwC0D0
crw-rw----+ 1 root audio 116, 10 Aug 17 18:44 hwC0D3
crw-rw----+ 1 root audio 116, 9 Aug 17 18:44 hwC0D4
crw-rw----+ 1 root audio 116, 8 Aug 17 18:44 hwC0D5
crw-rw----+ 1 root audio 116, 7 Aug 17 18:44 pcmC0D0c
crw-rw----+ 1 root audio 116, 6 Aug 17 18:44 pcmC0D0p
crw-rw----+ 1 root audio 116, 5 Aug 17 18:44 pcmC0D1p
crw-rw----+ 1 root audio 116, 4 Aug 17 18:44 pcmC0D3p
crw-rw----+ 1 root audio 116, 3 Aug 17 18:44 pcmC0D7p
crw-rw----+ 1 root audio 116, 2 Aug 17 18:44 pcmC0D8p
crw------- 1 root root 116, 1 Aug 17 18:44 seq
crw-rw----+ 1 root audio 116, 33 Aug 17 18:44 timer
I need /dev/snd/seq to look look the others. I can't find the udev rule or configuration that creates these nodes. Many thanks for any consideration.
_____________________________________________________________
Get your FREE, LinuxWaves.com Email Now! --> http://www.LinuxWaves.com
Join Linux Discussions! --> http://Community.LinuxWaves.com
next reply other threads:[~2012-08-17 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 8:54 Cinder [this message]
2012-08-17 9:08 ` [gentoo-user] /dev/snd/seq access mode and permission Alan McKinnon
2012-08-17 9:40 ` Marc Joliet
2012-08-17 19:20 ` Marc Joliet
2012-08-17 16:35 ` Canek Peláez Valdés
-- strict thread matches above, loose matches on Subject: below --
2012-08-23 3:35 Cinder
2012-08-23 3:52 ` Bill Kenworthy
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=20120817015434.A25AFA4C@m0005299.ppops.net \
--to=cinder@linuxwaves.com \
--cc=gentoo-user@lists.gentoo.org \
/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