From: Andreas Jellinghaus <aj@dungeon.inka.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev/ubuntu problem solved
Date: Tue, 10 Jul 2007 15:46:57 +0000 [thread overview]
Message-ID: <200707101746.57406.aj@dungeon.inka.de> (raw)
In-Reply-To: <200707101653.31621.aj@dungeon.inka.de>
On Tuesday 10 July 2007 17:39:24 Kay Sievers wrote:
> What are theses guys smoking? That's so sick to bind-mount
> /dev-directories to /proc! I wouldn't support such a system at all. It
> is totally broken.
I was worried about that too. I guess they made that change so all
applications get the benefit of the ACL's in /dev/bus/usb without changes
to the source code (i.e. path adjustment).
> Are you using PROGRAM? That is for plugging external program into udev
> to give devices a name or symlink. If you use RUN+=, your program
> never runs before the node and all symlinks are created.
no I'm using RUN+= and I thought this would work the wy you described.
testing on ubuntu edgy (which has udev 108-0ubuntu4) shows this is different.
when I have my loop inside the script I RUN+= I can increase the timeout to 20
seconds, still it times out as the $DEVICE file is not there. if I have the
script start the loop in the background then it find the file after 100 ms
(one sleep).
maybe my diagnosis is a bit off: not the device file is created late, but the
DEVICE event is processed first, and the other events are in a queue in the
meantime till my RUN+= script is finished? and some other event triggers the
creation of /dev/bus/usb/NNN/NNN and it is processes after the event with
MODALIAS and DEVICE=/proc/bus/usb/NNN/NNN ? that would explain what I'm seing
too. is this explanation possible?
Thanks,
Andreas
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-07-10 15:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 14:53 udev/ubuntu problem solved Andreas Jellinghaus
2007-07-10 15:39 ` Kay Sievers
2007-07-10 15:46 ` Andreas Jellinghaus [this message]
2007-07-10 16:19 ` Kay Sievers
2007-07-11 7:32 ` Andreas Jellinghaus
2007-07-11 8:34 ` Scott James Remnant
2007-07-11 10:09 ` Kay Sievers
2007-07-12 0:35 ` Greg KH
2007-07-12 8:52 ` Scott James Remnant
2007-07-12 16:09 ` Greg KH
2007-07-12 16:58 ` Scott James Remnant
2007-07-12 18:37 ` Greg KH
2007-07-13 8:44 ` Scott James Remnant
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=200707101746.57406.aj@dungeon.inka.de \
--to=aj@dungeon.inka.de \
--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).