From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udev update changed cd/dvd device name
Date: Mon, 19 Nov 2012 11:18:39 -0600 [thread overview]
Message-ID: <20121119171839.GE8428@server> (raw)
In-Reply-To: <CAK2H+efXKV4WxeToF9XYw1sehgLhZ07m9L5LsL+Q6_1W=5gCNw@mail.gmail.com>
On Mon, Nov 19, 2012 at 07:59:34AM -0800, Mark Knecht wrote:
> Anyone else run into this problem with udev-171-r9? I updated
> yesterday and my CD/DVD, which has been /dev/cdrom1 since I built the
> machine 2 1/2 years ago, is now called /dev/scd0.
>
> Machine is x86_64, mostly stable.
>
> - Mark
mingdao@workstation ~ $ cat /etc/udev/rules.d/70-persistent-cd.rules
# This file was automatically generated by the /lib/udev/write_cd_rules
# program, run by the cd-aliases-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and set the $GENERATED variable.
# TSSTcorp_CDDVDW_SH-222AB (pci-0000:00:11.0-scsi-0:0:0:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:11.0-scsi-0:0:0:0", SYMLINK+="cdrom", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:11.0-scsi-0:0:0:0", SYMLINK+="cdrw", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:11.0-scsi-0:0:0:0", SYMLINK+="dvd", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:11.0-scsi-0:0:0:0", SYMLINK+="dvdrw", ENV{GENERATED}="1"
# TSSTcorp_CDDVDW_SH-222AB (pci-0000:00:11.0-scsi-3:0:0:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:11.0-scsi-3:0:0:0", SYMLINK+="cdrom1", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:11.0-scsi-3:0:0:0", SYMLINK+="cdrw1", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:11.0-scsi-3:0:0:0", SYMLINK+="dvd1", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:11.0-scsi-3:0:0:0", SYMLINK+="dvdrw1", ENV{GENERATED}="1"
mingdao@workstation ~ $ ls -l /dev/cdrom*
lrwxrwxrwx 1 root root 3 Nov 19 05:05 /dev/cdrom1 -> sr0
mingdao@workstation ~ $ ls -l /dev/sr*
brw-rw---- 1 root cdrom 11, 0 Nov 19 05:05 /dev/sr0
mingdao@workstation ~ $ ls -l /dev/scd*
lrwxrwxrwx 1 root root 3 Nov 19 05:05 /dev/scd0 -> sr0
mingdao@workstation ~ $ cat /var/log/portage/elog/sys-fs\:udev-171-r9\:20121119-131656.log
INFO: setup
Package: sys-fs/udev-171-r9
Repository: gentoo
Maintainer: udev-bugs@gentoo.org
USE: amd64 elibc_glibc kernel_linux multilib rule_generator userland_GNU
FEATURES: sandbox
Package: sys-fs/udev-171-r9
Repository: gentoo
Maintainer: udev-bugs@gentoo.org
USE: amd64 elibc_glibc kernel_linux multilib rule_generator userland_GNU
FEATURES: sandbox
Determining the location of the kernel source code
ERROR: setup
Unable to find kernel sources at /usr/src/linux
INFO: setup
Please make sure that /usr/src/linux points at your running kernel,
(or the kernel you wish to build against).
Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
WARN: setup
Unable to calculate Linux Kernel version for build, attempting to use running version
INFO: setup
Found kernel object directory:
/home/mingdao/kernel/linux-3.0
Found sources for kernel version:
3.0.51
Checking for suitable kernel configuration options...
WARN: setup
udev-171 does not support Linux kernel before version 2.6.32!
INFO: setup
Your kernel version (3.0.51) is new enough to run udev-171 reliably.
Found kernel object directory:
/home/mingdao/kernel/linux-3.0
Found sources for kernel version:
3.0.51
INFO: prepare
Applying udev-171-path_id-skip-ATA-transport.patch ...
Applying various patches (bugfixes/updates) ...
0001-Revert-udevd-log-warning-if-run-is-not-writable.patch ...
Done with patching
Running elibtoolize in: udev-171/
Applying portage/1.2.0 patch ...
Applying sed/1.5.6 patch ...
Applying as-needed/2.2.6 patch ...
LOG: postinst
Updating persistent-net rules file
WARN: postinst
You need to add udev-mount to the sysinit runlevel.
If you do not do this,
your system will not be able to boot!
Run this command:
rc-update add udev-mount sysinit
LOG: postinst
persistent-net does assigning fixed names to network devices.
If you have problems with the persistent-net rules,
just delete the rules file
rm /etc/udev/rules.d/70-persistent-net.rules
and then reboot.
This may however number your devices in a different way than they are now.
WARN: postinst
If you build an initramfs including udev, then please
make sure that the /sbin/udevadm binary gets included,
and your scripts changed to use it,as it replaces the
old helper apps udevinfo, udevtrigger, ...
mount options for directory /dev are no longer
set in /etc/udev/udev.conf, but in /etc/fstab
as for other directories.
If you use /dev/md/*, /dev/loop/* or /dev/rd/*,
then please migrate over to using the device names
/dev/md*, /dev/loop* and /dev/ram*.
The devfs-compat rules have been removed.
For reference see Bug #269359.
Rules for /dev/hd* devices have been removed
Please migrate to libata.
LOG: postinst
For more information on udev on Gentoo, writing udev rules, and
fixing known issues visit:
http://www.gentoo.org/doc/en/udev-guide.xml
Always good to have some idiot change things without mentioning it.
Before the update and reboot mine was /dev/cdrom symlinked to /dev/sr0
Good way to spend my day finding what said idiot broke where/why...
--
Happy Penguin Gymnastics >')
126 Fenco Drive ( \
Tupelo, MS 38801 ^^
admin@happypenguingymnastics.com
662-321-7009
http://happypenguingymnastics.com/
FB: http://tiny.cc/HappyPenguinGymnastics
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
next prev parent reply other threads:[~2012-11-19 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 15:59 [gentoo-user] udev update changed cd/dvd device name Mark Knecht
2012-11-19 17:18 ` Bruce Hill [this message]
2012-11-19 17:54 ` Mark Knecht
2012-11-19 18:17 ` Bruce Hill
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=20121119171839.GE8428@server \
--to=daddy@happypenguincomputers.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