From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev.rules woes
Date: Mon, 26 Jan 2004 13:59:23 +0000 [thread overview]
Message-ID: <20040126135923.GA10323@vrfy.org> (raw)
In-Reply-To: <20040123185637.GA2431@Benine>
On Fri, Jan 23, 2004 at 08:56:37PM +0200, Guido Schimmels wrote:
>
> To reproduce my static /dev with udev, I tried and replaced:
>
> BUS="ide", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT="cdrom",
> NAME="%k", SYMLINK="cdrom"
>
> with:
>
> BUS="ide", PROGRAM="/bin/cat /proc/ide/hdc/media", RESULT="cdrom",
> NAME="hdc", SYMLINK="cdrom"
>
> Looks innocent enough, but triggers completely unexpected behaviour.
> It makes __all__ IDE device nodes disappear, except /dev/hdc and /dev/
> cdrom symlinked to it.
No, it doesn't look innocent, in any kind :) You ask for _every_ ide
device "if hdc is a cdrom" and if yes please give it the name 'hdc'.
The first rule matches every time.
Why not stick with the provided example? It just works.
If you want your own rules, you may add KERNEL= to the rule.
thanks,
Kay
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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-01-26 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 18:56 udev.rules woes Guido Schimmels
2004-01-26 13:59 ` 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=20040126135923.GA10323@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).