diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2024-09-23 12:01:21 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2024-09-23 12:12:06 +0200 |
| commit | 7352a0093f4ef96c361be22337cde3296d79da01 (patch) | |
| tree | 005d11b7257122d618cef5fcbc8abb61c970654b /man/os-release.xml | |
| parent | man: reword some sentences with umbiguous subjects (diff) | |
| download | systemd-7352a0093f4ef96c361be22337cde3296d79da01.tar.xz systemd-7352a0093f4ef96c361be22337cde3296d79da01.zip | |
man: say that SYSEXT_SCOPE=initrd also applies to exitrds
We generally do _not_ want the same sysexts to be loaded in both initrd and
exitrd phases. The environment is completely different and it's unlikely that
the same code can be useful in both places. Nevertheless, it can be useful in
_some_ cases, for example when the sysexts contains debugging tools.
I think we don't need to differentiate between initrds and exitrds through
SYSEXT_SCOPE, because the two types are made available in completely different
locations and loaded through a different mechanism, with very little chance of
an initrd being loaded as an exitrd without an explicit admin action (or the
other way around). So let's not complicate our code or definitions by an
explicit "exitrd" sysext designator, but just clarify that "initrd" also
encompasses exitrds in this context.
Diffstat (limited to 'man/os-release.xml')
| -rw-r--r-- | man/os-release.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/man/os-release.xml b/man/os-release.xml index 6fb3e1bb1a..99e31ba24e 100644 --- a/man/os-release.xml +++ b/man/os-release.xml @@ -594,10 +594,10 @@ <listitem><para>Takes a space-separated list of one or more of the strings <literal>system</literal>, <literal>initrd</literal> and <literal>portable</literal>. This field is only supported in <filename>extension-release.d/</filename> files and indicates what environments - the system extension is applicable to: i.e. to regular systems, to initrds, or to portable service - images. If unspecified, <literal>SYSEXT_SCOPE=system portable</literal> is implied, i.e. any system - extension without this field is applicable to regular systems and to portable service environments, - but not to initrd environments.</para> + the system extension is applicable to: i.e. to regular systems, to initrds and exitrds, or to + portable service images. If not specified, <literal>SYSEXT_SCOPE=system portable</literal> is + implied, i.e. any system extension without this field is applicable to regular systems and to + portable service environments, but not to initrd/exitrd environments.</para> <xi:include href="version-info.xml" xpointer="v250"/></listitem> </varlistentry> |