From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#36876: guix system delete-generations removes custom boot menu entries Date: Fri, 23 Aug 2019 14:28:59 +0200 Message-ID: <87sgps6p6c.fsf@gnu.org> References: <20190731094857.28829b11@gmail.com> <8736ifzjfe.fsf@sdf.lonestar.org> 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]:59086) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i18hg-00006k-Sf for bug-guix@gnu.org; Fri, 23 Aug 2019 08:30:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i18hf-0007nJ-Nz for bug-guix@gnu.org; Fri, 23 Aug 2019 08:30:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:58643) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i18he-0007ld-NT for bug-guix@gnu.org; Fri, 23 Aug 2019 08:30:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1i18he-0001VV-HH for bug-guix@gnu.org; Fri, 23 Aug 2019 08:30:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <8736ifzjfe.fsf@sdf.lonestar.org> (Jakob L. Kreuze's message of "Mon, 05 Aug 2019 12:05:57 -0400") 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: "Jakob L. Kreuze" Cc: 36876@debbugs.gnu.org, Jesse Gibbons Hello! zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze) skribis: > Jesse Gibbons writes: > >> I dual-booted Guix with another gnu/linux-libre distro. >> My configuration includes the other distro in the grub menu. When I run >> "sudo guix system delete-generations" the changes to the grub menu drop >> the other distro with the older system generations of guix. >> >> My current work-around for this is to run "guix system reconfigure ..." >> which includes the boot menu entries specified in the configuration. > > Thanks for reporting this; it's a rather serious issue. The problem lies > in the 'reinstall-bootloader' procedure. Chiefly, it uses the default > bootloader configuration for whatever it can find using > 'lookup-bootloader-by-name' and generates menu entries for the > generations reachable from '%system-profile', which is quite a bit > different from how 'guix system reconfigure' produces the bootloader > configuration. It really isn't ideal. To quote a comment in > 'system.scm': "[i]t will be enough to allow the system to boot." > > I don't think this should be _too_ hard to fix. To me, parsing the > installed Grub configuration to get existing menu entries seems like a > logical step forward. I agree with Danny here that parsing the GRUB config wouldn=E2=80=99t be gr= eat. We have information about the user=E2=80=99s extra menu entries. The issue= , as I see it, as that this information is lost once the system is instantiated. But! We have the structure, that gets serialized with the system, and which we could extend with those extra menu entries. That way, the info would be preserved, and we can restore them upon =E2=80=98delete-generations=E2=80=99. records are bootloader-= independent, which is good. How does that sound? Thanks, Ludo=E2=80=99.