mirror of
https://github.com/systemd/systemd.git
synced 2024-11-23 10:13:34 +08:00
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.
This commit is contained in:
parent
c87bce7d28
commit
7352a0093f
@ -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>
|
||||
|
Loading…
Reference in New Issue
Block a user