From: Norbert Kiesel <nkiesel@tbdnetworks.com>
To: linux-hotplug@vger.kernel.org
Subject: how to automatically create symlinks named /dev/cdrom?
Date: Sun, 09 May 2004 03:58:29 +0000 [thread overview]
Message-ID: <20040509035829.GA16229@tbdnetworks.com> (raw)
Hi,
started using udev and came across a problem I could not solve in
a satisfactory way: I'd like to get my symlinks /dev/cdrom and
/dev/dvd back. For now I added two lines to links.conf (btw, where
is its file format documented?) like "L hdc cdrom", but this of course
breaks as soon as the cdrom moves around. man pages and googleing
did not help.
What I'm looking for is a rule stating: "whenever a media capable of
playing audio CDs (or reading ISO-9660 data CDs) shows up, generate
a symlink named cdrom within udev root to it". Analogous for DVD.
Currently I personally don't care that the above is broken as soon as
the second of a kind shows up because I don't have a machine with 2
CD drives :-) But I could imagine either picking just the first or
picking the "best" cdrom (using e.g. "speed" or user-provided data
like "First pick is the Pioneer CD-ROM, else the CD-RW").
so long
Norbert
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
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 reply other threads:[~2004-05-09 3:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-09 3:58 Norbert Kiesel [this message]
2004-05-09 10:49 ` how to automatically create symlinks named /dev/cdrom? Marco d'Itri
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=20040509035829.GA16229@tbdnetworks.com \
--to=nkiesel@tbdnetworks.com \
--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).