From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] udev - fix cdrom symlink rule
Date: Sun, 08 Feb 2004 15:24:35 +0000 [thread overview]
Message-ID: <20040208152435.GC10390@vrfy.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 60 bytes --]
We only need to look at the device, not at the partitions.
[-- Attachment #2: 02-cdrom-symlink.patch --]
[-- Type: text/plain, Size: 590 bytes --]
===== etc/udev/udev.rules 1.26 vs edited =====
--- 1.26/etc/udev/udev.rules Thu Jan 15 22:42:58 2004
+++ edited/etc/udev/udev.rules Sun Feb 8 16:03:06 2004
@@ -35,7 +35,7 @@
#KERNEL="tty*", NAME="vc/%n"
# if this is a ide cdrom, name it the default name, and create a symlink to cdrom
-BUS="ide", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT="cdrom", NAME="%k", SYMLINK="cdrom"
+BUS="ide", KERNEL="*[!0-9]", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT="cdrom", NAME="%k", SYMLINK="cdrom"
# device mapper creates its own device nodes so ignore these
KERNEL="dm-[0-9]*", NAME=""
next reply other threads:[~2004-02-08 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 15:24 Kay Sievers [this message]
2004-02-11 22:30 ` [PATCH] udev - fix cdrom symlink rule Greg KH
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=20040208152435.GC10390@vrfy.org \
--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).