GNU bug report logs - #37851
Grub installation only checks for encrypted /boot folder

Previous Next

Full log

View this message in rfc822 format

From: Miguel Arruga Vivas <rosen644835 <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 37851 <at> debbugs.gnu.org
Subject: bug#37851: Grub installation only checks for encrypted /boot folder
Date: Sun, 27 Oct 2019 02:00:31 +0100

[Message part 1 (text/plain, inline)]

Hi Ludo’,

El Tue, 22 Oct 2019 16:12:49 +0200
Ludovic Courtès <ludo <at> gnu.org> escribió:
> Hola Miguel,
> 
> Miguel Arruga Vivas <rosen644835 <at> gmail.com> skribis:
> > (...)
> > +cryptomount -a  
> 
> Does that cause GRUB to mount all the LUKS partitions it was aware of
> at installation time, or does it cause it to scan all the partitions
> in search of a LUKS signature?

That patch is the first one, it mounts everything it can find, unlike
this one.

The only option I've seen was to modify boot-parameters (as in #35394,
wink wink nudge nudge) in order to store the needed partitions.  I've
reduced it this time to one patch, is it somehow easier to read this
way?  I could split it in two stages (one add the boot-parameters
field, the other one to make use of it) or squash the three for the
other feature into one if that easier for the review.  The main issues
I've found is that the source of the device-mappings needed for boot up
has to be declared by the UUID to ensure they are not system
dependent.  Also, the warning is shown several times and the message
isn't quite good, any idea how to fix/improve this?

Happy hacking!
Miguel

[0001-system-Use-of-mapped-devices-for-boot-process.patch (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.