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 11:21:57 +0200	[thread overview]
Message-ID: <20130108112157.3cb99168@khamul.example.com> (raw)
In-Reply-To: <CAK2H+edkeMkeKQe-8t-hMTAog7q09eYYL7NbeAxY-fb-1vu-6Q@mail.gmail.com>

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

>    I really don't see why I'm the one getting banged on here but
> that's life sometimes. I saw a problem for a couple of months. It
> frustrated me but not enough to do anything about it. Solving it
> finally bubbled up high enough on my list that I finally asked if
> others were having the same problem. (which they were, and which they
> also considered a problem) Before anyone had actually answered me I
> had posted one way that folks who cared could fix it. I thought I was
> doing the community a small service by getting a little bit of
> technically positive info out there. I guess not in this case.



You're not getting banged on, as Michael said udev is a polarizing
piece of software.

Life is full of silly and not-so-silly conventions and /dev/dvd is one
of them. It has no good reason to be there, and equally no good reason
to not be there, but you already fixed your stuff to make it do what
you want.

"It's not a bug" should be read more as "upstream is probably going to
ignore you" if you log a bug. In my opinion of course.

Do stick around, you are up there in the list of people who make
many useful posts.

-- 
Alan McKinnon
alan.mckinnon@gmail.com



  parent reply	other threads:[~2013-01-08  9:28 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 [this message]
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=20130108112157.3cb99168@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