Re: Btrfs wiki, add Parrot as production user

[Nicholas D Steeves <nsteeves@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1513 bytes --]

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.

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)

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).

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.


Regards,
Nicholas

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]