From: nunojsilva@ist.utl.pt (Nuno J. Silva)
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: How to get /dev/cdrom
Date: Wed, 12 Jan 2011 17:13:56 +0000 [thread overview]
Message-ID: <877hea9h9n.fsf@ist.utl.pt> (raw)
In-Reply-To: 4D2DDDF6.3020906@kutulu.org
Mike Edenfield <kutulu@kutulu.org> writes:
> On 1/12/2011 11:31 AM, Nuno J. Silva wrote:
>> Michael Sullivan <msulli1355@gmail.com> writes:
>>
>>> OK, for several years I have not had a /dev/cdrom. My workstation has
>>> an internal cd-rom drive, which gets mapped to /dev/hda, and an external
>>
>> If you're using a recent kernel, it's probably udev which refuses to
>> process devices under the old ATA driver.
>>
>> (I don't know if it *exactly* refuses, or if it's something else, but
>> the final result is what you see, no /dev/{cdrom,cdrw,...} link)
>
> The problem, as far as I could figure out, is that the ID_PATH that udev
> gets from the old ATA drivers is identical for everything on the same
> IDE controller; it basically gives the path to the PCI bus slot where
> the IDE controller is connected. So udev has no way to differentiate
> between multiple drives connected to a single controller. This is a
> change at some point from the previous behavior, which specified the IDE
> information as well.
So is this supposed to be a problem only if there is more than one PATA
device?
I never investigated this deeply enough, thanks for your explanation. I
ended up adding code to init scripts to create the links.
> You used to get something like:
>
> ENV{ID_PATH}=="pci-0000:00:1f.1-ide-0:0"
>
> and now you get:
>
> ENV{ID_PATH}=="pci-0000:00:1f.1"
>
> Switching over to libata gives you:
>
> ENV{ID_PATH}=="pci-0000:00:1f.1-scsi-0:0:0:0"
>
> which returns everything to working order :)
I guess this means that if one gets some other way to match a drive (by
name? serial number?), it's possible to make a working rule.
>
> --Mike
>
>
--
Nuno J. Silva
gopher://sdf-eu.org/1/users/njsg
next prev parent reply other threads:[~2011-01-12 17:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 16:11 [gentoo-user] How to get /dev/cdrom Michael Sullivan
2011-01-12 16:28 ` Paul Hartman
2011-01-12 16:57 ` Michael Sullivan
2011-01-12 17:23 ` Paul Hartman
2011-01-12 16:31 ` [gentoo-user] " Nuno J. Silva
2011-01-12 16:46 ` Michael Sullivan
2011-01-12 16:59 ` Mike Edenfield
2011-01-12 17:13 ` Nuno J. Silva [this message]
2011-01-12 17:20 ` Mike Edenfield
2011-01-12 16:54 ` [gentoo-user] " Mike Edenfield
2011-01-12 17:08 ` Michael Sullivan
2011-01-12 17:21 ` Neil Bothwick
2011-01-12 17:33 ` Paul Hartman
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=877hea9h9n.fsf@ist.utl.pt \
--to=nunojsilva@ist.utl.pt \
--cc=gentoo-user@lists.gentoo.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