From: Scott James Remnant <scott@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 089 release
Date: Wed, 05 Apr 2006 19:33:54 +0000 [thread overview]
Message-ID: <1144265634.8146.3.camel@quest.netsplit.com> (raw)
In-Reply-To: <20060403171123.GA24860@vrfy.org>
[-- Attachment #1: Type: text/plain, Size: 1857 bytes --]
On Wed, 2006-04-05 at 20:51 +0200, Kay Sievers wrote:
> On Wed, Apr 05, 2006 at 12:25:34AM +0100, Scott James Remnant wrote:
> > On Mon, 2006-04-03 at 19:11 +0200, Kay Sievers wrote:
> >
> > > Provide "udevtrigger" program to request events on coldplug. The
> > > shell script is much too slow with thousends of devices.
> > >
> > How does this differ from our "udevplug" ? :)
>
> It simply triggers events for all devices. And the logic to wait for
> the queue to become empty is in a different tool.
>
> > Would it be worth consolidating both into the same tool?
>
> 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.
In the initramfs, we exercise a little more caution; making sure that we
only probe PCI IDE or SCSI controllers first before we move on to
probing for USB buses. The reasoning for this is that we don't want
someone's fast USB pen drive beating their SATA or SCSI disk to
getting /dev/sda1
This may be unique to Ubuntu where we try to have an initramfs image
that can do everything, rather than customising it per-install; but then
for us being able to move an installation between machines and have it
always boot has been an important goal.
Scott
--
Scott James Remnant
scott@ubuntu.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-04-05 19:33 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 [this message]
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
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=1144265634.8146.3.camel@quest.netsplit.com \
--to=scott@ubuntu.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).