From: David Sterba <dsterba@suse.cz>
To: Nicholas D Steeves <nsteeves@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs wiki, add Parrot as production user
Date: Sat, 28 Sep 2019 15:23:41 +0200 [thread overview]
Message-ID: <20190928132340.GY2751@suse.cz> (raw)
In-Reply-To: <871rw1du17.fsf@DigitalMercury.dynalias.net>
On Fri, Sep 27, 2019 at 10:38:44PM -0400, Nicholas D Steeves wrote:
> Hi David,
>
> David Sterba <dsterba@suse.cz> writes:
>
> > On Mon, Aug 26, 2019 at 06:55:47PM -0600, Chris Murphy wrote:
> >> https://blog.parrotlinux.org/parrot-4-4-release-notes/
> >>
> >> Looks like they switched to Btrfs by default for / and /home.
> >>
> >> I think they should be listed on
> >> https://btrfs.wiki.kernel.org/index.php/Production_Users
> >
> > Added, thanks for the tip.
>
> If this is the criteria for Production Users, then NeptuneOS can also be
> added. This distribution was an early adopter who defaulted to btrfs
> since sometime around 2014, using linux-3.13.11.
Can be added too.
> By the way, would you please document that the Debian kernel team
> backports fixes release-critical (eg: data loss) patches to their stable
> kernel, provides a recent mainline kernel via stable-backports (or
> $codename-backports), and finally also provides recent btrfs-progs via
> that same stable-backports source? (I've been responsible for
> btrfs-progs backports since 2016)
But this is too detailed for an overview page. Each
vendor/distro/company should have some sort of documentation about that
(wiki, product landing page, etc).
> It might also be worth noting that the Debian installer doesn't yet
> support installation to subvolumes, the Ubuntu installer doesn't support
> configuration of subvolumes, and I think neither does Calamares installer
> (@ and @home are hard-coded like in Ubuntu IIRC).
Same.
> Also--to my alarm--the upstream Calamares installer defaults to
> compress=lzo, with no way for the user to opt-out. IMHO this should be
> documented for the benefit of conservative users who wish to avoid the
> once-a-year newly-found compression bug.
Documented yes (and perhaps reported) but not on the community wiki.
prev parent reply other threads:[~2019-09-28 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 0:55 Btrfs wiki, add Parrot as production user Chris Murphy
2019-08-27 12:46 ` David Sterba
2019-09-28 2:38 ` Nicholas D Steeves
2019-09-28 4:58 ` Andrei Borzenkov
2019-09-28 13:23 ` David Sterba [this message]
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=20190928132340.GY2751@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=nsteeves@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 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.