From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
L p R n d n <guix@lprndn.info>
Subject: Re: GRUB fallback mechanism [was Re: Brain storming cool Guix features]
Date: Sun, 13 Jan 2019 21:58:50 +0100 [thread overview]
Message-ID: <87sgxw2s1h.fsf@gnu.org> (raw)
In-Reply-To: <87fttxookn.fsf@elephly.net> (Ricardo Wurmus's message of "Sat, 12 Jan 2019 16:58:16 +0100")
Ricardo Wurmus <rekado@elephly.net> skribis:
> swedebugia <swedebugia@riseup.net> writes:
>
>> Leo Famulari <leo@famulari.name> skrev: (11 januari 2019 23:32:12 CET)
[...]
>>>Apparently GRUB has a feature that records a "fallback" system to boot
>>>if booting fails.
>>>
>>>Maybe when reconfiguring, Guix could set the current system as the
>>>fallback so that it would always boot.
>>>
>>>If we did that, we'd want to warn the user somehow... not sure how to
>>>achieve that.
>>>
>>>Discussion of this feature at NixOS:
>>>
>>>https://github.com/NixOS/nixpkgs/issues/26332
>>
>> I don't think automatic fallback is a good idea because it unnecessarily complicates a now well working simple part of the OS.
>> KISS is a nice principle.
>
> I think exposing this GRUB feature would be good, even if not enabled by
> default. It does not seem very complicated and can be very useful for
> some users.
I agree.
> Unfortunately, it doesn’t help us when GRUB itself is broken with an
> upgrade, which I think is what was suggested earlier.
We’ll have to assume (and ensure!) this doesn’t happen…
Ludo’.
next prev parent reply other threads:[~2019-01-13 20:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 12:11 Brain storming cool Guix features Joshua Branson
2019-01-04 16:01 ` Ricardo Wurmus
2019-01-05 13:59 ` Joshua Branson
2019-01-05 17:06 ` Ricardo Wurmus
2019-01-13 20:18 ` Joshua Branson
2019-01-13 21:36 ` bug#25453: Keyboard layout configuration Ludovic Courtès
2019-01-13 22:49 ` nee
2019-01-13 22:49 ` nee
2019-01-15 22:21 ` bug#25453: " Ludovic Courtès
2019-01-15 22:21 ` Ludovic Courtès
2019-03-12 19:34 ` bug#25453: " Taylan Kammer
2019-03-15 18:19 ` nee
2019-03-21 22:23 ` Taylan Kammer
2019-03-12 19:34 ` Taylan Kammer
2019-03-20 23:07 ` Ludovic Courtès
2019-03-20 23:07 ` Ludovic Courtès
2019-01-16 13:10 ` Ludovic Courtès
2019-01-16 13:10 ` bug#25453: " Ludovic Courtès
2019-01-04 16:10 ` Brain storming cool Guix features Pierre Neidhardt
2019-01-04 16:14 ` John Soo
2019-01-04 16:58 ` znavko
2019-01-06 13:44 ` Amirouche Boubekki
2019-01-06 16:33 ` swedebugia
2019-01-06 20:04 ` Amirouche Boubekki
2019-01-07 16:48 ` L p R n d n
2019-01-07 18:16 ` Joshua Branson
2019-01-11 22:32 ` GRUB fallback mechanism [was Re: Brain storming cool Guix features] Leo Famulari
2019-01-12 12:59 ` swedebugia
2019-01-12 15:58 ` Ricardo Wurmus
2019-01-13 20:58 ` Ludovic Courtès [this message]
2019-01-14 14:15 ` L p R n d n
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=87sgxw2s1h.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=guix@lprndn.info \
--cc=rekado@elephly.net \
/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.