Hi,
Appears that the failure reported by Karl Schmidt occurred when two
devices matched the rule.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040445
Similar erroneous result here with only one matching device. Details
below.
Ideas?
Thx, ... P.
=====================================
In Debian 11.
root@imager:~# cat /etc/deb*ver*
11.8
root@imager:~# head -n 13 /etc/udev/rules.d/10* | tail -n 2
KERNEL=="sd?3", SUBSYSTEM=="block", ATTR{size}=="60028928", \
SYMLINK+="AY", OWNER="root", GROUP="root", MODE="700"
root@imager:~# ls -ld /dev/A*
lrwxrwxrwx 1 root root 4 Oct 22 07:00 /dev/AY -> sdb3
# That, ^, is the correct result.
In Debian 12.
root@imager:~# cat /etc/deb*ver*
12.2
root@imager:~# head -n 23 /etc/udev/rules.d/10* | tail -n 2
KERNEL=="sd?3", SUBSYSTEM=="block", ATTR{size}=="60028928", \
SYMLINK+="A1", OWNER="root", GROUP="root", MODE="700"
root@imager:~# ls -ld /dev/A*
lrwxrwxrwx 1 root root 4 Oct 22 06:53 /dev/A1 -> sda5
# That, ^, is the wrong result. /dev/sda has no ATTR{size}=="60028928".
Simple tests similar to these reported by Karl and I are likely to
produce failures in short order.
Failure of salient features impairs the appeal of Debian. With
removable storage routinely depending upon udev, successful operation
really should be verified before a new Debian is released.
Regards, ... Peter E.
-
VoIP: +1 604 670 0140
work: https://en.wikibooks.org/wiki/User:PeterEasthope
