From: juuso.alasuutari@tamperelainen.org
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] fix udevtrigger first/default/last ordering
Date: Wed, 12 Apr 2006 23:22:49 +0000 [thread overview]
Message-ID: <1144884169.443d8bc9d4d25@cs1.alpha12.l-secure.net> (raw)
In-Reply-To: <20060408175157.6dfb3d29@eusebe>
Quoting Kay Sievers <kay.sievers@vrfy.org>:
> On Sat, Apr 08, 2006 at 05:51:57PM +0200, Thomas de Grenier de Latour wrote:
> > There is some logic in udevtrigger (udev-0.89 or current git) to make
> > some events being triggered first or last. But it doesn't work because,
> > in device_list_insert(), some "sysfs_path"-prefixed devices paths are
> > compared to some unprefixed paths
>
> Fixed. Thanks a lot,
> Kay
I don't completely understand the issue that this patch deals with, but does it
have something to do with module loading order? This has been giving
considerable trouble for people (also previously discussed on this list), and
is still one major obstacle for udev to reliably replace hotplug. At least this
is the case for the distribution I assist in developing.
Is there a chance that udev could in the future load modules (network, audio,
etc.) in the same order every time if no significant hardware changes take
place? If yes, when and thanks to what changes? If not, what prevents it?
I apologise if this question has already been answered here. Feel free to point
me to a thread if necessary.
Juuso Alasuutari
----------------------------------------------------------------
This mail sent through L-secure: http://www.l-secure.net/
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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:[~2006-04-12 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 15:51 [PATCH] fix udevtrigger first/default/last ordering Thomas de Grenier de Latour
2006-04-08 16:20 ` Kay Sievers
2006-04-12 23:22 ` juuso.alasuutari [this message]
2006-04-13 0:51 ` Greg KH
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=1144884169.443d8bc9d4d25@cs1.alpha12.l-secure.net \
--to=juuso.alasuutari@tamperelainen.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).