From: Goffredo Baroncelli <kreijack@inwind.it>
To: Chris Murphy <lists@colorremedies.com>
Cc: David Sterba <dsterba@suse.cz>,
Andrei Borzenkov <arvidjaar@gmail.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Does GRUB btrfs support log tree?
Date: Wed, 13 Nov 2019 19:54:26 +0100 [thread overview]
Message-ID: <4480d47f-1b1e-d99d-e480-b31220433340@inwind.it> (raw)
In-Reply-To: <CAJCQCtQm_5L9uvH53O3Qby3Ktwpvsc2_6rUhkBLGeD07RP5a7Q@mail.gmail.com>
On 13/11/2019 18.00, Chris Murphy wrote:
>> The GRUB-fs should have the following main requirements:
>> - allow the atomicity guarantee
>> - allow molti-disk setup
>> - allow grub to update some file (grubenv come me as first)
>> - it should require a simple implementation (easy to porting to multiple system, which basically means linux, *bsd and solaris ?)
>> - the speed should be not important
> Plausibly we're most of the way there already, adapting the existing
> "BIOS Boot" partition.
>
Unfortunately the BIOS Boot partition (which means basically FAT), doesn't have support for "atomicity" nor multidisk..
BR
G.Baroncelli
--
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:[~2019-11-13 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 9:47 Does GRUB btrfs support log tree? Chris Murphy
2019-10-25 9:50 ` Chris Murphy
2019-10-26 7:12 ` Andrei Borzenkov
2019-10-27 20:05 ` Chris Murphy
2019-11-04 19:34 ` David Sterba
2019-11-11 19:37 ` Chris Murphy
2019-11-12 20:04 ` Goffredo Baroncelli
2019-11-13 17:00 ` Chris Murphy
2019-11-13 18:54 ` Goffredo Baroncelli [this message]
2019-11-13 21:50 ` Chris Murphy
2019-11-14 8:18 ` Andrei Borzenkov
2019-11-17 23:24 ` Chris Murphy
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=4480d47f-1b1e-d99d-e480-b31220433340@inwind.it \
--to=kreijack@inwind.it \
--cc=arvidjaar@gmail.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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