From: Greg KH Date: Wed, 14 Jan 2004 21:12:29 +0000 Subject: Re: [ANNOUNCE] udev 013 release Message-Id: <20040114211229.GB6650@kroah.com> List-Id: References: <20040113235213.GA7659@kroah.com> <4004D084.1050106@vgertech.com> <20040114171527.GB5472@kroah.com> <40058086.5000106@nortelnetworks.com> <4005AAD3.4010301@nortelnetworks.com> In-Reply-To: <4005AAD3.4010301@nortelnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Chris Friesen Cc: Clay Haapala , Nuno Silva , linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org On Wed, Jan 14, 2004 at 03:47:15PM -0500, Chris Friesen wrote: > Clay Haapala wrote: > > >Is the act of printing/syslogging a rule in an of itself? > > I haven't looked at the capabilities in a while. Can you specify a > default rule if nothing else matches? The "default rule" is to use the kernel name to name the device. That one is built in. > Can you, in one rule, specify another rule? (Kind of like iptables > jump targets). No. > If so, then this would allow massive flexibility. And massive complexity :) Why would you want to have a rule specify another (in the current syntax)? These rules aren't that complex, and anything that does grow to be complex should be shoved out into a separate script/program that a rule can then call. Does this help? thanks, greg k-h ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ 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