diff options
| author | Dieter Plaetinck <dieter@plaetinck.be> | 2011-05-17 22:12:31 +0200 |
|---|---|---|
| committer | Dieter Plaetinck <dieter@plaetinck.be> | 2011-05-17 22:12:33 +0200 |
| commit | 281b49fd3dd0984805a9dc435d1a2c36c675eb4d (patch) | |
| tree | 95f11e52db0f54c2fc413d9eb98b1ca7cdbf3636 /src | |
| parent | 3c9483c433ec200a8cb35cb978ae4d9e9c994f3c (diff) | |
btrfs: ask for mountpoint
This commit supports using a btrfs directly.
Despite recommendations and strong suggestions to somehow prevent users from
doing this (and using subvolumes instead) - see
http://mailman.archlinux.org/pipermail/arch-releng/2010-December/001341.html -
it's taking way to long for code to support this to go into AIF.
It's now the users' choice to choose what they want and deal with the
consequences.
Diffstat (limited to 'src')
| -rw-r--r-- | src/core/libs/lib-blockdevices-filesystems.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/core/libs/lib-blockdevices-filesystems.sh b/src/core/libs/lib-blockdevices-filesystems.sh index 13160c9..212253d 100644 --- a/src/core/libs/lib-blockdevices-filesystems.sh +++ b/src/core/libs/lib-blockdevices-filesystems.sh @@ -73,7 +73,7 @@ fs_on[lvm-pv]=${fs_on_lvm_pv[@]} fs_on[lvm-vg]=${fs_on_lvm_vg[@]} fs_on[dm_crypt]=${fs_on_dm_crypt[@]} -fs_mountable=(ext2 ext3 ext4 nilfs2 xfs jfs vfat reiserfs) +fs_mountable=(btrfs ext2 ext3 ext4 nilfs2 xfs jfs vfat reiserfs) fs_label_mandatory=('lvm-vg' 'lvm-lv' 'dm_crypt') fs_label_optional=('swap' 'ext2' 'ext3' 'ext4' 'reiserfs' 'nilfs2' 'xfs' 'jfs' 'vfat') |