From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Tue, 21 Dec 2004 14:34:56 +0000 Subject: Re: parser problem Message-Id: <1103639696.5845.8.camel@localhost.localdomain> List-Id: References: <20041221141751.GA11862@cirrus.madduck.net> In-Reply-To: <20041221141751.GA11862@cirrus.madduck.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Tue, 2004-12-21 at 15:17 +0100, martin f krafft wrote: > Trying to anticipate the udev crippling The answer to this email is delayed for the next 72 hours! > this one seems like a bug: > > BUS="scsi", SYSFS{model}="FLASH G13", KERNEL="sd?1", NAME="%k", SYMLINK="flash", GROUP="flash", MODE="0660" > > (all in one line) works. > Both of the following: > > BUS="scsi", SYSFS{model}="FLASH G13", KERNEL="sd?1", > NAME="%k", SYMLINK="flash", GROUP="flash", MODE="0660" > > BUS="scsi", SYSFS{model}="FLASH G13", KERNEL="sd?1", \ > NAME="%k", SYMLINK="flash", GROUP="flash", MODE="0660" > > yield *all* "FLASH G13" scsi devices to be chgrp'd to flash and > chmod'd to 660. Seems like the newline causes udev to ignore the > previous match specification. > > Parser bug? > > If I could find a specification about the rules syntax, I might be > able to find my own errors. Any pointers? > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ 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