diff options
author | Lennart Poettering <lennart@poettering.net> | 2020-08-18 15:11:06 +0200 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2020-08-19 15:46:07 +0200 |
commit | caf6bd166f6521e1e33a25c39bb2e1b05d61b733 (patch) | |
tree | e51ba617202cdf4281ae93295e42e67d929e8d79 /man/homed.conf.xml | |
parent | 1b13600948b9fc5d35b3b643d02e5323f75dd682 (diff) | |
download | systemd-caf6bd166f6521e1e33a25c39bb2e1b05d61b733.tar.gz |
homed: default to "btrfs" as fs type in the LUKS backend
Apparently both Fedora and suse default to btrfs now, it should hence be
good enough for us too.
This enables a bunch of really nice things for us, most importanly we
can resize home directories freely (i.e. both grow *and* shrink) while
online. It also allows us to add nice subvolume based home directory
snapshotting later on.
Also, whenever we mention the three supported types, alaways mention
them in alphabetical order, which is also our new order of preference.
Diffstat (limited to 'man/homed.conf.xml')
-rw-r--r-- | man/homed.conf.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/man/homed.conf.xml b/man/homed.conf.xml index 2c5f3355d3..d43a83de3e 100644 --- a/man/homed.conf.xml +++ b/man/homed.conf.xml @@ -63,9 +63,9 @@ <varlistentry> <term><varname>DefaultFileSystemType=</varname></term> <listitem><para>When using <literal>luks</literal> as storage (see above), selects the default file - system to use inside the user's LUKS volume. Takes one of <literal>ext4</literal>, - <literal>xfs</literal> or <literal>btrfs</literal>. If not specified defaults to - <literal>ext4</literal>. This setting has no effect if a different storage mechanism is used. The + system to use inside the user's LUKS volume. Takes one of <literal>btrfs</literal>, + <literal>ext4</literal> or <literal>xfs</literal>. If not specified defaults to + <literal>btrfs</literal>. This setting has no effect if a different storage mechanism is used. The file system type selected on the <command>homectl</command> command line always takes precedence.</para></listitem> </varlistentry> |