GNU bug report logs - #26339
[PATCH 00/18] wip: Support non grub bootloaders.

Previous Next

Package: guix-patches;

Reported by: Mathieu Othacehe <m.othacehe <at> gmail.com>

Date: Sun, 2 Apr 2017 13:51:01 UTC

Severity: important

Tags: patch

Done: Mathieu Othacehe <m.othacehe <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: ludo <at> gnu.org (Ludovic Courtès)
To: Mathieu Othacehe <m.othacehe <at> gmail.com>
Cc: 26339 <at> debbugs.gnu.org, David Craven <david <at> craven.ch>
Subject: bug#26339: [PATCH 02/18] system: Add extlinux support.
Date: Tue, 09 May 2017 22:40:23 +0200
Hello!

Mathieu Othacehe <m.othacehe <at> gmail.com> skribis:

>> Woow, that was fast!  :-)
>
> I had time to kill during a train trip :)

I like train trips too.  :-)

>> Good question!  I guess we need to store the name of the bootloader type
>> in the “parameters” file, and then look it up upon switch-generation?
>> But maybe we also need to store a reference to the bootloader package so
>> that it isn’t GC’d?
>
> We have three options for switch-generation :
>
> 1. Do not reinstall bootloader, only update config (current behaviour).
>
> -> It was ok with one bootloader, it's more problematic with multiple
> bootloaders. For example switching between two generations with two
> different bootloaders.

OTOH, if it turns out to be safer to keep the current bootloader, which
is likely I think, then perhaps it’s best to not try to change.

I mean, I prefer a rollback that doesn’t roll back the bootloader over a
rollback that tries to do something smart and makes the system
unbootable.

Of course, if we can make it safe to reinstall the previous bootloader,
that’s optimal.

> 2. Save the bootloader type in "parameters" and reinstall bootloader
> (current bootloader build, not necessarily the one used when creating
> this generation)
>
> -> It's the option I choose in my series.

OK.  I guess I should read that part of the series.

> 3. Same as 2. but also save bootloader used (store reference) and add a
> gc-root to keep it around.
>
> I can try to implement option 3 if you're ok ?

Hmm maybe, I need to investigate.

>> I think the most important is to make sure that our current use case,
>> where people always use GRUB, doesn’t break.
>
> With my basic-one-unencrypted-partition setup it work fine, but it would
> be great if people with more complex setup could try this serie :)

Did you try something like:

  make check-system TESTS="encrypted-root-os btrfs-root-os"

?  It takes quite a bit of time to run, but it’s a good starting point
to test these things.

Thanks!

Ludo’.




This bug report was last modified 7 years and 210 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.