From: raid5atemyhomework via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "47442@debbugs.gnu.org" <47442@debbugs.gnu.org>
Subject: bug#47442: guix system delete-generations does not use bootloader configuration
Date: Mon, 29 Mar 2021 02:01:24 +0000 [thread overview]
Message-ID: <DKQDGI2bWCFisUBsqNg0GbiuNshOnpA0iRwyMqLPLcIEQuhWsjp9w41I6BZo_f7WChR8DzokpviJuEccJqHydneIFIFreDiwqs_UplsiR_A=@protonmail.com> (raw)
In-Reply-To: <UEumGHB0DHPN4Px9M_hdXYJ1Z3ap-1-yGXhaQKk5-m_7c2dxwsItslSQJzhQ0DQls5UUjQffWL3WaakI31iGIf_V7iDoWP9fLvN2hP9L-sU=@protonmail.com>
Note as well that keyboard layouts at Grub time are also broken by this. As the keyboard layout is used when accepting passphrases for cryptodisks, this can leave a user potentially unable to boot at all without expert GRUB knowledge, if they selected a passphrase including characters not available on default US keyboard.
An alternative solution is to split the `grub.cfg` file into two pieces: one containing the bootloader configuration settings, the other containing the entries. Then `reinstall-bootloader` just changes the entries.
On alternative bootloaders, there is usually little to no configuration.
* `depthcharge` - No configuration.
* `extlinux` - Only `timeout` configuration.
* `u-boot` - Based on `extlinux` (so only `timeout` configuration).
So a possible design would be to have a "split" generation of the configuration file.
This affects how `bootloader-configuration-file-generator` is used, however. This affects three points:
* `gnu/machine/ssh.scm` - This is given a `bootloader-configuration` from the actual OS on the machine, so probably OK to use this legacy interface.
* `gnu/system.scm` - Like the above, given a `bootloader-configuration` from the actual OS on the machine.
* `gnu/scripts/system.scm` - This is the problem point identified before.
Yet another solution would be to augment `boot-parameters` with the fields of `bootloader-configuration`, but that violates DRY --- fields added to `bootloader-configuration` in the future need to be added to `boot-parameters` as well, so I think this is undesirable.
Thanks
raid5atemyhomework
next prev parent reply other threads:[~2021-03-29 2:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 4:42 bug#47442: guix system delete-generations does not use bootloader configuration raid5atemyhomework via Bug reports for GNU Guix
2021-03-29 2:01 ` raid5atemyhomework via Bug reports for GNU Guix [this message]
2021-07-23 15:32 ` raid5atemyhomework via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='DKQDGI2bWCFisUBsqNg0GbiuNshOnpA0iRwyMqLPLcIEQuhWsjp9w41I6BZo_f7WChR8DzokpviJuEccJqHydneIFIFreDiwqs_UplsiR_A=@protonmail.com' \
--to=bug-guix@gnu.org \
--cc=47442@debbugs.gnu.org \
--cc=raid5atemyhomework@protonmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).