linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: martin f krafft <madduck@madduck.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: feature request (if possible): symlink name in environment
Date: Tue, 21 Dec 2004 17:48:07 +0000	[thread overview]
Message-ID: <20041221174807.GA24667@cirrus.madduck.net> (raw)
In-Reply-To: <20041221150258.GB14897@cirrus.madduck.net>

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

also sprach Kay Sievers <kay.sievers@vrfy.org> [2004.12.21.1836 +0100]:
> Any other scripts running after that, which change may it back?

Not that I know. Maybe permissions.d itself is getting int the way,
but the problem persists if I clean out everything else from
permissions.d. Apart, those should (have) be(en) applied before the
dev.d hooks, right?

> And
>   name=${node#/dev/}
>   perms=$(grep -h "^$name" $udev_permissions/*.permissions | tail -1)
> 
> will not return the "name*:..." line for a device named "name0" what it
> should, right?

Good spot. The final colon ':' should be part of the regexp:

>   perms=$(grep -h "^${name}:" $udev_permissions/*.permissions | tail -1)

Does it work for anyone yet?

-- 
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
 
"common sense is the collection of prejudices
 acquired by age eighteen."
                                                    -- albert einstein

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2004-12-21 17:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21 15:02 feature request (if possible): symlink name in environment martin f krafft
2004-12-21 15:11 ` Kay Sievers
2004-12-21 15:38 ` martin f krafft
2004-12-21 16:04 ` Greg KH
2004-12-21 16:08 ` martin f krafft
2004-12-21 17:36 ` Kay Sievers
2004-12-21 17:48 ` martin f krafft [this message]

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=20041221174807.GA24667@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).