public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: »Q« <boxcars@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] udev-197 and /etc/udev/rules.d/
Date: Mon, 21 Jan 2013 21:56:00 -0600	[thread overview]
Message-ID: <20130121215600.068d49ff@fuchsia.remarqs.net> (raw)

udev-197-r3 gave me this postinstall warning:

  Upstream has removed the persistent-cd rules generator. If you need
  persistent names for these devices, place udev rules for them
  in /etc/udev/rules.d.

Well, I have had such a rule for a long time, and it worked ok until I
installed udev-197, which seems to be ignoring it.  I'm at a loss to
see what's wrong.

Here's /etc/udev/rules.d/12-opticaldrive.rules, just one line:

KERNEL=="sr0", SUBSYSTEM=="block", NAME="opticaldrive", SYMLINK+="%k", SYMLINK+="cdrom", SYMLINK+="cdrw", SYMLINK+="dvd", SYMLINK+="dvdrom", SYMLINK+="dvdrw"

And here's the first part of udevadm info for the device:

 looking at device '/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sr0':
   KERNEL=="sr0"
   SUBSYSTEM=="block"
   DRIVER==""
   ATTR{ro}=="0"
   ATTR{size}=="4"
   ATTR{stat}=="       0        0        0        0        0        0        0        0        0        0        0"
   ATTR{range}=="1"
   ATTR{discard_alignment}=="0"
   ATTR{events}=="media_change eject_request"
   ATTR{ext_range}=="1"
   ATTR{events_poll_msecs}=="-1"
   ATTR{alignment_offset}=="0"
   ATTR{inflight}=="       0        0"
   ATTR{removable}=="1"
   ATTR{capability}=="119"
   ATTR{events_async}==""




             reply	other threads:[~2013-01-22  3:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22  3:56 »Q« [this message]
2013-01-22  6:07 ` [gentoo-user] Re: udev-197 and /etc/udev/rules.d/ Hartmut Figge
2013-01-22  8:55 ` [gentoo-user] " Marc Joliet
2013-01-22 14:23 ` Neil Bothwick
2013-01-22 17:51   ` Marc Joliet
2013-01-23  2:29     ` [gentoo-user] " »Q«

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=20130121215600.068d49ff@fuchsia.remarqs.net \
    --to=boxcars@gmx.net \
    --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