On Sun, Mar 22, 2009 at 22:16, Marco d'Itri <md@xxxxxxxx> wrote:
> After switching from 125 to 140 I noticed that in some cases (e.g. a
> freshly installed kvm VM works, but my laptop and the one of another
> Debian developer does not) the /dev/root symlink is not created anymore.
>
> How can I debug this? I verified that the link is listed in $DEVLINKS
> captured at boot time by a logger run after all rules:
>
> DEVLINKS='/dev/block/8:4 /dev/disk/by-id/ata-SAMSUNG_HM080II_xxxxxxxxxxxxxx-part4 /dev/disk/by-id/scsi-SATA_SAMSUNG_HM080II_xxxxxxxxxxxxxx-part4 /dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part4 /dev/disk/by-uuid/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx /dev/disk/by-label/root /dev/root'
>
> but is not present in the udev database:
>
> E: DEVLINKS=/dev/block/8:4 /dev/disk/by-id/ata-SAMSUNG_HM080II_xxxxxxxxxxxxxx-part4 /dev/disk/by-id/scsi-SATA_SAMSUNG_HM080II_xxxxxxxxxxxxxx-part4 /dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part4 /dev/disk/by-uuid/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx /dev/disk/by-label/root
>
> /dev/.udev/rules.d/61-dev-root-link.rules exists and looks correct:
>
> ACTION=="add", SUBSYSTEM=="block", ENV{MAJOR}=="8", ENV{MINOR}=="4", SYMLINK+="root"
Add "change" here? Rules that create links or set a name are almost
all wrong, if they do not match on :add" and "change" at the same
time.
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
