path: root/Software/systemd/APIFileSystems.mdwn
diff options
authorLennartPoettering <LennartPoettering@web>2015-02-20 07:48:02 -0800
committerwww <>2015-02-20 07:48:02 -0800
commite2db989f263e75400b7b4168a972904deed9e7f4 (patch)
tree3fbc4f2e23d46e30fcacb635f8436b50c294efd2 /Software/systemd/APIFileSystems.mdwn
parent0cbf0598d1a6a82175a56bd92646ec9988abe7d2 (diff)
Diffstat (limited to 'Software/systemd/APIFileSystems.mdwn')
1 files changed, 1 insertions, 0 deletions
diff --git a/Software/systemd/APIFileSystems.mdwn b/Software/systemd/APIFileSystems.mdwn
index a7600ad8..169a51cf 100644
--- a/Software/systemd/APIFileSystems.mdwn
+++ b/Software/systemd/APIFileSystems.mdwn
@@ -22,6 +22,7 @@ The Linux kernel provides a number of different ways for userspace to communicat
* `/dev/hugepages` as a userspace API for allocating "huge" memory pages (X)
* `/sys/fs/fuse/connections` for exposing kernel FUSE connections to userspace (X)
* `/sys/firmware/efi/efivars` for exposing firmware variables to userspace
All these _API file systems_ are mounted during very early boot-up of systemd and are generally not listed in `/etc/fstab`. Depending on the used kernel configuration some of these API file systems might not be available and others might exist instead. As these interfaces are important for kernel-to-userspace and userspace-to-userspace communication they are mounted automatically and without configuration or interference by the user. Disabling or changing their parameters might hence result in applications breaking as they can no longer access the interfaces they need.
Even though the default settings of these file systems should normally be suitable for most setups, in some cases it might make sense to change the mount options, or possibly even disable some of these file systems.