From: martin f krafft <madduck@madduck.net>
To: linux-hotplug@vger.kernel.org
Subject: parser problem
Date: Tue, 21 Dec 2004 14:17:51 +0000 [thread overview]
Message-ID: <20041221141751.GA11862@cirrus.madduck.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Trying to anticipate the udev crippling, 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?
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
spamtraps: madduck.bogus@madduck.net
kermit: why are there so many songs about rainbows?
fozzy: that's part of what rainbows do.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-12-21 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 14:17 martin f krafft [this message]
2004-12-21 14:34 ` parser problem Kay Sievers
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=20041221141751.GA11862@cirrus.madduck.net \
--to=madduck@madduck.net \
--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).