From: Kai Lueke <kailuke@microsoft.com>
Date: Fri, 22 Jul 2022 13:09:21 +0000 (+0200)
Subject: man: Document mask workaround for sysext images
X-Git-Tag: v252-rc1~601^2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F24084%2Fhead;p=thirdparty%2Fsystemd.git

man: Document mask workaround for sysext images

A read-only /usr may ship a sysext image by default and the user wants
to opt out. Currently it's not clear how to do this.
Document that a /dev/null symlink in /etc/extensions/ works to "mask" a
sysext image in a folder with lower precedence.
---

diff --git a/man/systemd-sysext.xml b/man/systemd-sysext.xml
index d7f5d2f37f8..42e8e12df97 100644
--- a/man/systemd-sysext.xml
+++ b/man/systemd-sysext.xml
@@ -108,7 +108,9 @@
     accessed.</para>
 
     <para>Note that there is no concept of enabling/disabling installed system extension images: all
-    installed extension images are automatically activated at boot.</para>
+    installed extension images are automatically activated at boot. However, you can place a symlink
+    to <filename>/dev/null</filename> in <filename>/etc/extensions/</filename> to "mask" an image with
+    the same name in a folder with lower precedence.</para>
 
     <para>A simple mechanism for version compatibility is enforced: a system extension image must carry a
     <filename>/usr/lib/extension-release.d/extension-release.<replaceable>$name</replaceable></filename>