From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: parser problem
Date: Tue, 21 Dec 2004 14:34:56 +0000 [thread overview]
Message-ID: <1103639696.5845.8.camel@localhost.localdomain> (raw)
In-Reply-To: <20041221141751.GA11862@cirrus.madduck.net>
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
next prev parent reply other threads:[~2004-12-21 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 14:17 parser problem martin f krafft
2004-12-21 14:34 ` Kay Sievers [this message]
2004-12-21 14:50 ` martin f krafft
2004-12-21 14:56 ` martin f krafft
2004-12-21 15:18 ` 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=1103639696.5845.8.camel@localhost.localdomain \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).