From: Goffredo Baroncelli <kreijack@inwind.it>
To: Kai Krakow <hurikhan77+btrfs@gmail.com>
Cc: Forza <forza@tnonline.net>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Matthew Warren <matthewwarren101010@gmail.com>
Subject: Re: raid1 root device with efi
Date: Tue, 12 Mar 2024 19:55:20 +0100 [thread overview]
Message-ID: <c8a4e4d4-8fed-4815-8cd0-fd6df354e99e@inwind.it> (raw)
In-Reply-To: <CAMthOuPQDMWGOA9O+StwnmUhZXxsF3ePZKMBgDZdPZ8gxQ+sdg@mail.gmail.com>
On 12/03/2024 13.39, Kai Krakow wrote:
> Am Mo., 11. März 2024 um 20:26 Uhr schrieb Goffredo Baroncelli
> <kreijack@libero.it>:
[...]
>> I am quite sure that grub access a btrfs filesystem dynamically, without using a
>> pre-stored table with the location of a file.
>
> Yes, it probably can work its way through the various trees but the
> extent resolver and reader is very basic.
>
> This means, at least for now: do not let anything touch the boot files
> grub is using, and do not use compression, then it SHOULD work well
> most of the time.
>
> I'd still avoid complex filesystems involved in the grub booting process.
>
The other options are not better: using a dedicated filesystem is not without
shortcomings: do you think that the implementations of VFAT in the UEFI bioseS
are better ? The fact that the FAT filesystem is far simpler is a plus but...
As sd-boot user, I like the simplicity of this bootloader. But in some
context it is limited. My efi partition has a size of 1GB, but now the
kernel+initrd images are in the order of 100MB....so it can't contain more than
10-12 images. This is fine for the standard user, but it may be not enough
for some hobbyist...
grub is over-complicated, but it can withstand complex filesystem layout...
May be a kernel with a dedicated initrd which kexec the real kernel ?
BR
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2024-03-12 18:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 20:39 raid1 root device with efi Matt Zagrabelny
2024-03-08 21:02 ` Qu Wenruo
2024-03-08 21:46 ` Matthew Warren
2024-03-08 21:48 ` Matt Zagrabelny
2024-03-08 21:54 ` Matthew Warren
2024-03-08 21:58 ` Matt Zagrabelny
2024-03-10 17:57 ` Forza
2024-03-11 14:34 ` Kai Krakow
2024-03-11 19:26 ` Goffredo Baroncelli
2024-03-12 12:39 ` Kai Krakow
2024-03-12 18:55 ` Goffredo Baroncelli [this message]
2024-03-27 20:21 ` Matt Zagrabelny
2024-03-28 4:03 ` Andrei Borzenkov
2024-03-28 11:42 ` Forza
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=c8a4e4d4-8fed-4815-8cd0-fd6df354e99e@inwind.it \
--to=kreijack@inwind.it \
--cc=forza@tnonline.net \
--cc=hurikhan77+btrfs@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=matthewwarren101010@gmail.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