All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lindsay Haisley <fmouse-gentoo@fmp.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev: remove permissions file from udev
Date: Mon, 20 Dec 2004 23:36:09 +0000	[thread overview]
Message-ID: <20041220233609.GK25934@fmp.com> (raw)
In-Reply-To: <1103476209.5746.19.camel@localhost.localdomain>

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://pubkeys.fmp.com>
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

  parent reply	other threads:[~2004-12-20 23:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-19 17:10 udev: remove permissions file from udev Kay Sievers
2004-12-19 17:31 ` Marco d'Itri
2004-12-19 17:36 ` Willem Riede
2004-12-19 17:49 ` Kay Sievers
2004-12-19 18:12 ` Kay Sievers
2004-12-19 19:57 ` Kay Sievers
2004-12-20  0:59 ` Marco d'Itri
2004-12-20  1:17 ` Kay Sievers
2004-12-20 13:36 ` Kay Sievers
2004-12-20 14:03 ` Marco d'Itri
2004-12-20 14:54 ` Kay Sievers
2004-12-20 17:13 ` Lindsay Haisley
2004-12-20 20:30 ` Kay Sievers
2004-12-20 20:49 ` Kay Sievers
2004-12-20 20:51 ` Marco d'Itri
2004-12-20 20:55 ` Kay Sievers
2004-12-20 20:58 ` Tobias Klauser
2004-12-20 23:36 ` Lindsay Haisley [this message]
2004-12-21  3:04 ` Kay Sievers
2004-12-22  3:41 ` Willem Riede
2004-12-22  6:18 ` Greg KH
2004-12-22 14:25 ` Willem Riede

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=20041220233609.GK25934@fmp.com \
    --to=fmouse-gentoo@fmp.com \
    --cc=linux-hotplug@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.