From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] add options to udevtrigger to control scanning
Date: Thu, 31 Aug 2006 17:31:20 +0000 [thread overview]
Message-ID: <20060831173120.GA19571@kroah.com> (raw)
In-Reply-To: <20060831004138.GA28528@kroah.com>
On Thu, Aug 31, 2006 at 10:46:12AM +0200, Kay Sievers wrote:
> On Wed, Aug 30, 2006 at 05:41:38PM -0700, Greg KH wrote:
> > This patch has been in the gentoo tree for a bit. It modifies
> > udevtrigger to allow a little more fine grained control for people who
> > don't want all of the sysfs tree to be scanned by udevtrigger at
> > startup.
>
> When is it useful to have such options. And "no" flags who negate
> something from all events sounds pretty odd to me.
Well, either that or force the --scan-class options to be used :)
> The Ubuntu guys use a patch which can filter on values to have control
> over what is triggered and what not. If we are going that road, I like
> their patch more than this.
Do you have a pointer to where this patch is?
> But in both cases, please explain in which situations this is really
> needed?
People do not want all of their devices probed for at boot time, they
want to load the modules that they know they want, on their own. So
they don't want all of the modalias files being poked at.
In short, they don't like the "coldplug" functionality for loading
modules and only want udev to handle the device nodes present at boot
time. I don't blame them for wanting this because with machines that
you know all the hardware, it isn't necessary, and does speed up the
boot process ever so slightly.
And yes, they can use the blacklist functionality from
module-init-tools, except that seems to be broken right now in the
Gentoo releases, and I'm having a hard time figuring out why. It used
to work...
So this could be reduced to just the one option, --no-scan-bus, as that
is all that Gentoo currently uses. I think the original author was just
trying to be nice in giving all possible options :)
Would you be more comfortable with just that option being added? The
filter seems a bit complicated, unless you are able to specify all
modalias files.
thanks,
greg k-h
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&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-08-31 17:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 0:41 [PATCH] add options to udevtrigger to control scanning Greg KH
2006-08-31 8:46 ` Kay Sievers
2006-08-31 17:31 ` Greg KH [this message]
2006-08-31 17:37 ` Marco d'Itri
2006-08-31 17:52 ` Greg KH
2006-08-31 20:02 ` Scott James Remnant
2006-09-02 17:46 ` Roy Marples
2006-09-03 1:34 ` Kay Sievers
2006-09-03 3:46 ` Greg KH
2006-09-03 4:03 ` 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=20060831173120.GA19571@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).