All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Patterson <andrew.patterson@hp.com>
To: linux-hotplug@vger.kernel.org
Subject: Problem parsing %s in udev rules
Date: Wed, 06 Oct 2004 23:33:04 +0000	[thread overview]
Message-ID: <1097105584.9273.9.camel@bluto.andrew> (raw)

[-- Attachment #1: Type: text/plain, Size: 852 bytes --]

Udev seems to be chopping off anything seen in a rule after a %s.  For
example, if I have the following rule:

BUS="scsi", KERNEL="sd*", PROGRAM="/sbin/scsi_id", NAME="%k",
SYMLINK="scsi_disks/some-proceeding-stuff-%s{model}-some-following-
stuff"

Everything after the %s{model} is ignored.

Furthermore, everything in model following whitespace is ignored as
well.  I.e, if model contains "HP 34.7G", the resulting device file
created is /dev/scsi_disks/some-proceeding-stuff-HP.

I used the following command to run this test:

# DEVPATH=/block/sda ACTION=add ./udev block

I also get the same behavior when using udevstart (patched to fix
parameter passing problems).

Environment:

OS: debian unstable
Arch: IA-64
udev version: 032
scsi_id version: 0.5

Andrew

-- 
Andrew Patterson                
Hewlett-Packard

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-10-06 23:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-06 23:33 Andrew Patterson [this message]
2004-10-06 23:50 ` Problem parsing %s in udev rules Kay Sievers
2004-10-07  0:23 ` Andrew Patterson
2004-10-07  0:30 ` Kay Sievers
2004-10-12 23:04 ` Andrew Patterson
2004-10-12 23:58 ` Greg KH
2004-10-13 23:13 ` Andrew Patterson
2004-10-13 23:56 ` Greg KH
2004-10-14 20:05 ` Andrew Patterson
2004-10-15 18:45 ` 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=1097105584.9273.9.camel@bluto.andrew \
    --to=andrew.patterson@hp.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.