From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] add options to udevtrigger to control scanning
Date: Thu, 31 Aug 2006 08:46:12 +0000 [thread overview]
Message-ID: <20060831084612.GA29222@vrfy.org> (raw)
In-Reply-To: <20060831004138.GA28528@kroah.com>
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.
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. But in both cases, please explain in which
situations this is really needed?
Thanks,
Kay
-------------------------------------------------------------------------
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 8:46 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 [this message]
2006-08-31 17:31 ` Greg KH
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=20060831084612.GA29222@vrfy.org \
--to=kay.sievers@vrfy.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 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.