summaryrefslogtreecommitdiff
path: root/man/systemd-sysext.xml
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2022-12-01 22:41:47 +0100
committerLennart Poettering <lennart@poettering.net>2023-04-05 20:55:15 +0200
commit9ea811914fce034c2fe9d5f7d5712d49462ac6a4 (patch)
tree8923f84ccfc9b4a41d23d449658c7b9ccd5cf4b7 /man/systemd-sysext.xml
parentf1f42aeaf1ba5444f4a4e0f2d0d4fb304fc34a49 (diff)
downloadsystemd-9ea811914fce034c2fe9d5f7d5712d49462ac6a4.tar.gz
man: document image policy syntax and semantics, and the hooks in the various components
Diffstat (limited to 'man/systemd-sysext.xml')
-rw-r--r--man/systemd-sysext.xml23
1 files changed, 21 insertions, 2 deletions
diff --git a/man/systemd-sysext.xml b/man/systemd-sysext.xml
index 96e40ddf95..2b7a87f510 100644
--- a/man/systemd-sysext.xml
+++ b/man/systemd-sysext.xml
@@ -89,7 +89,12 @@
carrying large binary images, however are still useful for carrying symlinks to them. The primary place
for installing system extensions is <filename>/var/lib/extensions/</filename>. Any directories found in
these search directories are considered directory based extension images; any files with the
- <filename>.raw</filename> suffix are considered disk image based extension images.</para>
+ <filename>.raw</filename> suffix are considered disk image based extension images. When invoked in the
+ initrd, the additional directory <filename>/.extra/sysext/</filename> is included in the directories that
+ are searched for extension images. Note however, that by default a tighter image policy applies to images
+ found there, though, see below. This directory is populated by
+ <citerefentry><refentrytitle>systemd-stub</refentrytitle><manvolnum>7</manvolnum></citerefentry> with
+ extension images found in the system's EFI System Partition.</para>
<para>During boot OS extension images are activated automatically, if the
<filename>systemd-sysext.service</filename> is enabled. Note that this service runs only after the
@@ -230,6 +235,19 @@
not.</para></listitem>
</varlistentry>
+ <varlistentry>
+ <term><option>--image-policy=<replaceable>policy</replaceable></option></term>
+
+ <listitem><para>Takes an image policy string as argument, as per
+ <citerefentry><refentrytitle>systemd.image-policy</refentrytitle><manvolnum>7</manvolnum></citerefentry>. The
+ policy is enforced when operating on system extension disk images. If not specified defaults to
+ <literal>root=verity+signed+encrypted+unprotected+absent:usr=verity+signed+encrypted+unprotected+absent</literal>,
+ i.e. only the root and <filename>/usr/</filename> file systems in the image are used. When run in the
+ initrd and operating on a system extension image stored in the <filename>/.extra/sysext/</filename>
+ directory a slightly stricter policy is used by default:
+ <literal>root=signed+absent:usr=signed+absent</literal>, see above for details.</para></listitem>
+ </varlistentry>
+
<xi:include href="standard-options.xml" xpointer="no-pager" />
<xi:include href="standard-options.xml" xpointer="no-legend" />
<xi:include href="standard-options.xml" xpointer="json" />
@@ -246,7 +264,8 @@
<title>See Also</title>
<para>
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
- <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>
+ <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
+ <citerefentry><refentrytitle>systemd-stub</refentrytitle><manvolnum>7</manvolnum></citerefentry>
</para>
</refsect1>