From: Stefan Schweizer <sschweizer@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: cdrom devices missing
Date: Mon, 03 Jan 2005 12:49:06 +0000 [thread overview]
Message-ID: <e796392205010304492eff76ba@mail.gmail.com> (raw)
In-Reply-To: <crbdo8$q5n$1@sea.gmane.org>
These are problems, that happen when not all udev.rules files for all
distributions are updated. We even use different ways to solve the
same problems ..
It is made at the beginning of the gentoo rules file:
# cdrom symlinks and other good cdrom naming
BUS="ide", KERNEL="hd[a-z]",
PROGRAM="/etc/udev/scripts/cdsymlinks.sh %k", SYMLINK="%c{1} %c{2}
%c{3} %c{4} %c{5} %c{6}"
BUS="scsi", KERNEL="sr[0-9]*",
PROGRAM="/etc/udev/scripts/cdsymlinks.sh %k", SYMLINK="%c{1} %c{2}
%c{3} %c{4} %c{5} %c{6}"
BUS="scsi", KERNEL="scd[a-z]",
PROGRAM="/etc/udev/scripts/cdsymlinks.sh %k", SYMLINK="%c{1} %c{2}
%c{3} %c{4} %c{5} %c{6}"
# devfs-names for ide-devices (uncomment only one)
# /dev/ide/.../{disc,cd} and /dev/{cdroms,discs}/* type names
BUS="ide", KERNEL="hd*", PROGRAM="/etc/udev/scripts/ide-devfs.sh %k %b
%n", NAME="%k", SYMLINK="%c{1} %c{2}"
Maybe you could just try to use the gentoo rules file? (make sure you
have the necessary scripts)
or change your rules similar to the above one.
Kind regards,
Stefan
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
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:[~2005-01-03 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 12:31 cdrom devices missing Sam Liddicott
2005-01-03 12:49 ` Stefan Schweizer [this message]
2005-01-03 12:55 ` Kay Sievers
2005-01-03 16:49 ` Sam Liddicott
2005-01-03 17:23 ` 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=e796392205010304492eff76ba@mail.gmail.com \
--to=sschweizer@gmail.com \
--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).