From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 089 release
Date: Thu, 06 Apr 2006 03:12:53 +0000 [thread overview]
Message-ID: <20060406031253.GA14098@kroah.com> (raw)
In-Reply-To: <20060403171123.GA24860@vrfy.org>
On Thu, Apr 06, 2006 at 03:54:17AM +0300, juuso.alasuutari@tamperelainen.org wrote:
> Quoting Scott James Remnant <scott@ubuntu.com>:
>
> > > If you can convince me why we would want to filter out events on the
> > > event generation side instead of doing that on the event handling side.
> > > I'm not sure about the idea of controlling the module load order or the
> > > other weird things that way, but you may may have good reasons I don't
> > > see at the moment.
> > >
> > The principal reason for us at the moment is in the initramfs; in the
> > main system we just plug everything and let the order be damned.
> > Indeed, wherever we've found a situation where a module load order is
> > necessary (I know of three or four I think at the moment) we've decided
> > that the bug is in the driver for requiring that order.
>
> I just wanted to pop in to confirm that network device modules loading in random
> order can be a pain. When interfaces are not always named in the same order,
> things can become more complicated than they should be.
> This can of course be avoided with rules that bind MAC addresses to fixed names,
> but it would be much nicer to have a predictable loading order.
Use MAC addressed to create fixed names if you really care about this.
Otherwise, the loading order is never guaranteed to be the same (pci bus
ids change, usb ids change, etc.)
thanks,
greg k-h
-------------------------------------------------------
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
prev parent reply other threads:[~2006-04-06 3:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 17:11 [ANNOUNCE] udev 089 release Kay Sievers
2006-04-04 19:46 ` David Gómez
2006-04-04 19:51 ` Kay Sievers
2006-04-04 19:56 ` David Gómez
2006-04-04 20:19 ` Kay Sievers
2006-04-04 23:25 ` Scott James Remnant
2006-04-05 18:51 ` Kay Sievers
2006-04-05 19:33 ` Scott James Remnant
2006-04-05 19:36 ` Marco d'Itri
2006-04-06 0:54 ` juuso.alasuutari
2006-04-06 3:02 ` Scott James Remnant
2006-04-06 3:12 ` Greg KH [this message]
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=20060406031253.GA14098@kroah.com \
--to=greg@kroah.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 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).