unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Lilah Tascheter <lilah@lunabee.space>
Cc: guix-devel@gnu.org, Hilton Chain <hako@ultrarare.space>
Subject: Re: [RFC] proposal for refactoring bootloaders
Date: Mon, 19 Feb 2024 12:18:14 +0200	[thread overview]
Message-ID: <ZdMq5n5jT7QR47zi@3900XT> (raw)
In-Reply-To: <118b8271dc53b5d0e5f245fac57181fed0db86da.camel@lunabee.space>

[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]

On Fri, Feb 16, 2024 at 02:33:02AM -0600, Lilah Tascheter wrote:
> one more quick change that I've realized will be necessary: add a
> bootloader-targets field to boot-parameters. some bootloaders would
> need target info to know where to install config files, and
> reinstall-bootloader doesn't have access to the operating-system
> record. rollbacks to generations pre-field addition shouldn't be an
> issue with this either, as existing bootloaders (sans depthcharge?) do
> just fine without targets.
> 
> all in all, bootloader-installer and bootloader-config-file-installer
> would be procedures that return gexps, with the following signatures:
> 
> * (installer entries #:key bootcfg mount-offset generation old-entries
>    store-crypto-devices store-directory-prefix locale)
> * (config-file-installer entries #:key package targets mount-offset
>    generation old-entries store-crypto-devices store-directory-prefix
>    locale)
> 
> mount-offset is the current target, and old-entries becomes an alist with
> generation numbers.

The current bootloader system started as grub only and then grew more
capabilities for other things too.  It should be possible to flash
u-boot separately and then use grub-efi (or something like it) but it's
not currently supported out of the box.  I look forward to seeing how
this might look.

-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-02-19 10:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15  7:28 [RFC] proposal for refactoring bootloaders Lilah Tascheter
2024-02-16  8:33 ` Lilah Tascheter
2024-02-19 10:18   ` Efraim Flashner [this message]
2024-02-24  1:27     ` Felix Lechner via Development of GNU Guix and the GNU System distribution.

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=ZdMq5n5jT7QR47zi@3900XT \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=hako@ultrarare.space \
    --cc=lilah@lunabee.space \
    /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).