public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: 4 machines - no /dev/cdrom or /dev/dvd anymore
Date: Sun, 6 Jan 2013 17:44:19 -0800	[thread overview]
Message-ID: <CAK2H+ec9fhUcqx9z-_r80C_KrgEBCLyz=xFJ_1F=FtORwTjFRA@mail.gmail.com> (raw)
In-Reply-To: <50EA2364.4080604@gmail.com>

On Sun, Jan 6, 2013 at 5:22 PM, Dale <rdalek1967@gmail.com> wrote:
<SNIP>
>
> I'm not sure that is a bug.  As I posted earlier, this was changed a
> good while back.  There was a reason for it but I can't recall what it
> was.  The new devices for CD/DVDs is /dev/sr*.  I don't have, and have
> not had, /dev/cdrom or dvd on this rig for a good while and it works.  I
> think this happened about the same time as the hard drive devices were
> changed from hd* to sd* even for old IDE drives.  Since it was changed
> on purpose, I don't believe this is a bug.
>
> Dale


Might be true but how about digging up some references that this was
done on purpose. It makes little sense to me that if someone did this
on purpose, breaking lots of old scripts, leaving broken udev rules
laying about and just assuming everyone would figure it out without so
much and a news item then I'd say it was done pretty badly.

Again, if it truly was 'on purpose' as you say then that's OK, but
let's not create too much false history here. In my mind it's just as
reasonable that it's just a mistake or someone that was overlooked,
but I'm totally open to you showing us what we all missed.


  reply	other threads:[~2013-01-07  1:45 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 [this message]
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 ` [gentoo-user] " Dale

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='CAK2H+ec9fhUcqx9z-_r80C_KrgEBCLyz=xFJ_1F=FtORwTjFRA@mail.gmail.com' \
    --to=markknecht@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