From 519c2f0d6b343d140f7e08e3eb0f46708c023b4a Mon Sep 17 00:00:00 2001 From: Kai Lueke Date: Fri, 22 Jul 2022 15:09:21 +0200 Subject: [PATCH] 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. --- man/systemd-sysext.xml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) 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. Note that there is no concept of enabling/disabling installed system extension images: all - installed extension images are automatically activated at boot. + installed extension images are automatically activated at boot. However, you can place a symlink + to /dev/null in /etc/extensions/ to "mask" an image with + the same name in a folder with lower precedence. A simple mechanism for version compatibility is enforced: a system extension image must carry a /usr/lib/extension-release.d/extension-release.$name -- 2.47.3