From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: feature request (if possible): symlink name in environment
Date: Tue, 21 Dec 2004 17:36:04 +0000 [thread overview]
Message-ID: <1103650564.5845.38.camel@localhost.localdomain> (raw)
In-Reply-To: <20041221150258.GB14897@cirrus.madduck.net>
On Tue, 2004-12-21 at 17:08 +0100, martin f krafft wrote:
> 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.
Any other scripts running after that, which change may it back?
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?
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-12-21 17:36 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 [this message]
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=1103650564.5845.38.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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.