From: william estrada <MrUmunhum@popdial.com>
Cc: "alsa-user@lists.sourceforge.net"
<alsa-user@lists.sourceforge.net>,
linux-hotplug-devel@lists.sourceforge.net,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: chmod with USB sound device?
Date: Wed, 10 Oct 2007 10:42:23 -0700 [thread overview]
Message-ID: <470D0EFF.8030105@popdial.com> (raw)
In-Reply-To: <470CDA7D.1070701@redhat.com>
Harald,
I revisited /etc/security/console.perms.d/50-default.perms
and got it to work.
For the list, I changed:
In /etc/security/console.perms.d/50-default.perms
> # permission definitions
.
> <console> 0666 <sound> 0666 root
And
In /etc/udev/rules.d/50-udev.rules
> KERNEL=="snd/*", MODE="0666", OWNER="wre00:root"
Then I did the udevtrigger.
Then i did the udevtrigger, plugged in my USB sound device and got this:
> [root@laptop wre00]# ls -lrt /dev/snd
> total 0
> crw-rw-rw- 1 wre00 root 116, 2 Oct 10 09:45 timer
> crw-rw-rw- 1 wre00 root 116, 3 Oct 10 09:45 seq
> crw-rw-rw- 1 wre00 root 116, 4 Oct 10 09:45 pcmC0D0p
> crw-rw-rw- 1 wre00 root 116, 5 Oct 10 09:45 pcmC0D0c
> crw-rw-rw- 1 wre00 root 116, 6 Oct 10 09:45 controlC0
> crw-rw-rw- 1 wre00 root 116, 7 Oct 10 10:28 pcmC1D0p
> crw-rw-rw- 1 wre00 root 116, 8 Oct 10 10:28 pcmC1D0c
> crw-rw-rw- 1 wre00 root 116, 9 Oct 10 10:28 controlC1
I guess both changes are required but it now works.
Thanks for your time.
William Estrada
MrUmunhum@popdial.com
Mt-Umunhum-Wireless.net ( http://Mt-Umunhum-Wireless.net )
Ymessenger: MrUmunhum
Harald Hoyer wrote:
> william estrada wrote:
>> Hi guys,
>>
>> I'm trying to run 'chmod' on a USB sound card using 'Hot Plug' udev
>> support.
>> From reading, I think I need to update my
>> '/etc/udev/rules.d/50-udev.rules'?
>> I have made these changes:
>>> # audio devices
.
>>> KERNEL=="snd/*", MODE="0666"
>
> You may have a look in pam_console...
> /etc/security/console.perms
> /etc/security/console.perms.d/*
>
parent reply other threads:[~2007-10-10 17:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <470CDA7D.1070701@redhat.com>]
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=470D0EFF.8030105@popdial.com \
--to=mrumunhum@popdial.com \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@lists.sourceforge.net \
--cc=linux-hotplug-devel@lists.sourceforge.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