All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Michael <rmichael-hotplug@edgeofthenet.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: ENV{DEVNAME} in remove rule?
Date: Tue, 03 Jul 2007 18:17:52 +0000	[thread overview]
Message-ID: <20070703181752.GK27375@server> (raw)
In-Reply-To: <20070703171658.GB27375@server>

On Tue, Jul 03, 2007 at 10:06:08PM +0400, Andrey Borzenkov wrote:
> On Tuesday 03 July 2007, Richard Michael wrote:
> > > DEVNAME is set by udev before calling RUN programs. It is not available
> > > when rules are being processed.
> >
> > Where are these details documented? 
> 
> source code?

I thought so.  I think udev is great, it just needs slightly more helpful
documentation to make is really user accessible.  There are quite a few
"things to know" (such as the default PATH, which took awhile to
realize I was overlooking..).

> > I've been writing lots of test 
> > rules to try and figure this out, but I'd prefer to just read something.
> >
> 
> patches to manual pages are welcome :)

I was thinking about changes to the How To Write UDev Rules document..
 
> What's wrong with using ID_PATH? It also has advantage of being more stable 
> than PHYSDEVPATH (which includes volatile details like running SCSI host 
> number).

Yes, I noticed the target number changes even when the hardware remains
identical.

I thought I had a problem running path_id/usb_id to set those environment
variables (I don't remember which one sets them..), because the sysfs
entry was already gone.  I think I misunderstood, maybe the variables
are set from when the device was created? .. I'll look into again.  I'm
probably just confused, it's been a bit of mess building some
understanding.. :)

Thanks,
Richard

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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:[~2007-07-03 18:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03 17:16 ENV{DEVNAME} in remove rule? Richard Michael
2007-07-03 17:45 ` Andrey Borzenkov
2007-07-03 17:52 ` Richard Michael
2007-07-03 18:06 ` Andrey Borzenkov
2007-07-03 18:17 ` Richard Michael [this message]
2007-07-03 19:44 ` Andrey Borzenkov

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=20070703181752.GK27375@server \
    --to=rmichael-hotplug@edgeofthenet.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.