From: "Eric S. Raymond" <esr@thyrsus.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: New hotplug interface is not working right for me
Date: Fri, 11 Mar 2005 06:04:05 +0000 [thread overview]
Message-ID: <20050311060405.GA16141@thyrsus.com> (raw)
Greg KH <greg@kroah.com>:
> On Fri, Mar 11, 2005 at 12:20:54AM -0500, Eric S. Raymond wrote:
> > Greg KH <greg@kroah.com>:
> > > > The problem appears to be that whatever thread of control is creating
> > > > the /dev/ttyUSB* node is running asynchronously with the hotplug
> > > > script and does not reliably (or even usually) create it before the
> > > > gpsd instance gets spawned and goes looking for the node.
> > >
> > > Then use the /etc/dev.d/ interface instead. That requires udev and a
> > > 2.6 kernel, but is the only way you can know exactly when the /dev entry
> > > is created.
> >
> > Where is this documented?
>
> In the udev documentation and a simple google search brings it up.
>
> > Even if the /etc/dev.d/ interface works, that doesn't really make it
> > acceptable that the /etc/hotplug.d/ interface is broken. There is some
> > locking that ought to be happening and isn't.
>
> The interface is not broken, you are trying to trigger off of two
> different hotplug events (one when the device appears, and a different
> one when the device node is to be created.)
If it's not broken, then it's not documented either.
Or, at least, I don't see any documentation that tells me about a
second hotplug event when /dev/ttyUSB0 is created. Now, if I could
write a script that would fire on only only /dev/ttyUSB* creation events and
allow me to filter on the vendor/product ID, that would be fine -- those
are what I'm really interested in.
> Also, please don't restrict this to private email, all further responses
> should be on the linux-hotplug-devel mailing list.
Done.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
-------------------------------------------------------
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://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
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 reply other threads:[~2005-03-11 6:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 6:04 Eric S. Raymond [this message]
2005-03-11 6:45 ` New hotplug interface is not working right for me Greg KH
2005-03-11 8:54 ` Kay Sievers
2005-03-11 13:38 ` Eric S. Raymond
2005-03-11 14:16 ` Kay Sievers
2005-03-11 15:38 ` Hannes Reinecke
2005-03-11 15:40 ` Eric S. Raymond
2005-03-11 16:05 ` Kay Sievers
2005-03-11 17:03 ` Eric S. Raymond
2005-03-11 17:32 ` Kay Sievers
2005-03-11 18:58 ` Christian Zoz
2005-03-11 19:07 ` Eric S. Raymond
2005-03-11 20:35 ` Kay Sievers
2005-03-11 20:48 ` Eric S. Raymond
2005-03-14 17:06 ` Darren Salt
2005-03-14 18:16 ` Marco d'Itri
2005-03-14 18:25 ` 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=20050311060405.GA16141@thyrsus.com \
--to=esr@thyrsus.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.