From: Treeve Jelbert <treeve01@pi.be>
To: linux-hotplug@vger.kernel.org
Subject: cdrom link not created
Date: Sun, 28 Mar 2004 16:55:39 +0000 [thread overview]
Message-ID: <200403281855.50290.treeve01@pi.be> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I am running udev-023 on /dev
the cdrom symlink is not created by the following rule
# if this is a ide cdrom, name it the default name, and create a symlink to
cdrom
BUS="ide", KERNEL="*[!0-9]", PROGRAM="/bin/cat /proc/ide/%k/media",
RESULT="cdrom", NAME="%k", SYMLINK="cdrom"
but when I ran udev on /udev, it did create the link
All other devices and symlinks are ok
If I create a symlink by hand, the device works ok
# ls -l cd*
lrwxrwxrwx 1 root root 3 2004-03-28 18:52 cdrom -> hdc
lrwxrwxrwx 1 root root 3 2004-03-28 18:31 cdrw -> sr0
Any thoughts on this?
Regards, Treeve
- --
PGP Key ID: AB929B24
PGP Key Fingerprint:31D9 D22F 42E6 F545 662E AB6F 9697 34C5 AB92 9B24
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAZwOTlpc0xauSmyQRAsXlAJ9r87B1tGDc4T20DTccwTNwslXcRgCffsFw
0L4B90HTAorpxjY0zWAv8gc—CT
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&opÃk
_______________________________________________
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-03-28 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 16:55 Treeve Jelbert [this message]
2004-03-28 17:06 ` cdrom link not created Marco d'Itri
2004-03-28 17:25 ` 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=200403281855.50290.treeve01@pi.be \
--to=treeve01@pi.be \
--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).