From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lindsay Haisley Date: Mon, 20 Dec 2004 23:36:09 +0000 Subject: Re: udev: remove permissions file from udev Message-Id: <20041220233609.GK25934@fmp.com> 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 Thus spake Kay Sievers on Mon, Dec 20, 2004 at 02:30:22PM CST > > 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). I figured this out, but had to go exploring in /sys to get a clue. Even a better doc on this would help. > 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. Yeah, this is really needed for sure for SYSFS terms in a rules file, and you're quite right about getting this information from /sys being relatively trivial, assuming one understands something about the structure of the sysfs file system. > udevinfo already prints BUS= and ID= so you may add the KERNEL=, > DRIVER=, SUBSYSTEM= keys there if you think that is useful. It's simply a matter of convenience. It wasn't very long ago that I started using devfs and had to learn devfs rules files. Now we've moved on to udev/sysfs, and it's new tech - different data structurs, different config files. Being able to get everything one needs to compose working udev rules from a single utility, without having to learn the structure of and explore /sys, is majorly convenient. It's just polish, but people do wax and polish their cars ;-) -- Lindsay Haisley | "Fighting against human | PGP public key FMP Computer Services | creativity is like | available at 512-259-1190 | trying to eradicate | http://www.fmp.com | dandelions" | | (Pamela Jones) | ------------------------------------------------------- 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