All of lore.kernel.org
 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 16:08:49 +0000	[thread overview]
Message-ID: <20041221160849.GA19281@cirrus.madduck.net> (raw)
In-Reply-To: <20041221150258.GB14897@cirrus.madduck.net>

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

also sprach Greg KH <greg@kroah.com> [2004.12.21.1704 +0100]:
> No, the hook should run after.

This is what I gathered from the code as well. However, it does not
appear to work.

Would you consider trying it out? Maybe I am just on crack...

Drop it into /etc/dev.d/default/permissions.dev with 755
permissions.

Create a file in permissions.d, the way it used to be.

See if the permissions are applied (symlinks should be followed, and
the last symlink shown by

  udevinfo -r -q symlink -p $DEVPATH

has the highest priority.

Thanks,

-- 
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
 
"i like wagner's music better than anybody's. it is so loud that one
 can talk the whole time without other people hearing what one says."
                                                        -- oscar wilde

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

  parent reply	other threads:[~2004-12-21 16:08 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 [this message]
2004-12-21 17:36 ` Kay Sievers
2004-12-21 17:48 ` martin f krafft

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=20041221160849.GA19281@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 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.