From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Sat, 10 Jan 2004 03:52:43 +0000 Subject: Re: udev - question about current config format Message-Id: <20040110035243.GB6911@kroah.com> List-Id: References: <20040109142112.GA752@vrfy.org> In-Reply-To: <20040109142112.GA752@vrfy.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Sat, Jan 10, 2004 at 02:38:50AM +0100, Kay Sievers wrote: > On Fri, Jan 09, 2004 at 05:30:20PM -0800, Greg KH wrote: > > On Fri, Jan 09, 2004 at 03:21:12PM +0100, Kay Sievers wrote: > > > Every line in udev.rules consists only of a number of ="" > > > > > > BUS match with bus type > > > SYSFS_ match with device attribute > > > ID/PLACE match with bus "number" or "id" > > > KERNEL match with kernel device name > > > RESULT match with string returned by executed PROGRAM > > > PROGRAM program to execute (true if exec returned with 0) > > > > So don't match on a string value here? Hm, would that make writing > > programs easier? At first glance it might. It also might be a bit > > easier to understand. > > What kind of string value do you mean? Sorry, I meant the string return value of the script. Like I had to hack "good" and "bad" as return values of the name_cd script. The IDstuff. 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