On Fri, 2010-04-09 at 11:46 -0400, Anthony DeRobertis wrote:
> 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"
These rules are lacking a device path (were they generated a long time
ago?) so we can't automatically update them.
I have now fixed the postinst script so it does not report files as
being automatically updated when it cannot find any new device IDs for
them.
[...]
> > 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:
This wording is currently in translation, so I don't want to change it
now. Instead, I have implemented a simple scan for the devices listed
in mdadm.conf so that the wording can be correct.
[...]
> Also, there should probably be a note about needing to re-run
> update-initramfs after modifying e.g., mdadm.conf.
I assume that the advanced users who use mdadm already know they need to
do that after editing mdadm.conf. Similarly, I assume that they know to
run lilo after editing lilo.conf. Remember also that this message has
to apply to all of the many configuration files that might need to be
changed.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part