public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: 4 machines - no /dev/cdrom or /dev/dvd anymore
Date: Tue, 8 Jan 2013 01:25:33 +0200	[thread overview]
Message-ID: <20130108012533.04004d12@khamul.example.com> (raw)
In-Reply-To: <CAK2H+ee55QC+M47K9+Qk93w-FfufhOu6_3Dx8W0V-PfeKU9iLw@mail.gmail.com>

On Mon, 7 Jan 2013 09:37:05 -0800
Mark Knecht <markknecht@gmail.com> wrote:

> Now, my point is that change to /dev/srX was the root cause is FUD. It
> isn't the root cause of this change because it didn't change on my
> systems. All I know is that ID_PATH (from the old file) used to work
> and no longer does. Whatever is responsible for creating that, likely
> some portion of the kernel, changed the value and created a need to
> modify how udev looks at the system. Is it a bug? I don't know.  It's
> just the way it is.


It's not a bug as /dev/dvd is a mere convenience for the user - a
nickname if you will. You are highly unlikely to find a standards doc
of any kind stating the symlink should be there. Which means if it's
not there, you get to make your own convenient nicknames.

/dev/harddrive has never existed, right? Same with /dev/dvd and
friends. make them if you want, but you can't expect them to be there
and their absence is not a bug.

Obviously someone left them out of the rules files. Maybe they had a
reason, maybe they got lazy. Either way you get to add your own rules
to get the names YOU want.

It really is as simple as that, don't overthink this one.


-- 
Alan McKinnon
alan.mckinnon@gmail.com



  reply	other threads:[~2013-01-07 23:31 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 [this message]
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=20130108012533.04004d12@khamul.example.com \
    --to=alan.mckinnon@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