From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 40236@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
"Efraim Flashner" <efraim@flashner.co.il>,
"Jonathan Brielmaier" <jonathan.brielmaier@web.de>
Subject: [bug#40236] [PATCH] doc: Suggest Btrfs with compression instead of ext4 for root partition.
Date: Mon, 01 Jun 2020 00:49:36 -0400 [thread overview]
Message-ID: <871rmz5r1b.fsf@gmail.com> (raw)
In-Reply-To: <87y2p83650.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Sun, 31 May 2020 09:39:23 +0200")
Hello Pierre,
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> Now that 37305 is merged, we can revisit this issue.
>
> 1. This patch only includes a documentation update.
> 2. We could make Btrfs the default in the graphical installer.
Is it already possible to choose Btrfs in the graphical installer? I
guess so, but I haven't tried.
> 3. We would probably need to update the tests, at least for the
> latter.
> As mentioned above, I think it's safe to enable Btrfs without subvolume,
> with Zstd compression.
My personal experience also tells me so, but it is true that it is still
newer and more exotic than EXT4.
> For subvolumes, we would need to implement the corresponding tests.
What kind of tests are you referring to? There is a test in (gnu tests
install) that install root on a Btrfs subvolume and boot from it, but
I'm pretty sure the graphical installer doesn't have support for
configuring a Btrfs subvolumes layout.
> Thoughts?
I'm in favor of encouraging the use of Btrfs with compression given that
Guix puts more stress on storage space compared to traditional distros,
and that I've had only positive experiences with Btrfs in the last year
and half or so that I've used it on my machines.
Maxim
next prev parent reply other threads:[~2020-06-01 4:50 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 8:35 [bug#40236] [PATCH] doc: Suggest Btrfs with compression instead of ext4 for root partition Pierre Neidhardt
2020-03-31 1:52 ` Maxim Cournoyer
2020-03-31 7:52 ` Pierre Neidhardt
2020-03-31 14:53 ` Pierre Neidhardt
2020-03-31 23:20 ` Maxim Cournoyer
2020-04-01 7:00 ` Pierre Neidhardt
2020-05-02 13:29 ` Pierre Neidhardt
2020-05-02 13:50 ` Marius Bakke
2020-05-02 13:58 ` Pierre Neidhardt
2020-05-02 19:03 ` Maxim Cournoyer
2020-05-03 7:01 ` Pierre Neidhardt
2020-05-04 15:22 ` Maxim Cournoyer
2020-04-01 21:28 ` Ludovic Courtès
2020-04-02 7:15 ` Pierre Neidhardt
2020-04-02 8:04 ` Ludovic Courtès
2020-04-02 10:36 ` Jonathan Brielmaier
2020-04-04 1:28 ` Maxim Cournoyer
2020-04-06 20:20 ` Pierre Neidhardt
2020-04-06 20:42 ` Jonathan Brielmaier
2020-04-07 7:07 ` Pierre Neidhardt
2020-04-08 3:18 ` Maxim Cournoyer
2020-04-09 20:12 ` Efraim Flashner
2020-04-10 7:39 ` Pierre Neidhardt
2020-04-10 8:24 ` Efraim Flashner
2020-04-10 9:04 ` Pierre Neidhardt
2020-04-14 2:20 ` Maxim Cournoyer
2020-04-14 6:53 ` Pierre Neidhardt
2020-05-31 7:39 ` Pierre Neidhardt
2020-05-31 7:55 ` Efraim Flashner
2020-06-01 4:21 ` Maxim Cournoyer
2020-06-01 6:16 ` Efraim Flashner
2020-06-01 7:48 ` Pierre Neidhardt
2020-06-01 18:29 ` Maxim Cournoyer
2020-05-31 21:07 ` Ludovic Courtès
2020-06-01 5:03 ` Maxim Cournoyer
2020-06-02 13:37 ` Pierre Neidhardt
2020-06-03 20:00 ` bug#40236: " Ludovic Courtès
2020-06-04 9:17 ` [bug#40236] " Pierre Neidhardt
2020-06-01 4:49 ` Maxim Cournoyer [this message]
2020-03-31 12:09 ` Jonathan Brielmaier
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rmz5r1b.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=40236@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=jonathan.brielmaier@web.de \
--cc=ludo@gnu.org \
--cc=mail@ambrevar.xyz \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).