All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev: remove permissions file from udev
Date: Tue, 21 Dec 2004 03:04:26 +0000	[thread overview]
Message-ID: <1103598266.5435.112.camel@localhost.localdomain> (raw)
In-Reply-To: <1103476209.5746.19.camel@localhost.localdomain>

On Mon, 2004-12-20 at 17:36 -0600, Lindsay Haisley wrote:
> 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.

> > udevinfo already prints BUS= and ID= so you may add the KERNEL=,
> > DRIVER=, SUBSYSTEM= keys there if you think that is useful.

> 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 ;-)

That's what udevinfo is for. You may look at the output of:
  udevinfo -a -p <DEVPATH>

and
  udevinfo -s

to get an idea. I've added the -s option while I was working on
wait_for_sysfs. It's not generally useful and it may be nice to move
some of that functionality into the -a option to provide the user with
the full list of possible keys to paste into a rule.

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

  parent reply	other threads:[~2004-12-21  3:04 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
2004-12-21  3:04 ` Kay Sievers [this message]
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=1103598266.5435.112.camel@localhost.localdomain \
    --to=kay.sievers@vrfy.org \
    --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.