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 EE85E1381F4 for ; Fri, 17 Aug 2012 09:50:02 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E8D3EE07AD; Fri, 17 Aug 2012 09:48:53 +0000 (UTC) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by pigeon.gentoo.org (Postfix) with SMTP id 1CB04E07A1 for ; Fri, 17 Aug 2012 09:40:58 +0000 (UTC) Received: (qmail invoked by alias); 17 Aug 2012 09:40:58 -0000 Received: from 77-23-33-134-dynip.superkabel.de (EHLO marcec.hunte.us) [77.23.33.134] by mail.gmx.net (mp010) with SMTP; 17 Aug 2012 11:40:58 +0200 X-Authenticated: #38048819 X-Provags-ID: V01U2FsdGVkX1+R1LsHEX2RzGwwE0RfoC9+fQIFZ1q4iIkXpiPNAA Bz2opVC48s6PVW Date: Fri, 17 Aug 2012 11:40:47 +0200 From: Marc Joliet To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] /dev/snd/seq access mode and permission Message-ID: <20120817114047.551dfab9@marcec.hunte.us> In-Reply-To: <20120817015434.A25AFA4C@m0005299.ppops.net> References: <20120817015434.A25AFA4C@m0005299.ppops.net> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) 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: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/zasN_1SiQ/G/6L_DxGIMQTc"; protocol="application/pgp-signature" X-Y-GMX-Trusted: 0 X-Archives-Salt: cb25193e-49f4-4f7c-86b5-dab29c1aa118 X-Archives-Hash: 92cc35a61300aa156f6da9963a5814b6 --Sig_/zasN_1SiQ/G/6L_DxGIMQTc Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable 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 e= very boot to make it accessible to my user. the other nodes are fine. Here'= s the output of ls -l /dev/snd/ >=20 > 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 >=20 > I need /dev/snd/seq to look look the others. I can't find the udev rule o= r 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 cor= rect 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 s= hould be of help there. HTH --=20 Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup --Sig_/zasN_1SiQ/G/6L_DxGIMQTc Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlAuEakACgkQBsMBz3L8+WNOEwCfckFVboET+RwLszu8ZqoSkwUw hIMAn0KjJlJFnnzKf6zt1dMrHKbcOvTo =UPBM -----END PGP SIGNATURE----- --Sig_/zasN_1SiQ/G/6L_DxGIMQTc--