Merging upstream version 4.23.0.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 58 insertions, 22 deletions

diff --git a/upstream/fedora-rawhide/man7/systemd.special.7 b/upstream/fedora-rawhide/man7/systemd.special.7
index 43e5332d..6596f118 100644
--- a/upstream/fedora-rawhide/man7/systemd.special.7
+++ b/upstream/fedora-rawhide/man7/systemd.special.7
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.SPECIAL" "7" "" "systemd 255" "systemd.special"
+.TH "SYSTEMD\&.SPECIAL" "7" "" "systemd 256~rc3" "systemd.special"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -85,6 +85,7 @@ smartcard\&.target,
 sockets\&.target,
 soft\-reboot\&.target,
 sound\&.target,
+ssh\-access\&.target,
 storage\-target\-mode\&.target,
 suspend\&.target,
 swap\&.target,
@@ -94,12 +95,14 @@ system\-update\-pre\&.target,
 time\-set\&.target,
 time\-sync\&.target,
 timers\&.target,
+tpm2\&.target,
 umount\&.target,
 usb\-gadget\&.target,
 \-\&.slice,
+capsule\&.slice,
+machine\&.slice,
 system\&.slice,
 user\&.slice,
-machine\&.slice,
 \-\&.mount,
 dbus\&.service,
 dbus\&.socket,
@@ -847,6 +850,19 @@ This may be used to pull in usb gadget dynamically when UDC hardware is found\&.
 .sp
 Added in version 242\&.
 .RE
+.PP
+tpm2\&.target
+.RS 4
+This target is started automatically if a TPM2 device is discovered, either by the OS or by the firmware\&. It acts as synchronization point for services that require TPM2 device access\&. The target unit is enqueued by
+\fBsystemd-tpm2-generator\fR(8)
+if it detects that the firmware has discovered a TPM2 device but the OS kernel has not activated a driver for it yet\&. It is also pulled in whenever
+\fBsystemd-udevd.service\fR(8)
+discovers a TPM2 device\&. The target unit is ordered after the
+/dev/tpmrm0
+device node, so that it only becomes active once the TPM2 device is actually accessible\&. Early boot programs that intend to access the TPM2 device should hence order themselves after this target unit, but not pull it in\&.
+.sp
+Added in version 256\&.
+.RE
 .SS "Special Passive System Units"
 .PP
 A number of special system targets are defined that can be used to properly order boot\-up of optional services\&. These targets are generally not part of the initial boot transaction, unless they are explicitly pulled in by one of the implementing services\&. Note specifically that these
@@ -1000,6 +1016,17 @@ for this target unit to all SysV init script service units with an LSB header re
 facility\&.
 .RE
 .PP
+ssh\-access\&.target
+.RS 4
+Service and socket units that provide remote SSH secure shell access to the local system should pull in this unit and order themselves before this unit\&. It\*(Aqs supposed to act as a milestone indicating if and when SSH access into the system is available\&. It should only become active when an SSH port is bound for remote clients (i\&.e\&. if SSH is used as a local privilege escalation mechanism, it should
+\fInot\fR
+involve this target unit), regardless of the protocol choices, i\&.e\&. regardless if IPv4, IPv6 or
+\fBAF_VSOCK\fR
+is used\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 time\-set\&.target
 .RS 4
 Services responsible for setting the system clock (\fBCLOCK_REALTIME\fR) from a local source (such as a maintained timestamp file or imprecise real\-time clock) should pull in this target and order themselves before it\&. Services where approximate, roughly monotonic time is desired should be ordered after this unit, but not pull it in\&.
@@ -1113,6 +1140,25 @@ The root slice is the root of the slice hierarchy\&. It usually does not contain
 Added in version 206\&.
 .RE
 .PP
+machine\&.slice
+.RS 4
+By default, all virtual machines and containers registered with
+\fBsystemd\-machined\fR
+are found in this slice\&. This is pulled in by
+systemd\-machined\&.service\&.
+.sp
+Added in version 206\&.
+.RE
+.PP
+capsule\&.slice
+.RS 4
+By default, all capsules encapsulated in
+capsule@\&.service
+are found in this slice\&.
+.sp
+Added in version 255\&.
+.RE
+.PP
 system\&.slice
 .RS 4
 By default, all system services started by
@@ -1129,16 +1175,6 @@ systemd\-logind\&.service\&.
 .sp
 Added in version 206\&.
 .RE
-.PP
-machine\&.slice
-.RS 4
-By default, all virtual machines and containers registered with
-\fBsystemd\-machined\fR
-are found in this slice\&. This is pulled in by
-systemd\-machined\&.service\&.
-.sp
-Added in version 206\&.
-.RE
 .SH "UNITS MANAGED BY THE USER SERVICE MANAGER"
 .SS "Special User Units"
 .PP
@@ -1146,7 +1182,7 @@ When systemd runs as a user instance, the following special units are available:
 .PP
 default\&.target
 .RS 4
-This is the main target of the user session, started by default\&. Various services that compose the normal user session should be pulled into this target\&. In this regard,
+This is the main target of the user service manager, started by default when the service manager is invoked\&. Various services that compose the normal user session should be pulled into this target\&. In this regard,
 default\&.target
 is similar to
 multi\-user\&.target
@@ -1155,6 +1191,14 @@ in the system instance, but it is a real unit, not an alias\&.
 Added in version 242\&.
 .RE
 .PP
+capsule@\&.target
+.RS 4
+This is the main target of capsule service managers, started by default, instantiated with the capsule name\&. This may be used to define different sets of units that are started for different capsules via generic unit definitions\&. For details about capsules see
+\fBcapsule@.service\fR(5)\&.
+.sp
+Added in version 255\&.
+.RE
+.PP
 In addition, the following units are available which have definitions similar to their system counterparts:
 exit\&.target,
 shutdown\&.target,
@@ -1290,15 +1334,7 @@ Added in version 247\&.
 .RE
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd.unit\fR(5),
-\fBsystemd.service\fR(5),
-\fBsystemd.socket\fR(5),
-\fBsystemd.target\fR(5),
-\fBsystemd.slice\fR(5),
-\fBbootup\fR(7),
-\fBsystemd-fstab-generator\fR(8),
-\fBuser@.service\fR(5)
+\fBsystemd\fR(1), \fBsystemd.unit\fR(5), \fBsystemd.service\fR(5), \fBsystemd.socket\fR(5), \fBsystemd.target\fR(5), \fBsystemd.slice\fR(5), \fBbootup\fR(7), \fBsystemd-fstab-generator\fR(8), \fBuser@.service\fR(5)
 .SH "NOTES"
 .IP " 1." 4
 Running Services After the Network Is Up