Re: Changes In udev?
On Sat, May 19, 2012 at 05:36:08PM +, Camaleón wrote: On Sat, 19 May 2012 13:12:49 -0400, Thomas H. George wrote: On Sat, May 19, 2012 at 03:35:29PM +, Camaleón wrote: (...) Note that /dev/cdrom and /dev/dvd are the names udev gives to your devices based on the content of /etc/udev/rules.d/70-persistent- cdrom.rules file. Now that you direct me to the content of the /etc/udev/rules.d/70-persistent-cdrom.rules file (attached below) it is clear why the assignments cdrom4 and dvdrw6 were made but where did all the extra entries in this file come from? Can I just delete them? Will they be regenrated by future updates? As the same file says at the top, yes, you can edit to fit your naming needs (or even try to delete it to see if it is auto re-generated after booting with the right device names), but before making any modification or deletion, back it up first :-) # This file was automatically generated by the /lib/udev/write_cd_rules # program, probably 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. If the file is deleted it is regenerated upon reboot starting count suffixes from one. Tom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jp8lm7$27j$2...@dough.gmane.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120520164617.ga12...@tomgeorge.info
Re: Changes In udev?
On Sat, 19 May 2012 11:04:02 -0400, Thomas H. George wrote: In /dev cdrom4, cdrw4, dvd4 and dvdrw4 all point to sr1 and cdrom6, cdrw6, dvd6 and dvdrw6 all point to sr0 I just replaced a dying motherboard - the ethernet circuit failed - and on boot up found the above soft links. Perhaps this was changed in a recent dist-upgrade and I only now noticed the changes. Either way my /dev/fstab file was out of date as it contained entries like /dev/sca1 /media/cdrom1 udf,iso9660 user,noauto 0 0 so my dvdrw drives were not found. Are you running squeeze, wheehy, sid? How many optical devices do you have, two (CD → sr1 and DVD → sr0)? You can run dmesg | grep sr and send the output. (...) Question: What are the best practice /etc/fstab entries given the changes in /dev? You can try with: /dev/cdrom /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/dvd /media/dvd0 udf,iso9660 user,noauto 0 0 Note that /dev/cdrom and /dev/dvd are the names udev gives to your devices based on the content of /etc/udev/rules.d/70-persistent- cdrom.rules file. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jp8ek1$27j$1...@dough.gmane.org
Re: Changes In udev?
On Sat, May 19, 2012 at 03:35:29PM +, Camaleón wrote:
On Sat, 19 May 2012 11:04:02 -0400, Thomas H. George wrote:
In /dev cdrom4, cdrw4, dvd4 and dvdrw4 all point to sr1 and cdrom6,
cdrw6, dvd6 and dvdrw6 all point to sr0
I just replaced a dying motherboard - the ethernet circuit failed - and
on boot up found the above soft links. Perhaps this was changed in a
recent dist-upgrade and I only now noticed the changes. Either way my
/dev/fstab file was out of date as it contained entries like
/dev/sca1 /media/cdrom1 udf,iso9660 user,noauto 0 0
so my dvdrw drives were not found.
Are you running squeeze, wheehy, sid?
Wheezy
How many optical devices do you have, two (CD → sr1 and DVD → sr0)? You
can run dmesg | grep sr and send the output.
(...)
[1.802349] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda
tray
[1.802964] sr 5:0:0:0: Attached scsi CD-ROM sr0
[2.936691] sr1: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray
[2.936900] sr 6:0:0:0: Attached scsi CD-ROM sr1
The dvdrw is a sata drive and the cdrw is a usb drive
changes in /dev?
You can try with:
/dev/cdrom /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/dvd /media/dvd0 udf,iso9660 user,noauto 0 0
The problem is that udev has chosen to link cdrom4 to sr1 and to link
dvdrw6 to sr0 so there are no /dev/cdrom /dev/dvd entries.
Note that /dev/cdrom and /dev/dvd are the names udev gives to your
devices based on the content of /etc/udev/rules.d/70-persistent-
cdrom.rules file.
Now that you direct me to the content of the
/etc/udev/rules.d/70-persistent-cdrom.rules file (attached below) it is
clear why the assignments cdrom4 and dvdrw6 were made but
where did all the extra entries in this file come from? Can I just
delete them? Will they be regenrated by future updates?
# This file was automatically generated by the /lib/udev/write_cd_rules
# program, probably 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.
# DRW-2014L1T (pci-:00:05.0-scsi-1:0:0:0)
ENV{ID_CDROM}==?*, ENV{ID_PATH}==pci-:00:05.0-scsi-1:0:0:0,
SYMLINK+=cdrom, ENV{GENERATED}=1
ENV{ID_CDROM}==?*, ENV{ID_PATH}==pci-:00:05.0-scsi-1:0:0:0,
SYMLINK+=cdrw, ENV{GENERATED}=1
ENV{ID_CDROM}==?*, ENV{ID_PATH}==pci-:00:05.0-scsi-1:0:0:0,
SYMLINK+=dvd, ENV{GENERATED}=1
ENV{ID_CDROM}==?*, ENV{ID_PATH}==pci-:00:05.0-scsi-1:0:0:0,
SYMLINK+=dvdrw, ENV{GENERATED}=1
# DRX-510UL (pci-:00:02.1-usb-0:1:1.0-scsi-0:0:0:0)
ENV{ID_CDROM}==?*, ENV{ID_PATH}==pci-:00:02.1-usb-0:1:1.0-scsi-0:0:0:0,
SYMLINK+=cdrom1, ENV{GENERATED}=1
ENV{ID_CDROM}==?*, ENV{ID_PATH}==pci-:00:02.1-usb-0:1:1.0-scsi-0:0:0:0,
SYMLINK+=cdrw1, ENV{GENERATED}=1
ENV{ID_CDROM}==?*, ENV{ID_PATH}==pci-:00:02.1-usb-0:1:1.0-scsi-0:0:0:0,
SYMLINK+=dvd1, ENV{GENERATED}=1
ENV{ID_CDROM}==?*, ENV{ID_PATH}==pci-:00:02.1-usb-0:1:1.0-scsi-0:0:0:0,
SYMLINK+=dvdrw1, ENV{GENERATED}=1
# DRX-510UL (pci-:00:02.1-usb-0:1:1.0-scsi-0:0:0:0)
ENV{ID_CDROM}==?*, ENV{ID_SERIAL}==Sony_DRX-510UL_DRX-510UL_SYQ013324,
SYMLINK+=cdrom2, ENV{GENERATED}=1
ENV{ID_CDROM}==?*, ENV{ID_SERIAL}==Sony_DRX-510UL_DRX-510UL_SYQ013324,
SYMLINK+=cdrw2, ENV{GENERATED}=1
ENV{ID_CDROM}==?*, ENV{ID_SERIAL}==Sony_DRX-510UL_DRX-510UL_SYQ013324,
SYMLINK+=dvd2, ENV{GENERATED}=1
ENV{ID_CDROM}==?*, ENV{ID_SERIAL}==Sony_DRX-510UL_DRX-510UL_SYQ013324,
SYMLINK+=dvdrw2, ENV{GENERATED}=1
# Cruzer (pci-:00:02.1-usb-0:2:1.0-scsi-0:0:0:1)
ENV{ID_CDROM}==?*, ENV{ID_PATH}==pci-:00:02.1-usb-0:2:1.0-scsi-0:0:0:1,
SYMLINK+=cdrom, ENV{GENERATED}=1
# Cruzer (pci-:00:02.1-usb-0:2:1.0-scsi-0:0:0:1)
ENV{ID_CDROM}==?*, ENV{ID_SERIAL}==SanDisk_Cruzer_08778113C0C349E1-0:1,
SYMLINK+=cdrom, ENV{GENERATED}=1
# DVD_RW_DRU-510A (pci-:00:02.0-usb-0:1:1.0-scsi-0:0:0:0)
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_PATH}==pci-:00:02.0-usb-0:1:1.0-scsi-0:0:0:0, SYMLINK+=cdrom3,
ENV{GENERATED}=1
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_PATH}==pci-:00:02.0-usb-0:1:1.0-scsi-0:0:0:0, SYMLINK+=cdrw3,
ENV{GENERATED}=1
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_PATH}==pci-:00:02.0-usb-0:1:1.0-scsi-0:0:0:0, SYMLINK+=dvd3,
ENV{GENERATED}=1
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_PATH}==pci-:00:02.0-usb-0:1:1.0-scsi-0:0:0:0, SYMLINK+=dvdrw3,
ENV{GENERATED}=1
# DVD_RW_DRU-510A (pci-:00:02.0-usb-0:1:1.0-scsi-0:0:0:0)
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_SERIAL}==SONY_DVD_RW_DRU-510A_DRX-510UL_SYQ013324-0:0,
SYMLINK+=cdrom4, ENV{GENERATED}=1
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_SERIAL}==SONY_DVD_RW_DRU-510A_DRX-510UL_SYQ013324-0:0,
SYMLINK+=cdrw4, ENV{GENERATED}=1
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_SERIAL}==SONY_DVD_RW_DRU-510A_DRX-510UL_SYQ013324-0:0,
SYMLINK+=dvd4, ENV{GENERATED}=1
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_SERIAL}==SONY_DVD_RW_DRU-510A_DRX-510UL_SYQ013324-0:0,
Re: Changes In udev?
On Sat, 19 May 2012 13:12:49 -0400, Thomas H. George wrote: On Sat, May 19, 2012 at 03:35:29PM +, Camaleón wrote: (...) /dev/sca1 /media/cdrom1 udf,iso9660 user,noauto 0 0 so my dvdrw drives were not found. Are you running squeeze, wheehy, sid? Wheezy Ah... I thought it was squeeze. How many optical devices do you have, two (CD → sr1 and DVD → sr0)? You can run dmesg | grep sr and send the output. (...) [1.802349] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray [1.802964] sr 5:0:0:0: Attached scsi CD-ROM sr0 [2.936691] sr1: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray [2.936900] sr 6:0:0:0: Attached scsi CD-ROM sr1 The dvdrw is a sata drive and the cdrw is a usb drive Okay. You can try with: /dev/cdrom /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/dvd /media/dvd0 udf,iso9660 user,noauto 0 0 The problem is that udev has chosen to link cdrom4 to sr1 and to link dvdrw6 to sr0 so there are no /dev/cdrom /dev/dvd entries. That's editable. Note that /dev/cdrom and /dev/dvd are the names udev gives to your devices based on the content of /etc/udev/rules.d/70-persistent- cdrom.rules file. Now that you direct me to the content of the /etc/udev/rules.d/70-persistent-cdrom.rules file (attached below) it is clear why the assignments cdrom4 and dvdrw6 were made but where did all the extra entries in this file come from? Can I just delete them? Will they be regenrated by future updates? As the same file says at the top, yes, you can edit to fit your naming needs (or even try to delete it to see if it is auto re-generated after booting with the right device names), but before making any modification or deletion, back it up first :-) # This file was automatically generated by the /lib/udev/write_cd_rules # program, probably 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. (...) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jp8lm7$27j$2...@dough.gmane.org
