From: Guido Schimmels <guido.schimmels@freenet.de>
To: linux-hotplug@vger.kernel.org
Subject: udev.rules woes
Date: Fri, 23 Jan 2004 18:56:37 +0000 [thread overview]
Message-ID: <20040123185637.GA2431@Benine> (raw)
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"
BUS="ide", PROGRAM="/bin/cat /proc/ide/hda/media", RESULT="cdrom",
NAME="hda", SYMLINK="cdrom"
BUS="ide", PROGRAM="/bin/cat /proc/ide/hdd/media", RESULT="cdrom",
NAME="hdd", SYMLINK="cdrom1"
BUS="ide", PROGRAM="/bin/cat /proc/ide/hdb/media", RESULT="cdrom",
NAME="hdb", SYMLINK="cdrom1"
Looks innocent enough, but triggers completely unexpected behaviour.
It makes __all__ IDE device nodes disappear, except /dev/hdc and /dev/
cdrom symlinked to it.
I installed udev only yesterday.
(udev-014 (klibc build) / kernel-2.6.1 + sysfs patches)
At least this worked:
SYSFS_name="BT848*", NAME="bttv", SYMLINK="video0"
SYSFS_name="BT878*", NAME="bttv", SYMLINK="video0"
SYSFS_name="*webcam*", NAME="webcam", SYMLINK="video1"
So I don't feel completely dumb now.
-------------------------------------------------------
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
next reply other threads:[~2004-01-23 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 18:56 Guido Schimmels [this message]
2004-01-26 13:59 ` udev.rules woes 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=20040123185637.GA2431@Benine \
--to=guido.schimmels@freenet.de \
--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).