From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 1C32C138010 for ; Thu, 23 Aug 2012 03:38:52 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A5446E0682; Thu, 23 Aug 2012 03:38:33 +0000 (UTC) Received: from imta-38.everyone.net (sitemail2.everyone.net [216.200.145.36]) by pigeon.gentoo.org (Postfix) with ESMTP id 603D5E078D for ; Thu, 23 Aug 2012 03:35:40 +0000 (UTC) Received: from pps.filterd (omta002 [127.0.0.1]) by imta-38.everyone.net (8.14.4/8.14.4) with SMTP id q7N3Zd8T026868 for ; Wed, 22 Aug 2012 20:35:39 -0700 X-Eon-Dm: dm23 Received: by resin03.mta.everyone.net (EON-PICKUP) id resin03.5035a487.5ae; Wed, 22 Aug 2012 20:35:34 -0700 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Message-Id: <20120822203534.518A9C4D@resin03.mta.everyone.net> Date: Wed, 22 Aug 2012 20:35:34 -0700 From: Cinder To: Subject: Re: [gentoo-user] /dev/snd/seq access mode and permission X-Eon-Sig: AQMX6pJQNaUGaj5pWwEAAAAB,c51eabbdba198b7797857740fe969225 X-Originating-Ip: 27.32.195.47 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.260,0.0.0000 definitions=2012-08-23_01:2012-08-22,2012-08-23,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=3 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1208220323 X-Archives-Salt: 589b41f4-c489-42bf-843b-3942e0c9a09f X-Archives-Hash: 130e54da3513d009053ad235664faabe I have tried creating this rule: /etc/udev/rules.d/40-seq.rules KERNEL=="snd/seq", GROUP="audio", MODE="0666" ...but I'm not sure about the kernel key pair. I have tried matching "/dev/snd/seq" and just "seq" aswell. The Bug 406871 for sys-fs/udev-171-r5 looks exactly right, butI have sys-fs/udev-171-r6 installed. I''l check my kernel config and try disabling tmpfs. I have read that it helps real time audio performanc with jack(audio-connection-kit)though. I have tried removing all the rules in /etc/udev/rules.d. but the mode and permissions on /dev/snd/seq persist. Thanks for everyones help. --- marcec@gmx.de wrote: From: Marc Joliet To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] /dev/snd/seq access mode and permission Date: Fri, 17 Aug 2012 21:20:08 +0200 Am Fri, 17 Aug 2012 11:40:47 +0200 schrieb Marc Joliet : > Am Fri, 17 Aug 2012 01:54:34 -0700 > schrieb Cinder : > > > 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. > > I have a hack for the same issue in my /etc/local.d/. A comment I put there > says this: > > # this is caused by using devtmpfs, which creates nodes with root:root and 600; > # I believe this is fixed by udev upstream > > So devtmpfs creates the device node before udev runs, but udev does not correct > the access permissions, which is however fixed by udev upstream (perhaps > already in ~arch?). Sadly I do not remember where I read this, but google should > be of help there. Ah, yes, I did a quick search on b.g.o and found this: https://bugs.gentoo.org/show_bug.cgi?id=406871 So my comment is wrong, it doesn't have anything to do with devtmpfs, but udev upstream did fix it :) . HTH -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup _____________________________________________________________ Get your FREE, LinuxWaves.com Email Now! --> http://www.LinuxWaves.com Join Linux Discussions! --> http://Community.LinuxWaves.com