From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: Re: [pve-devel] [RFC pve-kernel-meta 0/5] unify boot-mode config
Date: Wed, 2 Feb 2022 10:03:05 +0100 [thread overview]
Message-ID: <897a7e1f-929f-24cc-41af-dcbf1158102c@proxmox.com> (raw)
In-Reply-To: <20220201220331.3491615-1-s.ivanov@proxmox.com>
On 01.02.22 23:03, Stoiko Ivanov wrote:
> patch 3 drops systemd-boot and uses grub for both boot-modes, hopefully
> unifying the boot-experience and causing less confusion (currently I suggest
> to look at the screen while booting to find out which boot-loader is used)
>
> (Sadly systemd-boot (which I would prefer, justifiably)
> won't get support for legacy boot)
>
The thing is, non-uefi systems will become more rare anyhow, so why
bother with that? The simplicity of systemd-boot is worth the few (?)
confusion - I mean what exactly is there confusing anyway, if most relevant
actions can be handled through our tool anyway?
I'm not definitive yet, but currently rather tending to NACK that.
next prev parent reply other threads:[~2022-02-02 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 22:03 Stoiko Ivanov
2022-02-01 22:03 ` [pve-devel] [RFC pve-kernel-meta 1/5] rename pve-efiboot-manual-kernels to proxmox-boot-manual-kernels Stoiko Ivanov
2022-02-01 22:03 ` [pve-devel] [RFC pve-kernel-meta 2/5] proxmox-boot: add reinit subcommand Stoiko Ivanov
2022-02-01 22:03 ` [pve-devel] [RFC pve-kernel-meta 3/5] proxmox-boot: keep EFI and legacy bootloaders in sync Stoiko Ivanov
2022-02-01 22:03 ` [pve-devel] [RFC pve-kernel-meta 4/5] proxmox-boot: use grub for UEFI boot Stoiko Ivanov
2022-02-01 22:03 ` [pve-devel] [RFC pve-kernel-meta 5/5] proxmox-boot: install grub in esp/EFI/BOOT/BOOTX64.EFI Stoiko Ivanov
2022-02-02 9:03 ` Thomas Lamprecht [this message]
2022-02-02 14:28 ` [pve-devel] [RFC pve-kernel-meta 0/5] unify boot-mode config Stoiko Ivanov
2022-02-02 14:42 ` Thomas Lamprecht
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=897a7e1f-929f-24cc-41af-dcbf1158102c@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@proxmox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox