From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: usb + sysfs + udev problems once more
Date: Wed, 27 Jun 2007 16:02:59 +0000 [thread overview]
Message-ID: <46828A33.2090909@ums.usu.ru> (raw)
In-Reply-To: <200706271514.22408.aj@leogic.com>
Andreas Jellinghaus wrote:
> Am Mittwoch, 27. Juni 2007 16:35 schrieb Kay Sievers:
>> The usb-interfaces (2nd event) do not have a device node. Only the
>> usb-device itself, but you match on interface properties. There is no
>> sane way for udev to match on an interface property and get the device
>> node name at the same time. You run into unsolvable timing problems,
>> or need to use weird hacks.
>
> if I remember correcty, with linux and hotplug this was possible, right?
> so linux+sysfs+udev is a regression from linux+hotplug? an unfixable?
It was "possible" due to a lot of "sleep"s in hotplug scripts (aka
"unsolvable timing problem", because sleeps are not a solution).
--
Alexander E. Patrakov
-------------------------------------------------------------------------
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-06-27 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 13:14 usb + sysfs + udev problems once more Andreas Jellinghaus
2007-06-27 14:35 ` Kay Sievers
2007-06-27 15:27 ` Andreas Jellinghaus
2007-06-27 16:02 ` Alexander E. Patrakov [this message]
2007-06-27 16:22 ` Andreas Jellinghaus
2007-06-27 16:36 ` 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=46828A33.2090909@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--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.