Date: Wed, 14 Jan 2004 13:12:29 -0800
From: Greg KH <greg@kroah.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Clay Haapala <chaapala@cisco.com>, Nuno Silva <nuno.silva@vgertech.com>,
       linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 013 release
Message-ID: <20040114211229.GB6650@kroah.com>
References: <20040113235213.GA7659@kroah.com> <4004D084.1050106@vgertech.com> <20040114171527.GB5472@kroah.com> <40058086.5000106@nortelnetworks.com> <yqujn08q46ct.fsf@chaapala-lnx2.cisco.com> <4005AAD3.4010301@nortelnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4005AAD3.4010301@nortelnetworks.com>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1037
Lines: 35

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/