From: "Marco d'Itri" <md@Linux.IT>
To: linux-hotplug@vger.kernel.org
Subject: Re: [udev] experimental (very simple) SYMLINK creation
Date: Sun, 07 Dec 2003 17:58:51 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107082001225551@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107060923531865@msgid-missing>
On Dec 07, Kay Sievers <kay.sievers@vrfy.org> wrote:
>What do you think? Should we allow multiple symlinks? Separated by which character?
Yes! And again, it should be able to define symlinks on a different line
than the one with the definition of the device name.
>So we may simply loop over the field and create more than one:
>
>..., SYMLINK="webcam%n:camera/%n:v4l/video%n"
Probably a space character would be a better separator, the odds you
want to use one in a device name are much lower.
--
ciao, |
Marco | [3500 uniyiB8SzEyTY]
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
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:[~2003-12-07 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 7:26 [udev] experimental (very simple) SYMLINK creation Olaf Hering
2003-12-05 15:45 ` Kay Sievers
2003-12-07 6:02 ` Kay Sievers
2003-12-07 17:45 ` Kay Sievers
2003-12-07 17:58 ` Marco d'Itri [this message]
2003-12-10 0:43 ` Greg KH
2003-12-10 1:06 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-12-05 4:24 Kay Sievers
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=marc-linux-hotplug-107082001225551@msgid-missing \
--to=md@linux.it \
--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).