From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: cdrom link not created
Date: Sun, 28 Mar 2004 17:25:35 +0000 [thread overview]
Message-ID: <20040328172535.GB5442@vrfy.org> (raw)
In-Reply-To: <200403281855.50290.treeve01@pi.be>
On Sun, Mar 28, 2004 at 06:55:39PM +0200, Treeve Jelbert wrote:
> -----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?
May be your timezone is still wrong :)
No, please try RESULT="cdrom*". Seems we lost the newline removal before
we compare the strings.
thanks,
Kay
-------------------------------------------------------
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=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
prev parent reply other threads:[~2004-03-28 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 16:55 cdrom link not created Treeve Jelbert
2004-03-28 17:06 ` Marco d'Itri
2004-03-28 17:25 ` Kay Sievers [this message]
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=20040328172535.GB5442@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).