From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Read before you deploy btrfs + zstd
Date: Wed, 15 Nov 2017 20:06:42 +0000 (UTC) [thread overview]
Message-ID: <pan$ce8bd$92de8589$64a02ff8$89689fba@cox.net> (raw)
In-Reply-To: CAK5rZE6gC-7pmAJSrrHEfEXVFdZ51MOwAKugHpmihrm6LwEnFQ@mail.gmail.com
Imran Geriskovan posted on Wed, 15 Nov 2017 20:16:56 +0200 as excerpted:
> On 11/15/17, Martin Steigerwald <martin@lichtvoll.de> wrote:
>> Somehow I am happy that I still have a plain Ext4 for /boot. :)
>
> You may use uncompressed btrfs for /boot.
> Both Syslinux (my choice) and Grub supports it.
And I've been running grub2 with compress=lzo on my /boot for years, now,
without issue.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-11-15 20:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 22:50 Read before you deploy btrfs + zstd David Sterba
2017-11-14 7:34 ` Martin Steigerwald
2017-11-14 9:45 ` Paul Jones
2017-11-14 12:38 ` Austin S. Hemmelgarn
2017-11-15 20:23 ` Duncan
2017-11-16 14:31 ` Dmitrii Tcvetkov
2017-11-14 18:49 ` David Sterba
2017-11-14 19:43 ` Martin Steigerwald
2017-11-14 18:53 ` David Sterba
2017-11-15 14:39 ` David Sterba
2017-11-15 16:22 ` Martin Steigerwald
2017-11-15 18:16 ` Imran Geriskovan
2017-11-15 20:06 ` Duncan [this message]
2017-11-15 20:09 ` Nick Terrell
2017-11-21 16:22 ` David Sterba
2017-11-28 21:31 ` Nick Terrell
2017-11-28 23:49 ` David Sterba
2017-11-29 0:44 ` Nick Terrell
2017-12-05 15:54 ` David Sterba
2017-12-05 20:36 ` Nick Terrell
2017-11-29 13:24 ` Austin S. Hemmelgarn
2017-11-29 19:29 ` Andrei Borzenkov
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='pan$ce8bd$92de8589$64a02ff8$89689fba@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.