From debbugs-submit-bounces@debbugs.gnu.org Tue Aug 06 12:32:40 2019 Received: (at 36876) by debbugs.gnu.org; 6 Aug 2019 16:32:40 +0000 Received: from localhost ([127.0.0.1]:37706 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hv2O8-000193-Fm for submit@debbugs.gnu.org; Tue, 06 Aug 2019 12:32:40 -0400 Received: from dd26836.kasserver.com ([85.13.145.193]:52560) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hv2O6-00018n-Dj for 36876@debbugs.gnu.org; Tue, 06 Aug 2019 12:32:39 -0400 Received: from localhost (77.117.217.54.wireless.dyn.drei.com [77.117.217.54]) by dd26836.kasserver.com (Postfix) with ESMTPSA id 26A29336212E; Tue, 6 Aug 2019 18:32:36 +0200 (CEST) Date: Tue, 6 Aug 2019 18:32:34 +0200 From: Danny Milosavljevic To: zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze) Subject: Re: bug#36876: guix system delete-generations removes custom boot menu entries Message-ID: <20190806183234.5e7714c2@scratchpost.org> In-Reply-To: <8736ifzjfe.fsf@sdf.lonestar.org> References: <20190731094857.28829b11@gmail.com> <8736ifzjfe.fsf@sdf.lonestar.org> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-unknown-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/AX2tY92m4G8OqHM5qxO6rfy"; protocol="application/pgp-signature" X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 36876 Cc: 36876@debbugs.gnu.org, Jesse Gibbons X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) --Sig_/AX2tY92m4G8OqHM5qxO6rfy Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Jakob, keep in mind that switching back to a previous generation could also entail= a switch of bootloader projects. It does you no good to parse the grub confi= g to find menu entries and then append them to u-boot. Fundamentally, it would be best if either the bootloader is part of the sta= te that guix manages (and each time uses), or it isn't; not both. Current situation: * If you select a previous generation in the boot menu, then the state that= is selected does NOT include the bootloader (i.e. it doesn't change the bootlo= ader or the bootloader config). * If you do "guix system reconfigure", the state that is saved includes only the bootloader in the boot sector (simplified) but not the bootloader insta= ller or the bootloader derivation. * If you do "guix system delete-generations", the state that is restored do= es not include the bootloader installer and previous bootloader configuration. Clearly, it's not nice to have these different things happen. It would be better if we retained the generation's bootloader installer and bootloader config and reinstalled it on each of those. So, I would suggest to retain the following for each system generation: * The bootloader package derivation * The bootloader config derivation * The bootloader installer derivation And to install the bootloader each time using the latter. This introduces cycles--not sure whether that's a problem or not. For the GC I think it's not a problem. --Sig_/AX2tY92m4G8OqHM5qxO6rfy Content-Type: application/pgp-signature Content-Description: Digitale Signatur von OpenPGP -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl1Jq6IACgkQ5xo1VCww uqX+MAf/SuzaBCxBH2Shxkh3c3JUJYnVPc9oW+MVvCou/sAwjeUkgI9LVz4lgaXA aLmknvllkHpWWi3sofBXqWQXqHSpu6PlJPMSSOadcPKTYc2J1oK0rMK4TWmLHqZk eqGdy9pAN06Fr56Vcl/OEqnEwCodFJ/Xv9kxGj5vS+6WtpDbdLDSmvQs2YkPAcc/ KaoNZBwYneMjAJV25EAq0i5jhCh3TmQkibl3FDdt8veURo+oAVf6B1gpXU12XRiS /PF2x6SERRMObz0jQXyGlzi6anFwXkRj9NKozfoKzwfncbqrTux/3EIDeUTQYvZS bkZ0ZDqXk6Lu40Byi54Oekn3XGnumg== =x0pE -----END PGP SIGNATURE----- --Sig_/AX2tY92m4G8OqHM5qxO6rfy--