From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and usb.agent
Date: Mon, 17 Oct 2005 01:44:15 +0000 [thread overview]
Message-ID: <20051017014415.GA25090@vrfy.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0510151611080.8404@terminal.gregs.com>
On Mon, Oct 17, 2005 at 10:42:20AM +1000, Greg Bell wrote:
>
> >Catch up! udev does _all_ hotplug today.
>
> Oh, oops. OK I've done some more reading. However the FAQ at
> http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ
>
> ...says/implies that udev is for creating the /dev nodes and not much else
> because that's where devfs went wrong (trying to do too much). They even
> refer the reader to HAL for the fancier more desktopy stuff.
>
> I see the PROGRAM= feature, but it seems that's run before the dev node
> gets created, and is intended for using a script to figure out what the
> node should be named, rather than reacting after the node's been created.
PROGRAM is for naming the node and therefore runs before the node is
created. RUN is for postprocessing.
> Maybe I'm looking at a multiple line udev.rules entry. I'm used to the
> main part of the event matching being a BUS= or KERNEL=.
>
> My understanding of what goes on is:
>
> 1) device is plugged in
> 2) USB event occurs
> 3) udev or usb.agent inserts SCSI module (sr_mod)
> 4) SCSI event occurs
> 5) udev creates /dev/camera (my rule)
> 6) ??? reacts and runs script to automatically slurp pictures off, etc.
>
> Its step 6 I'm having trouble with.
Yeah, 6 runs along with 3, that's your trouble. :)
2 and 4 are different events, 2 will have finished before 4 even starts.
What you are looking for is 7, the block device event, which creates the
node.
Kay
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
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
next prev parent reply other threads:[~2005-10-17 1:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 6:14 udev and usb.agent Greg Bell
2005-10-15 18:27 ` Kay Sievers
2005-10-15 23:33 ` Greg Bell
2005-10-16 11:57 ` Kay Sievers
2005-10-17 0:42 ` Greg Bell
2005-10-17 1:44 ` Kay Sievers [this message]
2005-10-27 10:36 ` Olivier Blin
2005-10-28 1:09 ` Kay Sievers
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=20051017014415.GA25090@vrfy.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).