From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: looking for udev rules to differentiate cdrom dvd
Date: Wed, 16 Nov 2005 23:44:28 +0000 [thread overview]
Message-ID: <20051116234428.GA14126@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0511161301350.31602@wm7d.net>
On Wed, Nov 16, 2005 at 01:14:22PM -0800, Joseph Mack NA3T wrote:
>
> Thinkpad 600E,
> 2.6.13, udev-062, sysfsutils-1.3.0, hotplug-2004_09_23
>
> I have both a cdrom and dvd for this machine. I was hoping
> to use systool and udevinfo to differentiate these two, and
> allow me to set up udev rules to have /dev/cdrom or /dev/dvd
> depending on which piece of hardward was in the machine.
>
> However both the cdrom and the dvd appear the same to
> systool and udevinfo (/sys/block/hd{a,c}/...)
>
> Looking for alternatives, lspci doesn't see them at all, but
> dmesg knows what I have.
>
> Should I be able to see the difference between the cdrom and
> the dvd with udevinfo?
No, but cdrom_id can do this for you. It's in the udev package, and
most distros set this up to handle it automatically.
Hope this helps,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id\x16845&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:[~2005-11-16 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 21:14 looking for udev rules to differentiate cdrom dvd Joseph Mack NA3T
2005-11-16 23:44 ` Greg KH [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=20051116234428.GA14126@kroah.com \
--to=greg@kroah.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).