From: zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze)
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36876@debbugs.gnu.org, Jesse Gibbons <jgibbons2357@gmail.com>
Subject: bug#36876: guix system delete-generations removes custom boot menu entries
Date: Wed, 28 Aug 2019 11:38:45 -0400 [thread overview]
Message-ID: <87lfvdpaey.fsf@sdf.lonestar.org> (raw)
In-Reply-To: <87sgps6p6c.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 23 Aug 2019 14:28:59 +0200")
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
Hi Ludo,
Ludovic Courtès <ludo@gnu.org> writes:
> I agree with Danny here that parsing the GRUB config wouldn’t be great.
>
> We have information about the user’s extra menu entries. The issue, as
> I see it, as that this information is lost once the system is
> instantiated.
>
> But! We have the <boot-parameters> 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
> ‘delete-generations’. <menu-entry> records are bootloader-independent,
> which is good.
>
> How does that sound?
Would that involve appending an additional field to <boot-parameters>
for storing the previous entries? I think that would have the pleasant
side-effect of making the code for deployment/reconfiguration simpler :)
Regards,
Jakob
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-08-28 15:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 15:48 bug#36876: guix system delete-generations removes custom boot menu entries Jesse Gibbons
2019-08-05 16:05 ` Jakob L. Kreuze
2019-08-06 3:12 ` Jesse Gibbons
2019-08-06 13:22 ` Jakob L. Kreuze
2019-08-06 16:32 ` Danny Milosavljevic
2019-08-06 16:35 ` Danny Milosavljevic
2019-08-06 18:27 ` Jakob L. Kreuze
2019-08-23 12:28 ` Ludovic Courtès
2019-08-28 15:38 ` Jakob L. Kreuze [this message]
2019-08-28 21:39 ` Ludovic Courtès
2019-08-29 8:02 ` Ludovic Courtès
2019-08-29 23:35 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfvdpaey.fsf@sdf.lonestar.org \
--to=zerodaysfordays@sdf.lonestar.org \
--cc=36876@debbugs.gnu.org \
--cc=jgibbons2357@gmail.com \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.