From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] 4 machines - no /dev/cdrom or /dev/dvd anymore
Date: Sat, 05 Jan 2013 22:01:39 -0600 [thread overview]
Message-ID: <50E8F723.1080004@gmail.com> (raw)
In-Reply-To: <CAK2H+eeuq1PdsX6YiALPDR3otE-O-y+mZC0wUzM8NrbwSqdb6w@mail.gmail.com>
Mark Knecht wrote:
> I think I touched on this a couple of weeks ago but never had time to
> dig in. At that time I thought this problem was only on one machine
> but now I see it's on every machine I've looked at this morning. Not a
> single machine has /dev/cdrom anymore, nor /dev/dvd or any of the
> other incantations that have existed forever.
>
> First, this is udev doing (or not doing) this, correct?
>
> As shown below hwinfo see the cdrom drive, and there are long existing
> udev rules that appear to want to create the devices. These rules have
> worked in the past but don't now.
>
> Are others running Gentoo stable, and in this case udev-171-r9, seeing
> this problem?
>
> Anyone recognize what's wrong with the udev rules below, or does udev
> no longer generate these devices at all? I understand that the
> 70-persistent-net.rules stuff has been 'removed'. Is this true for CDs
> also or have I botched something up on all these machines?
>
> Thanks in advance and please ask me to post anything else required.
> I've gone through the latest Gentoo install docs and don't see that
> I'm doing anything other than what they tell me to do but with udev in
> such a state of flux I've obviously missed something.
>
> Thanks,
> Mark
>
> <<<SNIP>>>
>
On my rig for a long time now, I have used the sr0 device. My DVD/CD
burning app, k3b, uses it for the CD/DVD drives. It works. From my
understanding this switched quite some time ago but can't recall the
reasoning behind it.
I don't have /dev/cdrom or /dev/dvd anymore. Everything so far has
worked tho. It just uses /dev/sr0 instead.
Hope that helps.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
prev parent reply other threads:[~2013-01-06 4:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 19:53 [gentoo-user] 4 machines - no /dev/cdrom or /dev/dvd anymore Mark Knecht
2013-01-05 20:36 ` J. Roeleveld
2013-01-05 20:46 ` Mark Knecht
2013-01-05 20:37 ` Randy Barlow
2013-01-05 20:44 ` [gentoo-user] " Mark Knecht
2013-01-05 23:00 ` David M. Fellows
2013-01-06 11:19 ` Mick
2013-01-06 15:55 ` Mark Knecht
2013-01-07 1:22 ` Dale
2013-01-07 1:44 ` Mark Knecht
2013-01-07 1:53 ` William Kenworthy
2013-01-07 2:06 ` Mark Knecht
2013-01-07 2:08 ` Dale
2013-01-07 2:29 ` Dale
2013-01-07 4:53 ` Mark Knecht
2013-01-07 7:35 ` Dale
2013-01-07 22:53 ` Mick
2013-01-08 7:09 ` J. Roeleveld
2013-01-08 7:49 ` Mick
2013-01-08 11:53 ` Dale
2013-01-07 15:18 ` Grant Edwards
2013-01-07 17:37 ` Mark Knecht
2013-01-07 23:25 ` Alan McKinnon
2013-01-08 1:05 ` Mark Knecht
2013-01-08 1:15 ` Michael Mol
2013-01-08 6:42 ` Mick
2013-01-08 9:21 ` Alan McKinnon
2013-01-08 20:26 ` Mark Knecht
2013-01-08 21:12 ` Alan McKinnon
2013-01-08 21:31 ` Michael Mol
2013-01-09 3:22 ` Dale
2013-01-11 14:31 ` Mark Knecht
2013-01-11 14:58 ` Dale
2013-01-06 4:01 ` Dale [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=50E8F723.1080004@gmail.com \
--to=rdalek1967@gmail.com \
--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