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 15:11:31 +0000 [thread overview]
Message-ID: <1103641892.5845.12.camel@localhost.localdomain> (raw)
In-Reply-To: <20041221150258.GB14897@cirrus.madduck.net>
On Tue, 2004-12-21 at 16:02 +0100, martin f krafft wrote:
> I am not sure this is possible, but if it is...
>
> Would you consider making the name of any symlinks to be added to
> a device available in the environment (e.g. a :-separated list in
> $SYMLINKS), when the /dev/dev.d hooks are called?
>
> This would allow me to write a hook for permissions.d, making it
> optional and still supporting all it should be able to do.
Use udevinfo in the dev.d/ script and ask with the DEVPATH for the
symlinks:
[kay@pim ~]$ udevinfo -r -q symlink -p /class/video4linux/video0
/dev/camera0 /dev/kamera0 /dev/videocam0 /dev/webcam0
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 15:11 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 [this message]
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
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=1103641892.5845.12.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 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).