The example in the disko-install documentation suggests specifying a device like /dev/disk/by-id/some-disk-id in configuration.nix, but then proceeds to show overwriting the value with /dev/sda. This might lead some readers to believe this is safe to do. However, the order in which devices with bus-based naming schemes are discovered is arbitrary and can change across reboots.
The documentation should explicitly advise against specifying disks in this way.
Alternatively, the disko-install CLI could include an option to "expand" a short name like /dev/sda into its corresponding persistent disk ID at runtime, which would be a nice convenience feature. However, this shouldn't be the default behavior, as some users might be relying on the current functionality.
The example in the disko-install documentation suggests specifying a device like
/dev/disk/by-id/some-disk-idinconfiguration.nix, but then proceeds to show overwriting the value with/dev/sda. This might lead some readers to believe this is safe to do. However, the order in which devices with bus-based naming schemes are discovered is arbitrary and can change across reboots.The documentation should explicitly advise against specifying disks in this way.
Alternatively, the
disko-installCLI could include an option to "expand" a short name like/dev/sdainto its corresponding persistent disk ID at runtime, which would be a nice convenience feature. However, this shouldn't be the default behavior, as some users might be relying on the current functionality.