From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Mon, 20 Dec 2004 20:30:22 +0000 Subject: Re: udev: remove permissions file from udev Message-Id: <1103574622.5435.64.camel@localhost.localdomain> List-Id: References: <1103476209.5746.19.camel@localhost.localdomain> In-Reply-To: <1103476209.5746.19.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Mon, 2004-12-20 at 11:13 -0600, Lindsay Haisley wrote: > Thus spake Kay Sievers on Mon, Dec 20, 2004 at 07:36:51AM CST > > Just an example how nice the permissions application can work now. The > > following line applies the "disk" group ownership to all block devices > > not catched by an earlier explicit rule. > > There is no longer the need to catch all the different node names of a > > device class. > > > > --- a/etc/udev/gentoo/udev.rules 2004-12-20 14:24:22 +01:00 > > +++ b/etc/udev/gentoo/udev.rules 2004-12-20 14:24:22 +01:00 > > @@ -207,6 +207,9 @@ > > # rem_ide devices > > KERNEL="microdrive*", NAME="%k", GROUP="disk" > > > > +# all block devices > > +SUBSYSTEM="block", NAME="%k", GROUP="disk" > > + > > # kbd devices > > KERNEL="kbd", NAME="%k", MODE="0664" > > If it hasn't been done, I'm going to lobby once again for the inclusion in > udev of a utility which will will parse the sysfs tree for acceptable values > for KERNEL and spit out copy 'n paste lines which are acceptable in a rules > file, much the way udevinfo does for SYSFS{*} terms. I corresponded with > Greg KH on this a while back and he suggested a simple shell script for > this, which I tweaked a bit and reposted. Such as script could also show > acceptable values for SUBSYSTEM. If it hasn't been done, and I get a moment > after the 1st of the year, I'll work on something and post it. Hmm, I don't know if this is really useful, as sysfs has well defined filenames you can list that with just "ls -1 /sys/class /sys/bus", which will print all possible subsystems (besides block). It's different from the sysfs _values_ which may be vendor defined and contain odd whitespaces and similar. That's why we have the udevinfo print. udevinfo already prints BUS= and ID= so you may add the KERNEL=, DRIVER=, SUBSYSTEM= keys there if you think that is useful. Thanks, Kay ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ 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