From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and usb.agent
Date: Sat, 15 Oct 2005 18:27:30 +0000 [thread overview]
Message-ID: <20051015182730.GB7625@vrfy.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0510151611080.8404@terminal.gregs.com>
On Sat, Oct 15, 2005 at 04:14:29PM +1000, Greg Bell wrote:
>
> Hi Developers,
>
> On my FC4 system, hotplug calls /etc/hotplug/usb.agent (and therefore my
> /etc/hotplug/usb/camera script). However, it doesn't run udev until
> AFTER, so my /dev/sd?1 mapping to /dev/camera hasn't happened yet when my
> camera script is running.
>
> What am I doing wrong? Is there a way to get hotplug to call udev to do
> the device mapping BEFORE usb.agent gets called?
The "camera script" is probably triggered by the usb device event, not the
block device event. Use an explicit udev rule that matches the block device
and the usb properties of the camera. The old agent crap should no longer
be used.
Btw: HAL which should be running on your box is expected to manage that
in conjunction with your desktop session. Modern desktop setups don't
need to fiddle around with device id's and scripts to make your camera
just work.
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-15 18:27 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 [this message]
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
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=20051015182730.GB7625@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).