From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Simple Rule Now Broken in udev089
Date: Wed, 12 Apr 2006 21:17:18 +0000 [thread overview]
Message-ID: <20060412211718.GB18693@vrfy.org> (raw)
In-Reply-To: <BAY113-F175373A5C279FACF07BC2AAACD0@phx.gbl>
On Wed, Apr 12, 2006 at 09:11:43PM +0000, Robert Kennedy wrote:
> >From: Kay Sievers <kay.sievers@vrfy.org>
> >To: Robert Kennedy <amtor@hotmail.com>
> >CC: linux-hotplug-devel@lists.sourceforge.net
> >Subject: Re: Simple Rule Now Broken in udev089
> >Date: Wed, 12 Apr 2006 10:45:15 +0200
> >
> >On Tue, Apr 11, 2006 at 09:49:43PM +0000, Robert Kennedy wrote:
> >>
> >> For awhile I have been using the following simple rule to create a
> >> persistent symlink for my removable CDRW burner:
> >>
> >> KERNEL="scd0", SYMLINK="cdrwiter"
> >>
> >> I placed this rule in 10-local.rules inside the /etc/udev/rules.d/
> >> directory.
> >>
> >> It used to work in previous version of udev but now it does not work.
> >udev
> >> is still creating the /dev/scd0 node but not the /dev/cdwriter node.
> >>
> >> Any ideas on what might be happening. Has anything changed in udev
> >089?
> >
> >No, something like this works for me. But you should always use += to
> >add a new symlink to the list, otherwise you reset all earlier added
> >ones. Maybe there is a later rule that overwrites that one?
> >
> >Kay
>
> Thanks for the tip Kay. I tried changing the rule to:
>
> KERNEL="scd0", SYMLINK+="cdwriter"
>
> and then doing a udevstart but it did not work. I still get a /dev/scd0
> node but not a /dev/cdwriter node. Very strange. I only have this one
> rule in 10-local.rules. 10-local.rules should be the first file processed
> in /etc/udev/rules.d/
Are sure you have a scd* kernel device and not a sr*?
What does:
ls -l /sys/block
show?
Kay
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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 prev parent reply other threads:[~2006-04-12 21:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 21:49 Simple Rule Now Broken in udev089 Robert Kennedy
2006-04-12 8:45 ` Kay Sievers
2006-04-12 21:11 ` Robert Kennedy
2006-04-12 21:17 ` Kay Sievers [this message]
2006-04-12 23:17 ` Robert Kennedy
2006-04-13 10:36 ` Kay Sievers
2006-04-14 0:34 ` Robert Kennedy
2006-04-14 14:49 ` Kay Sievers
2006-04-15 19:15 ` Robert Kennedy
2006-04-18 5:17 ` Scott James Remnant
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=20060412211718.GB18693@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).