Hi, I've noticed that in GuixSD (version 0.9.0), the directory /dev/disk/by-uuid is missing. Is that expected?
Because this directory is missing, cryptsetup cannot open a LUKS device by UUID. For example, see the following: --8<---------------cut here---------------start------------->8--- [0] marusich@garuda:~ $ sudo cryptsetup open --type luks UUID=c39bbc82-b70d-4e3d-a7dc-05f0b85dd84a backup Device /dev/disk/by-uuid/c39bbc82-b70d-4e3d-a7dc-05f0b85dd84a doesn't exist or access denied. [4] marusich@garuda:~ $ sudo cryptsetup open --type luks /dev/sdd1 backup Enter passphrase for /dev/sdd1: [0] marusich@garuda:~ $ blkid /dev/sdd1: UUID="c39bbc82-b70d-4e3d-a7dc-05f0b85dd84a" TYPE="crypto_LUKS" PARTUUID="00093e61-01" [0] marusich@garuda:~ $ ls /dev/disk by-id/ [0] marusich@garuda:~ $ ls /dev/disk/by-id/ dm-name-home dm-uuid-CRYPT-LUKS1-2c7fc92e9e534bd08a178f15a89746bb-home [0] marusich@garuda:~ $ --8<---------------cut here---------------end--------------->8--- As shown above, cryptsetup works fine if I specify /dev/sdd1, but it would be nice to be able to specify the UUID instead. The /dev/disk/by-id directory exists, but the purpose of that directory appears to be different than the purpose of the /dev/disk/by-uuid directory, and it does not contain an entry for the device in question. Is it expected that GuixSD is missing the /dev/disk/by-uuid directory? Thank you for your help, Chris
