summaryrefslogtreecommitdiffstats
path: root/docs/INCOMPATIBILITIES.md
diff options
context:
space:
mode:
authorDmitry V. Levin <ldv@strace.io>2024-04-27 10:00:00 +0200
committerLuca Boccassi <luca.boccassi@gmail.com>2024-04-27 12:11:13 +0200
commitc309b9e9c3e56a89d0f11ae40f5c088ac5cbccee (patch)
tree92d118874a2e3cbc01a54e31a3ac0932e5734945 /docs/INCOMPATIBILITIES.md
parentFix spelling errors found by Lintian (diff)
downloadsystemd-c309b9e9c3e56a89d0f11ae40f5c088ac5cbccee.tar.xz
systemd-c309b9e9c3e56a89d0f11ae40f5c088ac5cbccee.zip
treewide: fix a few typos in NEWS, docs, comments, and log messages
Diffstat (limited to 'docs/INCOMPATIBILITIES.md')
-rw-r--r--docs/INCOMPATIBILITIES.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/INCOMPATIBILITIES.md b/docs/INCOMPATIBILITIES.md
index 332f1ef3d9..784f3a2c02 100644
--- a/docs/INCOMPATIBILITIES.md
+++ b/docs/INCOMPATIBILITIES.md
@@ -30,7 +30,7 @@ Many of the incompatibilities are specific to distribution-specific extensions o
* Early boot runlevels as they are used by some distributions are no longer supported. i.e. "fake", distribution-specific runlevels such as "S" or "b" cannot be used with systemd.
* On SysV systems changes to init scripts or any other files that define the boot process (such as /etc/fstab) usually had an immediate effect on everything started later. This is different on systemd-based systems where init script information and other boot-time configuration files are only reread when "systemctl daemon-reload" is issued. (Note that some commands, notably "systemctl enable"/"systemctl disable" do this implicitly however.) This is by design, and a safety feature, since it ensures that half-completed changes are not read at the wrong time.
* Multiple entries for the same mount path in /etc/fstab are not supported. In systemd there's only a single unit definition for each mount path read at any time. Also the listing order of mounts in /etc/fstab has no effect, mounts are executed in parallel and dependencies between them generated automatically depending on path prefixes and source paths.
-* systemd's handling of the existing "nofail" mount option in /etc/fstab is stricter than it used to be on some sysvinit distributions: mount points that fail and are not listed as "nofail" will cause the boot to be stopped, for security reasons, as we we should not permit unprivileged code to run without everything listed — and not expressly exempted through "nofail" — being around. Hence, please mark all mounts where booting shall proceed regardless whether they succeeded or not with "nofail"
+* systemd's handling of the existing "nofail" mount option in /etc/fstab is stricter than it used to be on some sysvinit distributions: mount points that fail and are not listed as "nofail" will cause the boot to be stopped, for security reasons, as we should not permit unprivileged code to run without everything listed — and not expressly exempted through "nofail" — being around. Hence, please mark all mounts where booting shall proceed regardless whether they succeeded or not with "nofail"
* Some SysV systems support an "rc.local" script that is supposed to be called "last" during boot. In systemd, the script is supported, but the semantics are less strict, as there is simply no concept of "last service", as the boot process is event- and request-based, parallelized and compositive. In general, it's a good idea to write proper unit files with properly defined dependencies, and avoid making use of rc.local.
* systemd assumes that the UID boundary between system and regular users is a choice the distribution makes, and not the administrator. Hence it expects this setting as compile-time option to be picked by the distribution. It will _not_ check /etc/login.defs during runtime.