From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#37851: Grub installation only checks for encrypted /boot folder Date: Tue, 22 Oct 2019 16:12:49 +0200 Message-ID: <87lftc27j2.fsf@gnu.org> References: <20191021130709.21d6ac20@gmail.com> <20191021144758.3d8cfe95@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:44622) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iMuuG-0002Hl-GW for bug-guix@gnu.org; Tue, 22 Oct 2019 10:13:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iMuuE-0005V2-BU for bug-guix@gnu.org; Tue, 22 Oct 2019 10:13:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:51424) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iMuuE-0005Uw-7K for bug-guix@gnu.org; Tue, 22 Oct 2019 10:13:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iMuuE-0000PW-1B for bug-guix@gnu.org; Tue, 22 Oct 2019 10:13:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20191021144758.3d8cfe95@gmail.com> (Miguel Arruga Vivas's message of "Mon, 21 Oct 2019 14:47:58 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Miguel Arruga Vivas Cc: 37851@debbugs.gnu.org Hola Miguel, Miguel Arruga Vivas skribis: > Attached can be found a workaround to mount all encrypted partitions. > There is no way to tell the devices to mount without changing > boot-parameters, where I'd add another field with the needed mapped > devices (a traversal onto the mapped-device dependency tree > of /gnu/store). Do you think this is a good idea? At least I think > it's the best way to encode the dependencies into the grub.cfg file, > even though the typical graph will contain 0 or 1 nodes. > From 9b50e2d8eb8b744595a54a9543993eb4e3813742 Mon Sep 17 00:00:00 2001 > From: =3D?UTF-8?q?Miguel=3D20=3DC3=3D81ngel=3D20Arruga=3D20Vivas?=3D > > Date: Mon, 21 Oct 2019 14:35:02 +0200 > Subject: [PATCH] system: Mount luks devices on boot. > > * gnu/bootloader/grub.scm (grub-configuration-file)[builder]: Mount all > encrypted partitions. > --- > gnu/bootloader/grub.scm | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/gnu/bootloader/grub.scm b/gnu/bootloader/grub.scm > index d984d5f5e3..b29477ec71 100644 > --- a/gnu/bootloader/grub.scm > +++ b/gnu/bootloader/grub.scm > @@ -369,6 +369,7 @@ keymap ~a~%" keymap))))) > (format port > "# This file was generated from your Guix configuratio= n. Any changes > # will be lost upon reconfiguration. > +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? In the latter case that wouldn=E2=80=99t be great, but in the former case it sounds like we could go ahead (well, with a comment above explaining what this does. :-)). Thanks for working on it! Ludo=E2=80=99.