All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Gilbert <bgilbert@cs.cmu.edu>
To: linux-hotplug@vger.kernel.org
Subject: Newer udev not performing %-substitutions on OWNER and GROUP
Date: Thu, 21 May 2009 20:31:33 +0000	[thread overview]
Message-ID: <4A15BA25.7030100@cs.cmu.edu> (raw)

I have a udev rule that sets the ownership of a device node based on the 
result of a PROGRAM run, e.g.:

	..., PROGRAM="echo 1000", OWNER="%c"

This works in Fedora 10 (udev-127) and Ubuntu 8.10 (udev-124) but not in 
Fedora Rawhide (udev-141) or Ubuntu 9.04 (udev-141).  Further 
investigation reveals that on the affected systems, substitutions appear 
not to be working at all for OWNER and GROUP keys.  (I tried %c, %m, %M, 
%n, and $result.)  Replacing OWNER="%c" with OWNER="1000" works for me, 
as does SYMLINK+="%c", so the rule is being properly executed.

Is this syntax still supported for OWNER and GROUP?  udev(7) claims that 
it is.

--Benjamin Gilbert

             reply	other threads:[~2009-05-21 20:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21 20:31 Benjamin Gilbert [this message]
2009-05-21 21:11 ` Newer udev not performing %-substitutions on OWNER and GROUP Kay Sievers
2009-05-22 18:44 ` Benjamin Gilbert

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=4A15BA25.7030100@cs.cmu.edu \
    --to=bgilbert@cs.cmu.edu \
    --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.