Hi Ludo', Ludovic Courtès <[email protected]> writes:
> Hi Tomas, > > Tomas Volf <[email protected]> skribis: > >> I have noticed after reboot that I the log there are lines line, one for >> each encrypted drive I am unlocking: >> >> [ 35.206908] shepherd[1]: luks-master-key: /etc/luks_script not found, >> skipping > > This new mechanism effectively supersedes #:key-file by making GRUB pass > instructions to open the LUKS device to the initrd; see “Automatic LUKS > Master Key Passing” in the manual (info "(guix) Bootloader Configuration"). Right, I have read that section and I am using it for my root devices. But I have no idea how to use it for these drives as well. When I check /etc, the luks_script file is not there, so it seems it is not persisted across root pivot? And even if it would be persisted, I have no idea how GRUB should even know *how* to unlock these drives. > It’s optional (the messages are harmless) but it allows you to simplify > your config. Sure, they are harmless, but less non-actionable messages in the logs are always better. I will try to send a patch for this later this week. Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
