Bug#577047: device ids will be changed as follows: (blank)
On Fri, Apr 09, 2010 at 11:24:23AM +0100, Ben Hutchings wrote:
>
> Right. And it is generally able to convert references to CD drives.
> Please send the contents of /etc/udev/rules.d/70-persistent-cd.rules and
> the output of 'ls -l /dev/disk/by-id'.
anthony@Feynman:~$ cat /etc/udev/rules.d/70-persistent-cd.rules
# 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.
# TSSTcorpCDDVDW_TS-H552U (pci-0000:00:0f.1-ide-0:0)
ENV{ID_CDROM}=="?*", SUBSYSTEMS=="ide", KERNELS=="1.0", SYMLINK+="cdrom", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", SUBSYSTEMS=="ide", KERNELS=="1.0", SYMLINK+="cdrw", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", SUBSYSTEMS=="ide", KERNELS=="1.0", SYMLINK+="dvd", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", SUBSYSTEMS=="ide", KERNELS=="1.0", SYMLINK+="dvdrw", ENV{GENERATED}="1"
# TSSTcorpCDDVDW_TS-H552U (pci-0000:00:06.0-ide-0:0)
ENV{ID_CDROM}=="?*", SUBSYSTEMS=="ide", KERNELS=="0.0", SYMLINK+="cdrom", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", SUBSYSTEMS=="ide", KERNELS=="0.0", SYMLINK+="cdrw", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", SUBSYSTEMS=="ide", KERNELS=="0.0", SYMLINK+="dvd", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", SUBSYSTEMS=="ide", KERNELS=="0.0", SYMLINK+="dvdrw", ENV{GENERATED}="1"
# Cruzer (pci-0000:00:02.1-usb-0:8:1.0-scsi-0:0:0:1)
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:02.1-usb-0:8:1.0-scsi-0:0:0:1", SYMLINK+="cdrom1", ENV{GENERATED}="1"
# Cruzer (pci-0000:00:02.1-usb-0:8:1.0-scsi-0:0:0:1)
ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="SanDisk_Cruzer_43171018A2C0A222-0:1", SYMLINK+="cdrom2", ENV{GENERATED}="1"
anthony@Feynman:~$
anthony@Feynman:~$
anthony@Feynman:~$
anthony@Feynman:~$ ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root 9 2010-04-08 01:40 ata-ST3200826AS_3ND1F9YR -> ../../sdb
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 ata-ST3200826AS_3ND1F9YR-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 ata-ST3200826AS_3ND1F9YR-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 ata-ST3200826AS_3ND1F9YR-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 ata-ST3200826AS_3ND1F9YR-part4 -> ../../sdb4
lrwxrwxrwx 1 root root 9 2010-04-08 01:40 ata-ST3200826AS_3ND1N1DD -> ../../sda
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 ata-ST3200826AS_3ND1N1DD-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 ata-ST3200826AS_3ND1N1DD-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 ata-ST3200826AS_3ND1N1DD-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 ata-ST3200826AS_3ND1N1DD-part4 -> ../../sda4
lrwxrwxrwx 1 root root 9 2010-04-08 01:40 ata-TSSTcorpCD_DVDW_TS-H552U_ -> ../../hda
lrwxrwxrwx 1 root root 9 2010-04-08 01:40 md-uuid-3b1518fe:b9388c72:cdd71fbf:ec6a9bd8 -> ../../md3
lrwxrwxrwx 1 root root 9 2010-04-08 01:40 md-uuid-62422da2:465098f7:5560184b:bb39a98b -> ../../md0
lrwxrwxrwx 1 root root 9 2010-04-08 01:40 md-uuid-a9bf03c7:3b086030:97f239c8:2653f7fa -> ../../md1
lrwxrwxrwx 1 root root 9 2010-04-08 01:40 md-uuid-b793be2f:48cd4737:16b3cc2e:d9736af9 -> ../../md2
lrwxrwxrwx 1 root root 9 2010-04-08 01:40 scsi-SATA_ST3200826AS_3ND1F9YR -> ../../sdb
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 scsi-SATA_ST3200826AS_3ND1F9YR-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 scsi-SATA_ST3200826AS_3ND1F9YR-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 scsi-SATA_ST3200826AS_3ND1F9YR-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 scsi-SATA_ST3200826AS_3ND1F9YR-part4 -> ../../sdb4
lrwxrwxrwx 1 root root 9 2010-04-08 01:40 scsi-SATA_ST3200826AS_3ND1N1DD -> ../../sda
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 scsi-SATA_ST3200826AS_3ND1N1DD-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 scsi-SATA_ST3200826AS_3ND1N1DD-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 scsi-SATA_ST3200826AS_3ND1N1DD-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 scsi-SATA_ST3200826AS_3ND1N1DD-part4 -> ../../sda4
lrwxrwxrwx 1 root root 9 2010-04-08 01:40 usb-SanDisk_SanDisk_Cruzer_43236209F691E55A-0:0 -> ../../sdc
lrwxrwxrwx 1 root root 10 2010-04-08 01:40 usb-SanDisk_SanDisk_Cruzer_43236209F691E55A-0:0-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 9 2010-04-08 01:40 usb-SanDisk_SanDisk_Cruzer_43236209F691E55A-0:1 -> ../../sr0
anthony@Feynman:~$
> We don't know how to parse mdadm.conf. So this is really a warning that
> it might need to be updated. The wording could be improved to make this
> clearer.
I think the 'still use' part is the wording problem. Maybe split it into
two lists, like:
┌───────────────────────┤ Configuring linux-base ├────────────────────────┐
│ │
│ Please check these configuration files before rebooting │
│ │
│ These configuration files still use some device names that may change │
│ when using the new kernel: │
│ │
│ /etc/fstab: /dev/hda │
│ │
│ These configuration files must be checked by hand for device names that │
│ may change when using the new kernel: │
│ │
│ /etc/mdadm/mdadm.conf │
│ │
│ <Ok> │
│ │
└─────────────────────────────────────────────────────────────────────────┘
Also, there should probably be a note about needing to re-run
update-initramfs after modifying e.g., mdadm.conf.
Reply to: