From: "John L. Fjellstad" <john-hotplug@fjellstad.org>
To: linux-hotplug@vger.kernel.org
Subject: additional symlinks
Date: Tue, 17 Feb 2004 07:29:40 +0000 [thread overview]
Message-ID: <20040217072940.GA2227@fjellstad.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
Correct me if I'm wrong, but udev currently doesn't let you specifiy
additional symlinks, correct?
That is, if you have this in the udev.rules file:
BUS="ide", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT="cdrom",
NAME="cdroms/cdrom%m", SYMLINK="cdrom%n"
I can't do something like this later on in the rules file:
UPDATE="cdroms/cdrom%m", SYMLINK="dvd%n"
I have a patch ready to do this, but didn't want to submit until I was
clear on this issue (no point in submitting something that already been
done)
--
John L. Fjellstad
web: http://www.fjellstad.org/ Quis custodiet ipsos custodes
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2004-02-17 7:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 7:29 John L. Fjellstad [this message]
2004-02-17 12:08 ` additional symlinks "Andrey Borzenkov"
2004-02-17 14:38 ` John L. Fjellstad
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=20040217072940.GA2227@fjellstad.org \
--to=john-hotplug@fjellstad.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).