change the installer workflow so that instead of selecting a LUKS label for me the installer prompts me for what I want the LUKS label to be
I wanted to expound on my particular feature request of letting the user select the LUKS name and how that relates to changing the LUKS name to one based on UUID. From the merge request:
instead of e.g. vda2_crypt, the
mapping will be called luks-<uuid>
Not being a fan of having the backing block device be a part of the name used for the LUKS config using the UUID seems like a very reasonable change. However, as a sysadmin that has to juggle these things, I would rather not have to type out a UUID when I'm working on a system. Sure cut and paste is a thing that can be done which helps cut down on the typing but I am also able to formulate names myself that are shorter, easier to type, and will work for my use cases.
I suggest the following:
1) Change the default name to incorporate the UUID.
2) Update the workflow to prompt the user for their desired name
3) Offer the UUID based name to the user by pre-populating it in the dialogue box so if they find the name acceptable they can simply confirm it
4) Ensure that the LUKS name is configurable via preseed so automated installs still allow the user to have the name they want
It may make sense to apply similar changes to the volume group if a user is setting up LVM via the installer. It certainly seems desirable to me to have consistent behavior between the LVM and LUKS configuration phases during install.
I think this covers all concerns and imposes a very minimal level of overhead for users who simply want to accept whatever defaults the installer may select.