Re: trying to understand how the /boot/loader symlink is supposed to work.
- From: Daniel Drake <drake endlessm com>
- To: Colin Walters <walters verbum org>
- Cc: Leon Woestenberg <leon sidebranch com>, ostree-list gnome org, Carlo Caione <carlo endlessm com>
- Subject: Re: trying to understand how the /boot/loader symlink is supposed to work.
- Date: Fri, 2 Feb 2018 10:32:56 -0400
On Fri, Feb 2, 2018 at 10:13 AM, Colin Walters <walters verbum org> wrote:
What at least for Fedora Atomic we settled on is a model where
the bootloader and its data are installed *once*, and never updated again.
I'm curious why you went with this model. Is it just because it's an
unsolved problem? What if the bootloader has a bug that needs to be
fixed, or a security issue?
Anyways it's a big messy topic, and gets into again how the distribution
is built. I'm just describing what we sort of settled on, but it's
by no means the *only* way one could do things. If someone has better
ideas, I'd love to discuss. Particularly if someone has a design for how
updates to the bootloader itself should work. (Is anyone using e.g. UEFI+ostree
actually updating the copy of grub.x64 or whatever on the ESP?)
We are just starting a project to update the bootloader files on the ESP.
https://github.com/endlessm/eos-boot-helper/pull/178
Daniel
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]