From: rutger@mail.com
To: linux-hotplug@vger.kernel.org
Subject: permissions of devices: modules vs. monolithic
Date: Tue, 04 May 2004 21:03:26 +0000 [thread overview]
Message-ID: <20040504210326.GA12129@mail.com> (raw)
Hi,
I've got two sound devices in my computer (SB-Live, which is card #0
and the on-board Intel ICH5 AC'97 is card #1). Since I want the order
fixed, I've got the SB-Live modules in the kernel, while the Intel
sound drivers are modularized. I do not need OSS emulation, so I don't
have any OSS devices. Relevant modules:
emu10k1_gp 2816 0
snd_intel8x0 28968 0
gameport 3840 2 emu10k1_gp,snd_intel8x0
snd_mpu401_uart 6144 1 snd_intel8x0
To be able for everyone in group 'audio' to use the sound cards, I've
got the following line in /etc/udev/udev.permissions:
snd/*:root:audio:0660
However, this doesn't work.
/dev/snd contains:
total 0
crw------- 1 root audio 116, 0 May 4 20:29 controlC0
crw-rw---- 1 root audio 116, 32 May 4 20:30 controlC1
crw------- 1 root audio 116, 4 May 4 20:29 hwC0D0
crw------- 1 root audio 116, 6 May 4 20:29 hwC0D2
crw------- 1 root audio 116, 8 May 4 20:29 midiC0D0
crw------- 1 root audio 116, 9 May 4 20:29 midiC0D1
crw------- 1 root audio 116, 10 May 4 20:29 midiC0D2
crw------- 1 root audio 116, 24 May 4 20:29 pcmC0D0c
crw------- 1 root audio 116, 16 May 4 20:29 pcmC0D0p
crw------- 1 root audio 116, 25 May 4 20:29 pcmC0D1c
crw------- 1 root audio 116, 26 May 4 20:29 pcmC0D2c
crw------- 1 root audio 116, 19 May 4 20:29 pcmC0D3p
crw-rw---- 1 root audio 116, 56 May 4 20:30 pcmC1D0c
crw-rw---- 1 root audio 116, 48 May 4 20:30 pcmC1D0p
crw-rw---- 1 root audio 116, 57 May 4 20:30 pcmC1D1c
crw-rw---- 1 root audio 116, 58 May 4 20:30 pcmC1D2c
crw-rw---- 1 root audio 116, 59 May 4 20:30 pcmC1D3c
crw-rw---- 1 root audio 116, 52 May 4 20:30 pcmC1D4p
crw------- 1 root audio 116, 1 May 4 20:29 seq
crw------- 1 root audio 116, 33 May 4 20:29 timer
So, for build-in modules, the permissions are not set! Is this
behaviour to be expected? How do I set the permissions for build-in
'modules'?
[More info:
uname -a:
Linux 2.6.6-rc2 #19 SMP Mon Apr 26 19:46:45 CEST 2004 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux
Distro: Gentoo ~x86; installed packages:
[I--] [ ] sys-apps/hotplug-base-20040401 (0)
[I--] [ ] sys-apps/hotplug-20040401 (0)
[I--] [ ] sys-fs/udev-025-r1 (0)
]
Thanks,
Rutger.
--
Rutger Nijlunsing ---------------------------- rutger ed tux tmfweb nl
never attribute to a conspiracy which can be explained by incompetence
----------------------------------------------------------------------
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_idÅ66&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2004-05-04 21:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040504210326.GA12129@mail.com \
--to=rutger@mail.com \
--cc=linux-hotplug@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.