Group: Software/FSDG distributions/Filesystems
(→Block device layer: parabola: Add more precise infos) |
(→Block device layer: Add LUKS) |
||
Line 898: | Line 898: | ||
! Trisquel 11 (aramo) | ! Trisquel 11 (aramo) | ||
! Ututo S | ! Ututo S | ||
+ | |- | ||
+ | ! LUKS 1 | ||
+ | | <!-- Dragora --> | ||
+ | | <!-- Dynebolics --> | ||
+ | | <!-- Guix x86 GNU/Linux --> | ||
+ | | <!-- Guix HURD --> | ||
+ | | <!-- Hyperbola --> | ||
+ | | <!-- LibreCMC --> | ||
+ | | <!-- Parabola --> | ||
+ | {| class="wikitable sortable" border="1" | ||
+ | |- bgcolor="#6699ff" | ||
+ | |- | ||
+ | ! Packages and manual installation<ref name="manual-installation"></ref> | ||
+ | | {{yes|Yes: cryptsetup}} | ||
+ | |- | ||
+ | ! Graphical installer | ||
+ | | | ||
+ | |- | ||
+ | ! Rootfs | ||
+ | | {{yes}} | ||
+ | |} | ||
+ | | <!-- ProteanOS --> | ||
+ | | {{yes}} <!-- PureOS 10 (byzantium) --> | ||
+ | | <!-- Replicant 6.0 --> | ||
+ | | {{yes}} <!-- Trisquel 11 (aramo) --> | ||
+ | | <!-- Ututo S --> | ||
+ | |- | ||
+ | ! LUKS 2 | ||
+ | | <!-- Dragora --> | ||
+ | | <!-- Dynebolics --> | ||
+ | | <!-- Guix x86 GNU/Linux --> | ||
+ | | <!-- Guix HURD --> | ||
+ | | <!-- Hyperbola --> | ||
+ | | <!-- LibreCMC --> | ||
+ | | <!-- Parabola --> | ||
+ | {| class="wikitable sortable" border="1" | ||
+ | |- bgcolor="#6699ff" | ||
+ | |- | ||
+ | ! Packages and manual installation<ref name="manual-installation"></ref> | ||
+ | | {{yes|Yes: cryptsetup}} | ||
+ | |- | ||
+ | ! Graphical installer | ||
+ | | | ||
+ | |- | ||
+ | ! Rootfs | ||
+ | | {{yes|Yes but requires a /boot as GRUB only has partial LUKS2 support}} | ||
+ | |} | ||
+ | | <!-- ProteanOS --> | ||
+ | | {{yes}} <!-- PureOS 10 (byzantium) --> | ||
+ | | <!-- Replicant 6.0 --> | ||
+ | | {{yes}} <!-- Trisquel 11 (aramo) --> | ||
+ | | <!-- Ututo S --> | ||
+ | |- | ||
|- | |- | ||
! LVM2 | ! LVM2 |
Revision as of 01:10, 9 September 2023
Contents
Introduction
This article is about filesystems support and might be extended to take into account block device technologies too like LVM,RAID, etc.
Choosing a filesystem
Using the default filesystem currently proposed during the installation of your distribution is a good idea. It makes sure that the filesystem is properly integrated and that the distribution trusts it enough (with data integrity, and security[1]) to propose it by default.
Known issues and limitations
- With NTFS the free software implementation lacks the ability to repair the filesystem without nonfree software, so if you have data in NTFS filesystem it would be a good idea to move it to other filesystems.
- ReiserFS 3 will be removed from Linux in 2025.[2]
Defaults
The defaults filesystems used are often a good indication of what filesystems are best supported by the distribution.
Distribution | Defaults | Comments | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Dragora | ||||||||||||||
Dynebolics | ||||||||||||||
Guix | ||||||||||||||
Hyperbola | ||||||||||||||
LibreCMC | ||||||||||||||
Parabola | ||||||||||||||
ProteanOS | ||||||||||||||
PureOS 10 (byzantium) |
|
|
||||||||||||
Replicant 6.0 | ||||||||||||||
Trisquel 10 (nabia) | ||||||||||||||
Ututo S |
Filesystems
Distributions | ||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Dragora | Dynebolics | Guix i686-linux and x86_64-linux (x86 GNU/Linux) | Guix i586-gnu (HURD) | Hyperbola | LibreCMC | Parabola | ProteanOS | PureOS 10 (byzantium) | Replicant 6.0 | Trisquel 10 (nabia) | Ututo S | |||||||||||||||||||||||||||||||||||||
btrfs |
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||
exfat |
|
|
||||||||||||||||||||||||||||||||||||||||||||||
ext2 |
|
|
||||||||||||||||||||||||||||||||||||||||||||||
ext4 |
|
|
|
|
|
|
||||||||||||||||||||||||||||||||||||||||||
f2fs |
|
|
|
|
||||||||||||||||||||||||||||||||||||||||||||
fat |
|
|
|
|
||||||||||||||||||||||||||||||||||||||||||||
hfs | No[10] | No[11] | No[12] |
|
No[13] |
|
||||||||||||||||||||||||||||||||||||||||||
hfs+ | No[14] | No[15] | No[16] |
|
No[17] |
|
||||||||||||||||||||||||||||||||||||||||||
jfs |
|
|
||||||||||||||||||||||||||||||||||||||||||||||
minix |
|
|||||||||||||||||||||||||||||||||||||||||||||||
nilfs2 |
|
|
||||||||||||||||||||||||||||||||||||||||||||||
ntfs |
|
|
||||||||||||||||||||||||||||||||||||||||||||||
reiser4 |
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||
reiserfs |
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||
xfs |
|
|
||||||||||||||||||||||||||||||||||||||||||||||
Dragora | Dynebolics | Guix i686-linux and x86_64-linux (x86 GNU/Linux) | Guix i586-gnu (HURD) | Hyperbola | LibreCMC | Parabola | ProteanOS | PureOS 10 (byzantium) | Replicant 6.0 | Trisquel 10 (nabia) | Ututo S | |||||||||||||||||||||||||||||||||||||
Distributions |
Block device layer
Distributions | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Dragora | Dynebolics | Guix i686-linux and x86_64-linux (x86 GNU/Linux) | Guix i586-gnu (HURD) | Hyperbola | LibreCMC | Parabola | ProteanOS | PureOS 10 (byzantium) | Replicant 6.0 | Trisquel 11 (aramo) | Ututo S | |||||||
LUKS 1 |
|
Yes | Yes | |||||||||||||||
LUKS 2 |
|
Yes | Yes | |||||||||||||||
LVM2 |
|
Yes | Yes |
References
- ↑ See the Unmaintained filesystems as a threat vector lwn.net article for more details.
-
↑ 2.02.12.22.3
The Linux kernel documentation for the REISERFS_FS option tells that:
Reiserfs is deprecated and scheduled to be removed from the kernel
in 2025. If you are still using it, please migrate to another
filesystem or tell us your usecase for reiserfs.
- ↑ 3.03.13.23.33.43.53.63.73.83.9 This tells if that filesystem can be used in a system.scm system definition.
- ↑ 4.004.014.024.034.044.054.064.074.084.094.104.114.124.134.144.15 Since users simply run commands manually during the manual installation, they can easily use the (packaged) tools to create new filesystems and add them to /etc/fstab for automatic mounting.
- ↑ The installation fails with an error.
- ↑ There is no HURD installer yet.
- ↑ After creating the rootfs with mkfs.ext4 from Guix, in Replicant, it says "Corrupted <vendor> SD card" in the notification bar.
- ↑ We can easily view the card content with "File Manager". It also detects a new MicroSD card when it is just formatted.
- ↑ The installation fails with an error.
- ↑ There is no hfsutils package.
- ↑ There is no hfsutils package.
- ↑ There is no hfsutils package.
- ↑ There is no hfsutils repository in the manifest.
- ↑ There is no hfsprogs package.
- ↑ There is no hfsprogs package.
- ↑ There is no hfsprogs package.
- ↑ There is no hfsprogs repository in the manifest.
- ↑ The installation fails with an error.
- ↑ The graphical installer complains about some UUID related issue
- ↑ In the graphical installer, the installation fails with: "The installer has encountered an unexpected problem. [...]", and we then get a stacktrace. If we manually install with the same system.scm we'd probably get the exact same stacktrace.
- ↑ Once installed, the rootfs is mounted with FUSE and ntfs-3g.
- ↑ The installation succeeds, but then sudo and policykit are broken due to wrong permissions. So users can't install any software. It's also a very bad idea to use NTFS since there is at the time of writing no way to safely repair corrupted NTFS filesystems with free software: The only tools we have are in ntfs-3g and they are way too experimental and dangerous so they are probably not shipped by any distribution.
- ↑ 23.023.123.2 According to the reiser 4 wiki, upstream Linux has no reiser4 support.