From: Andreas Jellinghaus <aj@ciphirelabs.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Ordering hotplug scripts vs. udev device node creation
Date: Sat, 21 Oct 2006 20:36:00 +0200 [thread overview]
Message-ID: <453A6890.5030803@ciphirelabs.com> (raw)
In-Reply-To: <727e50150610211021s7779b787s7bac8f409a3f2518@mail.gmail.com>
not sure, I ran into the same problem with usb device files
(both in /proc and /dev/bus/usb). and my quick hack was to simply
add a "sleep 1".
but there might be a cleaner solution:
with udevmonitor you should see what udev does, and it should
give you the name of the device it creates, so the call to udevinfo
should not be needed. and when that event with the device name
comes in - at least I hope - udev has already created it.
(at least I think it would be right if it creates a file to fire
the event associated with doing that after the mknod.)
maybe give it a try. reporting back here (or on the hotplug mailing
list which might be more appropriate) would be very welcome, as you
are not the only one running into these kind of problems.
good luck!
Andreas
next prev parent reply other threads:[~2006-10-21 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-21 17:21 Aaron Cohen
2006-10-21 18:36 ` Andreas Jellinghaus [this message]
2006-10-22 18:49 ` Alistair John Strachan
2006-10-23 19:26 Aaron Cohen
2006-10-24 2:45 ` 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=453A6890.5030803@ciphirelabs.com \
--to=aj@ciphirelabs.com \
--cc=linux-kernel@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
Powered by JetHome