Merging upstream version 4.23.0.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
author: Daniel Baumann <daniel.baumann@progress-linux.org> 2024-06-17 10:52:03 +0000
committer: Daniel Baumann <daniel.baumann@progress-linux.org> 2024-06-17 10:52:03 +0000
commit: 932e4432596447eb9331cc2a2bb74a26a35b4efc (patch)
tree: 95161711ea07fd64f0c82d6e7943024c033dd5a8 /upstream/fedora-rawhide/man5
parent: Adding debian version 4.22.0-1. (diff)
download: manpages-l10n-932e4432596447eb9331cc2a2bb74a26a35b4efc.tar.xz
manpages-l10n-932e4432596447eb9331cc2a2bb74a26a35b4efc.zip
242 files changed, 3660 insertions, 1906 deletions
diff --git a/upstream/fedora-rawhide/man5/BUILDINFO.5 b/upstream/fedora-rawhide/man5/BUILDINFO.5
index 13f1ccde..c7f0a361 100644
--- a/upstream/fedora-rawhide/man5/BUILDINFO.5
+++ b/upstream/fedora-rawhide/man5/BUILDINFO.5
@@ -2,12 +2,12 @@
 .\"     Title: buildinfo
 .\"    Author: [see the "Authors" section]
 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
-.\"      Date: 2024-01-25
+.\"      Date: 2024-04-14
 .\"    Manual: Pacman Manual
-.\"    Source: Pacman 6.0.2
+.\"    Source: Pacman 6.1.0
 .\"  Language: English
 .\"
-.TH "BUILDINFO" "5" "2024\-01\-25" "Pacman 6\&.0\&.2" "Pacman Manual"
+.TH "BUILDINFO" "5" "2024\-04\-14" "Pacman 6\&.1\&.0" "Pacman Manual"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -34,7 +34,7 @@ BUILDINFO \- Makepkg package build information file
 This manual page describes the format of a BUILDINFO file found in the root of a package created by makepkg\&. The file contains a description of the package\(cqs build environment\&. The information is formatted in key\-value pairs separated by a \fI=\fR, one value per line\&. Arrays are represented multiple keys with the same value\&.
 .SH "DESCRIPTION"
 .sp
-This is a description of the contents of version \fI1\fR of the BUILDINFO file format\&.
+This is a description of the contents of version \fI2\fR of the BUILDINFO file format\&.
 .PP
 \fBformat\fR
 .RS 4
@@ -86,6 +86,19 @@ The directory where the package was built\&.
 The directory from which makepkg was executed\&.
 .RE
 .PP
+\fBbuildtool\fR
+.RS 4
+The name of the tool ecosystem used to set up the build environment\&. Used for defining a spec for reproducible builds, e\&.g\&. the source of the
+\fBmakepkg.conf\fR(5)
+used\&.
+.RE
+.PP
+\fBbuildtoolver\fR
+.RS 4
+The full version of the
+\fIbuildtool\fR, for example: "$pkgver\-$pkgrel\-$pkgarch"\&.
+.RE
+.PP
 \fBbuildenv (array)\fR
 .RS 4
 The build environment specified in makepkg\&.conf\&.
@@ -142,17 +155,6 @@ Andrew Gregory <andrew\&.gregory\&.8@gmail\&.com>
 .sp -1
 .IP \(bu 2.3
 .\}
-Eli Schwartz <eschwartz@archlinux\&.org>
-.RE
-.sp
-.RS 4
-.ie n \{\
-\h'-04'\(bu\h'+03'\c
-.\}
-.el \{\
-.sp -1
-.IP \(bu 2.3
-.\}
 Morgan Adamiec <morganamilo@archlinux\&.org>
 .RE
 .sp
@@ -235,4 +237,15 @@ Nagy Gabor <ngaba@bibl\&.u\-szeged\&.hu>
 Dave Reisner <dreisner@archlinux\&.org>
 .RE
 .sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+Eli Schwartz <eschwartz@archlinux\&.org>
+.RE
+.sp
 For additional contributors, use git shortlog \-s on the pacman\&.git repository\&.
diff --git a/upstream/fedora-rawhide/man5/PKGBUILD.5 b/upstream/fedora-rawhide/man5/PKGBUILD.5
index c320a1e5..a81c3aa9 100644
--- a/upstream/fedora-rawhide/man5/PKGBUILD.5
+++ b/upstream/fedora-rawhide/man5/PKGBUILD.5
@@ -2,12 +2,12 @@
 .\"     Title: pkgbuild
 .\"    Author: [see the "Authors" section]
 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
-.\"      Date: 2024-01-25
+.\"      Date: 2024-04-14
 .\"    Manual: Pacman Manual
-.\"    Source: Pacman 6.0.2
+.\"    Source: Pacman 6.1.0
 .\"  Language: English
 .\"
-.TH "PKGBUILD" "5" "2024\-01\-25" "Pacman 6\&.0\&.2" "Pacman Manual"
+.TH "PKGBUILD" "5" "2024\-04\-14" "Pacman 6\&.1\&.0" "Pacman Manual"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -28,7 +28,7 @@
 .\" * MAIN CONTENT STARTS HERE *
 .\" -----------------------------------------------------------------
 .SH "NAME"
-PKGBUILD \- Arch Linux package build description file
+PKGBUILD \- Package build description file
 .SH "SYNOPSIS"
 .sp
 PKGBUILD
@@ -104,15 +104,7 @@ This field contains a URL that is associated with the software being packaged\&.
 .PP
 \fBlicense (array)\fR
 .RS 4
-This field specifies the license(s) that apply to the package\&. Commonly used licenses can be found in
-\fI/usr/share/licenses/common\fR\&. If you see the package\(cqs license there, simply reference it in the license field (e\&.g\&.,
-license=(\*(AqGPL\*(Aq))\&. If the package provides a license not available in
-\fI/usr/share/licenses/common\fR, then you should include it in the package itself and set
-license=(\*(Aqcustom\*(Aq)
-or
-license=(\*(Aqcustom:LicenseName\*(Aq)\&. The license should be placed in
-\fI$pkgdir/usr/share/licenses/$pkgname/\fR
-when building the package\&. If multiple licenses are applicable, list all of them:
+This field specifies the license(s) that apply to the package\&. If multiple licenses are applicable, list all of them:
 license=(\*(AqGPL\*(Aq \*(AqFDL\*(Aq)\&.
 .RE
 .PP
@@ -223,8 +215,6 @@ is one of five comparisons:
 <
 (less than)\&.
 .sp
-If the dependency name appears to be a library (ends with \&.so), makepkg will try to find a binary that depends on the library in the built package and append the version needed by the binary\&. Appending the version yourself disables automatic detection\&.
-.sp
 Additional architecture\-specific depends can be added by appending an underscore and the architecture name e\&.g\&.,
 \fIdepends_x86_64=()\fR\&.
 .RE
@@ -292,8 +282,6 @@ and
 <
 operators are invalid as only specific versions of a package may be provided\&.
 .sp
-If the provision name appears to be a library (ends with \&.so), makepkg will try to find the library in the built package and append the correct version\&. Appending the version yourself disables automatic detection\&.
-.sp
 Additional architecture\-specific provides can be added by appending an underscore and the architecture name e\&.g\&.,
 \fIprovides_x86_64=()\fR\&.
 .RE
@@ -421,7 +409,16 @@ If you create any variables of your own in any of these functions, it is recomme
 .RS 4
 The
 package()
-function is used to install files into the directory that will become the root directory of the built package and is run after all the optional functions listed below\&. The packaging stage is run using fakeroot to ensure correct file permissions in the resulting package\&. All other functions will be run as the user calling makepkg\&.
+function is used to install files into the directory that will become the root directory of the built package and is run after all the optional functions listed below\&. The packaging stage is run using fakeroot to ensure correct file permissions in the resulting package\&. All other functions will be run as the user calling makepkg\&. This function is run inside
+$srcdir\&.
+.RE
+.PP
+\fBverify() Function\fR
+.RS 4
+An optional
+verify()
+function can be specified to implement arbitrary source authentication\&. The function should return a non\-zero exit code when verification fails\&. This function is run before sources are extracted\&. This function is run inside
+$startdir\&.
 .RE
 .PP
 \fBprepare() Function\fR
@@ -432,7 +429,8 @@ function can be specified in which operations to prepare the sources for buildin
 build()
 function\&. The
 prepare()
-function is skipped when source extraction is skipped\&.
+function is skipped when source extraction is skipped\&. This function is run inside
+$srcdir\&.
 .RE
 .PP
 \fBbuild() Function\fR
@@ -441,7 +439,8 @@ The optional
 build()
 function is used to compile and/or adjust the source files in preparation to be installed by the
 package()
-function\&.
+function\&. This function is run inside
+$srcdir\&.
 .RE
 .PP
 \fBcheck() Function\fR
@@ -454,7 +453,8 @@ and
 package()
 functions\&. Be sure any exotic commands used are covered by the
 checkdepends
-array\&.
+array\&. This function is run inside
+$srcdir\&.
 .RE
 .sp
 All of the above variables such as $pkgname and $pkgver are available for use in the packaging functions\&. In addition, makepkg defines the following variables:
@@ -462,9 +462,6 @@ All of the above variables such as $pkgname and $pkgver are available for use in
 \fBsrcdir\fR
 .RS 4
 This contains the directory where makepkg extracts, or copies, all source files\&.
-.sp
-All of the packaging functions defined above are run starting inside
-$srcdir
 .RE
 .PP
 \fBpkgdir\fR
@@ -563,6 +560,8 @@ source=(\*(Aqdirectory::url#fragment?query\*(Aq)
 .sp
 Currently makepkg supports the Bazaar, Git, Subversion, Fossil and Mercurial version control systems\&. For other version control systems, manual cloning of upstream repositories must be done in the prepare() function\&.
 .sp
+Some VCS Sources like Git support pinning the checkout by a checksum of its content using deterministic export functionality like \(lqgit archive\(rq\&.
+.sp
 The source URL is divided into four components:
 .PP
 \fBdirectory\fR
@@ -620,7 +619,7 @@ source=(url?signed#fragment)\&. Currently only supported by Git\&.
 .RE
 .SH "EXAMPLE"
 .sp
-The following is an example PKGBUILD for the \fIpatch\fR package\&. For more examples, look through the build files of your distribution\(cqs packages\&. For those using Arch Linux, consult the Arch Build System (ABS) tree\&.
+The following is an example PKGBUILD for the \fIpatch\fR package\&. For more examples, look through the build files of your distribution\(cqs packages\&.
 .sp
 .if n \{\
 .RS 4
@@ -640,8 +639,8 @@ depends=(\*(Aqglibc\*(Aq)
 makedepends=(\*(Aqed\*(Aq)
 optdepends=(\*(Aqed: for "patch \-e" functionality\*(Aq)
 source=("ftp://ftp\&.gnu\&.org/gnu/$pkgname/$pkgname\-$pkgver\&.tar\&.xz"{,\&.sig})
-md5sums=(\*(Aqe9ae5393426d3ad783a300a338c09b72\*(Aq
-         \*(AqSKIP\*(Aq)
+sha256sums=(\*(Aq9124ba46db0abd873d0995c2ca880e81252676bb6c03e0a37dfc5f608a9b0ceb\*(Aq
+            \*(AqSKIP\*(Aq)
 
 build() {
         cd "$srcdir/$pkgname\-$pkgver"
@@ -699,17 +698,6 @@ Andrew Gregory <andrew\&.gregory\&.8@gmail\&.com>
 .sp -1
 .IP \(bu 2.3
 .\}
-Eli Schwartz <eschwartz@archlinux\&.org>
-.RE
-.sp
-.RS 4
-.ie n \{\
-\h'-04'\(bu\h'+03'\c
-.\}
-.el \{\
-.sp -1
-.IP \(bu 2.3
-.\}
 Morgan Adamiec <morganamilo@archlinux\&.org>
 .RE
 .sp
@@ -792,4 +780,15 @@ Nagy Gabor <ngaba@bibl\&.u\-szeged\&.hu>
 Dave Reisner <dreisner@archlinux\&.org>
 .RE
 .sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+Eli Schwartz <eschwartz@archlinux\&.org>
+.RE
+.sp
 For additional contributors, use git shortlog \-s on the pacman\&.git repository\&.
diff --git a/upstream/fedora-rawhide/man5/acct.5 b/upstream/fedora-rawhide/man5/acct.5
index 18d458e6..a140bc43 100644
--- a/upstream/fedora-rawhide/man5/acct.5
+++ b/upstream/fedora-rawhide/man5/acct.5
@@ -2,7 +2,7 @@
 .\"
 .\" SPDX-License-Identifier: Linux-man-pages-copyleft
 .\"
-.TH acct 5 2023-10-31 "Linux man-pages 6.06"
+.TH acct 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 acct \- process accounting file
 .SH SYNOPSIS
diff --git a/upstream/fedora-rawhide/man5/alpm-hooks.5 b/upstream/fedora-rawhide/man5/alpm-hooks.5
index f82c1e8a..15f4cafe 100644
--- a/upstream/fedora-rawhide/man5/alpm-hooks.5
+++ b/upstream/fedora-rawhide/man5/alpm-hooks.5
@@ -2,12 +2,12 @@
 .\"     Title: alpm-hooks
 .\"    Author: [see the "Authors" section]
 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
-.\"      Date: 2024-01-25
+.\"      Date: 2024-04-14
 .\"    Manual: Pacman Manual
-.\"    Source: Pacman 6.0.2
+.\"    Source: Pacman 6.1.0
 .\"  Language: English
 .\"
-.TH "ALPM\-HOOKS" "5" "2024\-01\-25" "Pacman 6\&.0\&.2" "Pacman Manual"
+.TH "ALPM\-HOOKS" "5" "2024\-04\-14" "Pacman 6\&.1\&.0" "Pacman Manual"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -176,17 +176,6 @@ Andrew Gregory <andrew\&.gregory\&.8@gmail\&.com>
 .sp -1
 .IP \(bu 2.3
 .\}
-Eli Schwartz <eschwartz@archlinux\&.org>
-.RE
-.sp
-.RS 4
-.ie n \{\
-\h'-04'\(bu\h'+03'\c
-.\}
-.el \{\
-.sp -1
-.IP \(bu 2.3
-.\}
 Morgan Adamiec <morganamilo@archlinux\&.org>
 .RE
 .sp
@@ -269,4 +258,15 @@ Nagy Gabor <ngaba@bibl\&.u\-szeged\&.hu>
 Dave Reisner <dreisner@archlinux\&.org>
 .RE
 .sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+Eli Schwartz <eschwartz@archlinux\&.org>
+.RE
+.sp
 For additional contributors, use git shortlog \-s on the pacman\&.git repository\&.
diff --git a/upstream/fedora-rawhide/man5/binfmt.d.5 b/upstream/fedora-rawhide/man5/binfmt.d.5
index f03a5a39..b52230ef 100644
--- a/upstream/fedora-rawhide/man5/binfmt.d.5
+++ b/upstream/fedora-rawhide/man5/binfmt.d.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "BINFMT\&.D" "5" "" "systemd 255" "binfmt.d"
+.TH "BINFMT\&.D" "5" "" "systemd 256~rc3" "binfmt.d"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,11 +23,15 @@
 binfmt.d \- Configure additional binary formats for executables at boot
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/binfmt\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /run/binfmt\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /usr/lib/binfmt\&.d/*\&.conf
+.RE
 .SH "DESCRIPTION"
 .PP
 At boot,
@@ -70,7 +74,12 @@ Packages should install their configuration files in
 /usr/local/lib/
 (local installs)\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. It is recommended to prefix all filenames with a two\-digit number and a dash, to simplify the ordering of the files\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. It is recommended to prefix all filenames with a two\-digit number and a dash, to simplify the ordering of the files\&. It is recommended to use the range 10\-40 for configuration files in
+/usr/
+and the range 60\-90 for configuration files in
+/etc/
+and
+/run/, to make sure that local and transient configuration files will always take priority over configuration files shipped by the OS vendor\&.
 .PP
 If the administrator wants to disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -92,10 +101,7 @@ in the configuration directory in
 .\}
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-binfmt.service\fR(8),
-\fBsystemd-delta\fR(1),
-\fBwine\fR(8)
+\fBsystemd\fR(1), \fBsystemd-binfmt.service\fR(8), \fBsystemd-delta\fR(1), \fBwine\fR(8)
 .SH "NOTES"
 .IP " 1." 4
 Kernel Support for miscellaneous Binary Formats (binfmt_misc)
diff --git a/upstream/fedora-rawhide/man5/btrfs.5 b/upstream/fedora-rawhide/man5/btrfs.5
index 208aa24b..68c29796 100644
--- a/upstream/fedora-rawhide/man5/btrfs.5
+++ b/upstream/fedora-rawhide/man5/btrfs.5
@@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
 ..
-.TH "BTRFS" "5" "Feb 14, 2024" "6.7.1" "BTRFS"
+.TH "BTRFS" "5" "Mar 26, 2024" "6.8.1" "BTRFS"
 .SH NAME
 btrfs \- topics about the BTRFS filesystem (mount options, supported file attributes and other)
 .SH DESCRIPTION
@@ -70,7 +70,7 @@ storage model, hardware considerations
 .SS BTRFS SPECIFIC MOUNT OPTIONS
 .sp
 This section describes mount options specific to BTRFS.  For the generic mount
-options please refer to \fBmount(8)\fP manual page. The options are sorted alphabetically
+options please refer to \fI\%mount(8)\fP manual page. The options are sorted alphabetically
 (discarding the \fIno\fP prefix).
 .sp
 \fBNOTE:\fP
@@ -95,7 +95,7 @@ have been applied.
 (default: on)
 .sp
 Enable/disable support for POSIX Access Control Lists (ACLs).  See the
-\fBacl(5)\fP manual page for more information about ACLs.
+\fI\%acl(5)\fP manual page for more information about ACLs.
 .sp
 The support for ACL is build\-time configurable (BTRFS_FS_POSIX_ACL) and
 mount fails if \fIacl\fP is requested but the feature is not compiled in.
@@ -228,7 +228,7 @@ If compression is enabled, \fInodatacow\fP and \fInodatasum\fP are disabled.
 .sp
 Enable data copy\-on\-write for newly created files.
 \fINodatacow\fP implies \fInodatasum\fP, and disables \fIcompression\fP\&. All files created
-under \fInodatacow\fP are also set the NOCOW file attribute (see \fBchattr(1)\fP).
+under \fInodatacow\fP are also set the NOCOW file attribute (see \fI\%chattr(1)\fP).
 .sp
 \fBNOTE:\fP
 .INDENT 7.0
@@ -247,7 +247,7 @@ at the cost of potential partial writes, in case the write is interrupted
 Enable data checksumming for newly created files.
 \fIDatasum\fP implies \fIdatacow\fP, i.e. the normal mode of operation. All files created
 under \fInodatasum\fP inherit the \(dqno checksums\(dq property, however there\(aqs no
-corresponding file attribute (see \fBchattr(1)\fP).
+corresponding file attribute (see \fI\%chattr(1)\fP).
 .sp
 \fBNOTE:\fP
 .INDENT 7.0
@@ -599,7 +599,7 @@ Historically, any user could create a snapshot even if he was not owner
 of the source subvolume, the subvolume deletion has been restricted for that
 reason. The subvolume creation has been restricted but this mount option is
 still required. This is a usability issue.
-Since 4.18, the \fBrmdir(2)\fP syscall can delete an empty subvolume just like an
+Since 4.18, the \fI\%rmdir(2)\fP syscall can delete an empty subvolume just like an
 ordinary directory. Whether this is possible can be detected at runtime, see
 \fIrmdir_subvol\fP feature in \fIFILESYSTEM FEATURES\fP\&.
 .UNINDENT
@@ -635,7 +635,7 @@ previous use of the \fIinode_cache\fP option can be removed by
 .UNINDENT
 .SS NOTES ON GENERIC MOUNT OPTIONS
 .sp
-Some of the general mount options from \fBmount(8)\fP that affect BTRFS and are
+Some of the general mount options from \fI\%mount(8)\fP that affect BTRFS and are
 worth mentioning.
 .INDENT 0.0
 .TP
@@ -763,6 +763,11 @@ stored as an extent, saves a few percent of metadata if sparse files are used
 .sp
 extended RAID1 mode with copies on 3 or 4 devices respectively
 .TP
+.B raid_stripe_tree
+(since: 6.7)
+.sp
+a separate tree for tracking file extents on RAID profiles
+.TP
 .B RAID56
 (since: 3.9)
 .sp
@@ -771,7 +776,7 @@ the filesystem contains or contained a RAID56 profile of block groups
 .B rmdir_subvol
 (since: 4.18)
 .sp
-indicate that \fBrmdir(2)\fP syscall can delete an empty subvolume just like an
+indicate that \fI\%rmdir(2)\fP syscall can delete an empty subvolume just like an
 ordinary directory. Note that this feature only depends on the kernel version.
 .TP
 .B skinny_metadata
@@ -784,6 +789,11 @@ reduced\-size metadata for extent references, saves a few percent of metadata
 .sp
 number of the highest supported send stream version
 .TP
+.B simple_quota
+(since: 6.7)
+.sp
+simplified quota accounting
+.TP
 .B supported_checksums
 (since: 5.5)
 .sp
@@ -813,8 +823,8 @@ sequentially, see section \fI\%ZONED MODE\fP
 .SH SWAPFILE SUPPORT
 .sp
 A swapfile, when active, is a file\-backed swap area.  It is supported since kernel 5.0.
-Use \fBswapon(8)\fP to activate it, until then (respectively again after deactivating it
-with \fBswapoff(8)\fP) it\(aqs just a normal file (with NODATACOW set), for which the special
+Use \fI\%swapon(8)\fP to activate it, until then (respectively again after deactivating it
+with \fI\%swapoff(8)\fP) it\(aqs just a normal file (with NODATACOW set), for which the special
 restrictions for active swapfiles don\(aqt apply.
 .sp
 There are some limitations of the implementation in BTRFS and Linux swap
@@ -1447,9 +1457,9 @@ pattern detection, byte frequency, Shannon entropy.
 .SH COMPATIBILITY
 .sp
 Compression is done using the COW mechanism so it\(aqs incompatible with
-\fInodatacow\fP\&. Direct IO works on compressed files but will fall back to buffered
-writes and leads to recompression. Currently \fInodatasum\fP and compression don\(aqt
-work together.
+\fInodatacow\fP\&. Direct IO read works on compressed files but will fall back to
+buffered writes and leads to no compression even if force compression is set.
+Currently \fInodatasum\fP and compression don\(aqt work together.
 .sp
 The compression algorithms have been added over time so the version
 compatibility should be also considered, together with other tools that may
@@ -1886,7 +1896,7 @@ depends on the \fInodesize\fP value, for 4KiB it\(aqs 3949 bytes, for larger nod
 it\(aqs 4095 due to the system limit PATH_MAX
 .sp
 The symlink target may not be a valid path, i.e. the path name components
-can exceed the limits (NAME_MAX), there\(aqs no content validation at \fBsymlink(3)\fP
+can exceed the limits (NAME_MAX), there\(aqs no content validation at \fI\%symlink(3)\fP
 creation.
 .TP
 .B maximum number of inodes
@@ -1944,7 +1954,7 @@ old and new interfaces, with confusing names. The following list should clarify
 that:
 .INDENT 0.0
 .IP \(bu 2
-\fIattributes\fP: \fBchattr(1)\fP or \fBlsattr(1)\fP utilities (the ioctls are
+\fIattributes\fP: \fI\%chattr(1)\fP or \fI\%lsattr(1)\fP utilities (the ioctls are
 FS_IOC_GETFLAGS and FS_IOC_SETFLAGS), due to the ioctl names the attributes
 are also called flags
 .IP \(bu 2
@@ -1952,7 +1962,7 @@ are also called flags
 bits similar to the attributes but extensible and new bits will be added in
 the future (the ioctls are FS_IOC_FSGETXATTR and FS_IOC_FSSETXATTR but they
 are not related to extended attributes that are also called xattrs), there\(aqs
-no standard tool to change the bits, there\(aqs support in \fBxfs_io(8)\fP as
+no standard tool to change the bits, there\(aqs support in \fI\%xfs_io(8)\fP as
 command \fBxfs_io \-c chattr\fP
 .UNINDENT
 .SS Attributes
@@ -1986,11 +1996,11 @@ empty files.
 .UNINDENT
 .TP
 .B d
-\fIno dump\fP, makes sense with 3rd party tools like \fBdump(8)\fP, on BTRFS the
+\fIno dump\fP, makes sense with 3rd party tools like \fI\%dump(8)\fP, on BTRFS the
 attribute can be set/unset but no other special handling is done
 .TP
 .B D
-\fIsynchronous directory updates\fP, for more details search \fBopen(2)\fP for \fIO_SYNC\fP
+\fIsynchronous directory updates\fP, for more details search \fI\%open(2)\fP for \fIO_SYNC\fP
 and \fIO_DSYNC\fP
 .TP
 .B i
@@ -1999,23 +2009,23 @@ long as this attribute is set (obviously the exception is unsetting the attribut
 .TP
 .B m
 \fIno compression\fP, permanently turn off compression on the given file. Any
-compression mount options will not affect this file. (\fBchattr\fP support added in
+compression mount options will not affect this file. (\fI\%chattr(1)\fP support added in
 1.46.2)
 .sp
 When set on a directory, all newly created files will inherit this attribute.
 This attribute cannot be set with \fIc\fP at the same time.
 .TP
 .B S
-\fIsynchronous updates\fP, for more details search \fBopen(2)\fP for \fIO_SYNC\fP and
+\fIsynchronous updates\fP, for more details search \fI\%open(2)\fP for \fIO_SYNC\fP and
 \fIO_DSYNC\fP
 .UNINDENT
 .sp
 No other attributes are supported.  For the complete list please refer to the
-\fBchattr(1)\fP manual page.
+\fI\%chattr(1)\fP manual page.
 .SS XFLAGS
 .sp
 There\(aqs an overlap of letters assigned to the bits with the attributes, this list
-refers to what \fBxfs_io(8)\fP provides:
+refers to what \fI\%xfs_io(8)\fP provides:
 .INDENT 0.0
 .TP
 .B i
@@ -2757,10 +2767,23 @@ have been demonstrated (\fIrowhammer\fP) achieving specific bits to be flipped.
 While these were targeted, this shows that a series of reads or writes can
 affect unrelated parts of memory.
 .sp
+Block group profiles with redundancy (like RAID1) will not protect against
+memory errors as the blocks are first stored in memory before they are written
+to the devices from the same source.
+.sp
+A filesystem mounted read\-only will not affect the underlying block device in
+almost 100% (with highly unlikely exceptions). The exception is a tree\-log that
+needs to be replayed during mount (and before the read\-only mount takes place),
+working memory is needed for that and that can be affected by bit flips.
+There\(aqs a theoretical case where bit flip changes the filesystem status from
+read\-only to read\-write.
+.sp
 Further reading:
 .INDENT 0.0
 .IP \(bu 2
 \fI\%https://en.wikipedia.org/wiki/Row_hammer\fP
+.IP \(bu 2
+memory overclocking, XMP, potential risks
 .UNINDENT
 .sp
 What to do:
@@ -2772,6 +2795,10 @@ is under heavy load that the default memtest cannot trigger
 memory errors may appear as filesystem going read\-only due to \(dqpre write\(dq
 check, that verify meta data before they get written but fail some basic
 consistency checks
+.IP \(bu 2
+newly built systems should be tested before being put to production use,
+ideally start a IO/CPU load that will be run on such system later; namely
+systems that will utilize overclocking or special performance features
 .UNINDENT
 .SS Direct memory access (DMA)
 .sp
@@ -2827,7 +2854,7 @@ to avoid unnecessary resets and performs optimizations to maximize the storage
 media lifetime. The known techniques are deduplication (blocks with same
 fingerprint/hash are mapped to same physical block), compression or internal
 remapping and garbage collection of used memory cells. Due to the additional
-processing there are measures to verity the data e.g. by ECC codes.
+processing there are measures to verify the data e.g. by ECC codes.
 .sp
 The observations of failing SSDs show that the whole electronic fails at once
 or affects a lot of data (e.g. stored on one chip). Recovering such data
@@ -2960,13 +2987,13 @@ and replacing the card could be required as well.
 filesystem when it tells you.\fP
 .SH SEE ALSO
 .sp
-\fBacl(5)\fP,
+\fI\%acl(5)\fP,
 \fI\%btrfs(8)\fP,
-\fBchattr(1)\fP,
-\fBfstrim(8)\fP,
-\fBioctl(2)\fP,
+\fI\%chattr(1)\fP,
+\fI\%fstrim(8)\fP,
+\fI\%ioctl(2)\fP,
 \fI\%mkfs.btrfs(8)\fP,
-\fBmount(8)\fP,
-\fBswapon(8)\fP
+\fI\%mount(8)\fP,
+\fI\%swapon(8)\fP
 .\" Generated by docutils manpage writer.
 .
diff --git a/upstream/fedora-rawhide/man5/capsule@.service.5 b/upstream/fedora-rawhide/man5/capsule@.service.5
new file mode 100644
index 00000000..b18401aa
--- /dev/null
+++ b/upstream/fedora-rawhide/man5/capsule@.service.5
@@ -0,0 +1,180 @@
+'\" t
+.TH "CAPSULE@\&.SERVICE" "5" "" "systemd 256~rc3" "capsule@.service"
+.\" -----------------------------------------------------------------
+.\" * Define some portability stuff
+.\" -----------------------------------------------------------------
+.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.\" http://bugs.debian.org/507673
+.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
+.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.ie \n(.g .ds Aq \(aq
+.el       .ds Aq '
+.\" -----------------------------------------------------------------
+.\" * set default formatting
+.\" -----------------------------------------------------------------
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.\" -----------------------------------------------------------------
+.\" * MAIN CONTENT STARTS HERE *
+.\" -----------------------------------------------------------------
+.SH "NAME"
+capsule@.service \- System unit for the capsule service manager
+.SH "SYNOPSIS"
+.PP
+capsule@\fINAME\fR\&.service
+.SH "DESCRIPTION"
+.PP
+Service managers for capsules run in
+capsule@\fINAME\fR\&.service
+system units, with the capsule name as the instance identifier\&. Capsules are way to run additional instances of the service manager, under dynamic user IDs, i\&.e\&. UIDs that are allocated when the capsule service manager is started, and released when it is stopped\&.
+.PP
+In many ways
+capsule@\&.service
+is similar to the per\-user
+user@\&.service
+service manager, but there are a few important distinctions:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+The capsule service manager utilizes
+\fIDynamicUser=\fR
+(see
+\fBsystemd.exec\fR(5)) to allocate a new UID dynamically on invocation\&. The user name is automatically generated from the capsule name, by prefixng
+"p_"\&. The UID is released when the service is terminated\&. The user service manager on the other hand operates under a statically allocated user ID that must be pre\-existing, before the user service manager is invoked\&.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+User service managers register themselves with
+\fBpam\fR(8), capsule service managers do not\&.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+User service managers typically read their configuration from a
+\fI$HOME\fR
+directory below
+/home/, capsule service managers from a
+\fI$HOME\fR
+directory below
+/var/lib/capsules/\&.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+User service managers are collectively contained in the
+user\&.slice
+unit, capsule service managers in
+capsule\&.slice\&. Also see
+\fBsystemd.special\fR(7)\&.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+User service managers start the user unit
+default\&.target
+initially\&. Capsule service managers invoke the user unit
+capsule@\&.target
+instead\&.
+.RE
+.PP
+The capsule service manager and the capsule\*(Aqs bus broker can be reached via the
+\fB\-\-capsule=\fR
+switch to
+\fBsystemctl\fR(1),
+\fBsystemd-run\fR(1)
+and
+\fBbusctl\fR(1)\&.
+.PP
+New capsules can be started via a simple
+\fBsystemctl start capsule@\fR\fB\fINAME\fR\fR\fB\&.service\fR
+command, and stopped via
+\fBsystemctl stop capsule@\fR\fB\fINAME\fR\fR\fB\&.service\fR\&. Starting a capsule will implicitly create a home directory
+/var/lib/capsules/\fINAME\fR/, if missing\&. A runtime directory is created as
+/run/capsules/\fINAME\fR/\&. To remove these resources use
+\fBsystemctl clean capsule@\fR\fB\fINAME\fR\fR\fB\&.service\fR, for example with the
+\fB\-\-what=all\fR
+switch\&.
+.PP
+The
+capsule@\&.service
+unit invokes a
+\fBsystemd \-\-user\fR
+service manager process\&. This means unit files are looked for according to the sames rules as for regular user service managers, for example in
+/var/lib/capsules/\fINAME\fR/\&.config/systemd/user/\&.
+.PP
+Capsule names may be chosen freely by the user, however, they must be suitable as UNIX filenames (i\&.e\&. 255 characters max, and contain no
+"/"), and when prefixed with
+"p\-"
+be suitable as a user name matching strict POSIX rules, see
+\m[blue]\fBUser/Group Name Syntax\fR\m[]\&\s-2\u[1]\d\s+2
+for details\&.
+.SH "EXAMPLES"
+.PP
+\fBExample\ \&1.\ \&Create a new capsule, invoke two programs in it (one interactively), terminate it, and clean everything up\fR
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+# systemctl start capsule@tatze\&.service
+# systemd\-run \-\-capsule=tatze \-\-unit=sleeptest\&.service sleep 999
+# systemctl \-\-capsule=tatze status sleeptest\&.service
+# systemd\-run \-t \-\-capsule=tatze bash
+# systemctl \-\-capsule=tatze stop sleeptest\&.service
+# systemctl stop capsule@tatze\&.service
+# systemctl clean \-\-all capsule@tatze\&.service
+.fi
+.if n \{\
+.RE
+.\}
+.SH "SEE ALSO"
+.PP
+\fBsystemd\fR(1),
+\fBuser@.service\fR(5),
+\fBsystemd.service\fR(5),
+\fBsystemd.slice\fR(5),
+\fBsystemd.exec\fR(5),
+\fBsystemd.special\fR(7),
+\fBsystemctl\fR(1),
+\fBsystemd-run\fR(1),
+\fBbusctl\fR(1),
+\fBpam\fR(8)
+.SH "NOTES"
+.IP " 1." 4
+User/Group Name Syntax
+.RS 4
+\%https://systemd.io/USER_NAMES
+.RE
diff --git a/upstream/fedora-rawhide/man5/charmap.5 b/upstream/fedora-rawhide/man5/charmap.5
index 1b66a63f..7dda95c4 100644
--- a/upstream/fedora-rawhide/man5/charmap.5
+++ b/upstream/fedora-rawhide/man5/charmap.5
@@ -2,7 +2,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-2.0-or-later
 .\"
-.TH charmap 5 2023-10-31 "Linux man-pages 6.06"
+.TH charmap 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 charmap \- character set description file
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/core.5 b/upstream/fedora-rawhide/man5/core.5
index 73408b44..ea250e20 100644
--- a/upstream/fedora-rawhide/man5/core.5
+++ b/upstream/fedora-rawhide/man5/core.5
@@ -2,7 +2,7 @@
 .\"
 .\" SPDX-License-Identifier: Linux-man-pages-copyleft
 .\"
-.TH core 5 2023-10-31 "Linux man-pages 6.06"
+.TH core 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 core \- core dump file
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/coredump.conf.5 b/upstream/fedora-rawhide/man5/coredump.conf.5
index 10f56339..ba037f56 100644
--- a/upstream/fedora-rawhide/man5/coredump.conf.5
+++ b/upstream/fedora-rawhide/man5/coredump.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "COREDUMP\&.CONF" "5" "" "systemd 255" "coredump.conf"
+.TH "COREDUMP\&.CONF" "5" "" "systemd 256~rc3" "coredump.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,13 +23,24 @@
 coredump.conf, coredump.conf.d \- Core dump storage configuration files
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/systemd/coredump\&.conf
-.PP
+.RE
+.RS 4
+/run/systemd/coredump\&.conf
+.RE
+.RS 4
+/usr/lib/systemd/coredump\&.conf
+.RE
+.RS 4
 /etc/systemd/coredump\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /run/systemd/coredump\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /usr/lib/systemd/coredump\&.conf\&.d/*\&.conf
+.RE
 .SH "DESCRIPTION"
 .PP
 These files configure the behavior of
@@ -45,16 +56,16 @@ and
 pages for the details\&.
 .SH "CONFIGURATION DIRECTORIES AND PRECEDENCE"
 .PP
-The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is either in
-/usr/lib/systemd/
-or
-/etc/systemd/
-and contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
+The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is loaded from one of the listed directories in order of priority, only the first file found is used:
+/etc/systemd/,
+/run/systemd/,
+/usr/local/lib/systemd/,
+/usr/lib/systemd/\&. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can also be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
 /etc/
-if it\*(Aqs shipped in
-/usr/) however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
+if it\*(Aqs shipped under
+/usr/), however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
 .PP
-In addition to the "main" configuration file, drop\-in configuration snippets are read from
+In addition to the main configuration file, drop\-in configuration snippets are read from
 /usr/lib/systemd/*\&.conf\&.d/,
 /usr/local/lib/systemd/*\&.conf\&.d/, and
 /etc/systemd/*\&.conf\&.d/\&. Those drop\-ins have higher precedence and override the main configuration file\&. Files in the
@@ -64,7 +75,12 @@ configuration subdirectories are sorted by their filename in lexicographic order
 When packages need to customize the configuration, they can install drop\-ins under
 /usr/\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defined a concept of drop\-in priority to allow distributions to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defines a concept of drop\-in priorities to allow OS vendors to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&. It is recommended to use the range 10\-40 for drop\-ins in
+/usr/
+and the range 60\-90 for drop\-ins in
+/etc/
+and
+/run/, to make sure that local and transient drop\-ins take priority over drop\-ins shipped by the OS vendor\&.
 .PP
 To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -152,6 +168,4 @@ The defaults for all values are listed as comments in the template
 file that is installed by default\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd-journald.service\fR(8),
-\fBcoredumpctl\fR(1),
-\fBsystemd-tmpfiles\fR(8)
+\fBsystemd-journald.service\fR(8), \fBcoredumpctl\fR(1), \fBsystemd-tmpfiles\fR(8)
diff --git a/upstream/fedora-rawhide/man5/crypttab.5 b/upstream/fedora-rawhide/man5/crypttab.5
index 1a621795..5ae5aaf9 100644
--- a/upstream/fedora-rawhide/man5/crypttab.5
+++ b/upstream/fedora-rawhide/man5/crypttab.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "CRYPTTAB" "5" "" "systemd 255" "crypttab"
+.TH "CRYPTTAB" "5" "" "systemd 256~rc3" "crypttab"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -170,8 +170,8 @@ file system socket in place of a key file in the third field\&. For details see
 .sp -1
 .IP "  4." 4.2
 .\}
-The key may be acquired via a PKCS#11 compatible hardware security token or smartcard\&. In this case an encrypted key is stored on disk/removable media, acquired via
-\fBAF_UNIX\fR, or stored in the LUKS2 JSON token metadata header\&. The encrypted key is then decrypted by the PKCS#11 token with an RSA key stored on it, and then used to unlock the encrypted volume\&. Use the
+The key may be acquired via a PKCS#11 compatible hardware security token or smartcard\&. In this case a saved key used in unlock process is stored on disk/removable media, acquired via
+\fBAF_UNIX\fR, or stored in the LUKS2 JSON token metadata header\&. For RSA, the saved key is an encrypted volume key\&. The encrypted volume key is then decrypted by the PKCS#11 token with an RSA private key stored on it, and used to unlock the encrypted volume\&. For elliptic\-curve (EC) cryptography, the saved key is the public key generated in enrollment process\&. The public key is then used to derive a shared secret with a private key stored in the PKCS#11 token\&. The derived shared secret is then used to unlock the volume\&. Use the
 \fBpkcs11\-uri=\fR
 option described below to use this mechanism\&.
 .RE
@@ -206,7 +206,7 @@ option described below to use this mechanism\&.
 .PP
 For the latter five mechanisms the source for the key material used for unlocking the volume is primarily configured in the third field of each
 /etc/crypttab
-line, but may also configured in
+line, but may also be configured in
 /etc/cryptsetup\-keys\&.d/
 and
 /run/cryptsetup\-keys\&.d/
@@ -305,6 +305,32 @@ for key files on external devices\&.
 Added in version 243\&.
 .RE
 .PP
+\fBlink\-volume\-key=\fR
+.RS 4
+Specifies the kernel keyring and key description (see
+\fBkeyrings\fR(7)) where LUKS2 volume key gets linked during device activation\&. The kernel keyring description and key description must be separated by
+"::"\&.
+.sp
+The kernel keyring part can be a string description or a predefined kernel keyring prefixed with
+"@"
+(e\&.g\&.: to use
+"@s"
+session or
+"@u"
+user keyring directly)\&. The type prefix text in the kernel keyring description is not required\&. The specified kernel keyring must already exist at the time of device activation\&.
+.sp
+The key part is a string description optionally prefixed by a
+"%key_type:"\&. If no type is specified, the
+"user"
+type key is linked by default\&. See
+\fBkeyctl\fR(1)
+for more information on key descriptions (KEY IDENTIFIERS section)\&.
+.sp
+Note that the linked volume key is not cleaned up automatically when the device is detached\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fBluks\fR
 .RS 4
 Force LUKS mode\&. When this mode is used, the following options are ignored since they are provided by the LUKS header on the device:
@@ -360,7 +386,9 @@ Added in version 186\&.
 This device will not be a hard dependency of
 cryptsetup\&.target\&. It\*(Aqll still be pulled in and started, but the system will not wait for the device to show up and be unlocked, and boot will not fail if this is unsuccessful\&. Note that other units that depend on the unlocked device may still fail\&. In particular, if the device is used for a mount point, the mount point itself also needs to have the
 \fBnofail\fR
-option, or the boot will fail if the device is not unlocked successfully\&.
+option, or the boot will fail if the device is not unlocked successfully\&. If a keyfile and/or a
+\fBheader\fR
+are specified, the dependencies on their respective directories will also not be fatal, so that umounting said directories will not cause the generated cryptset unit to be deactivated\&.
 .sp
 Added in version 186\&.
 .RE
@@ -467,11 +495,23 @@ Added in version 240\&.
 The encrypted block device will be used as a swap device, and will be formatted accordingly after setting up the encrypted block device, with
 \fBmkswap\fR(8)\&. This option implies
 \fBplain\fR\&.
+.if n \{\
 .sp
-WARNING: Using the
+.\}
+.RS 4
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+.ps +1
+\fBWarning\fR
+.ps -1
+.br
+Using the
 \fBswap\fR
 option will destroy the contents of the named partition during every boot, so make sure the underlying block device is specified correctly\&.
-.sp
+.sp .5v
+.RE
 Added in version 186\&.
 .RE
 .PP
@@ -569,11 +609,23 @@ or
 "btrfs"\&. If no argument is specified defaults to
 "ext4"\&. This option implies
 \fBplain\fR\&.
+.if n \{\
 .sp
-WARNING: Using the
+.\}
+.RS 4
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+.ps +1
+\fBWarning\fR
+.ps -1
+.br
+Using the
 \fBtmp\fR
 option will destroy the contents of the named partition during every boot, so make sure the underlying block device is specified correctly\&.
-.sp
+.sp .5v
+.RE
 Added in version 186\&.
 .RE
 .PP
@@ -616,17 +668,17 @@ Takes either the special value
 "auto"
 or an
 \m[blue]\fBRFC7512 PKCS#11 URI\fR\m[]\&\s-2\u[2]\d\s+2
-pointing to a private RSA key which is used to decrypt the encrypted key specified in the third column of the line\&. This is useful for unlocking encrypted volumes through PKCS#11 compatible security tokens or smartcards\&. See below for an example how to set up this mechanism for unlocking a LUKS2 volume with a YubiKey security token\&.
+pointing to a private key which is used to decrypt the encrypted key specified in the third column of the line\&. This is useful for unlocking encrypted volumes through PKCS#11 compatible security tokens or smartcards\&. See below for an example how to set up this mechanism for unlocking a LUKS2 volume with a YubiKey security token\&.
 .sp
 If specified as
 "auto"
 the volume must be of type LUKS2 and must carry PKCS#11 security token metadata in its LUKS2 JSON token section\&. In this mode the URI and the encrypted key are automatically read from the LUKS2 JSON token header\&. Use
 \fBsystemd-cryptenroll\fR(1)
-as simple tool for enrolling PKCS#11 security tokens or smartcards in a way compatible with
+as a simple tool for enrolling PKCS#11 security tokens or smartcards in a way compatible with
 "auto"\&. In this mode the third column of the line should remain empty (that is, specified as
 "\-")\&.
 .sp
-The specified URI can refer directly to a private RSA key stored on a token or alternatively just to a slot or token, in which case a search for a suitable private RSA key will be performed\&. In this case if multiple suitable objects are found the token is refused\&. The encrypted key configured in the third column of the line is passed as is (i\&.e\&. in binary form, unprocessed) to RSA decryption\&. The resulting decrypted key is then Base64 encoded before it is used to unlock the LUKS volume\&.
+The specified URI can refer directly to a private key stored on a token or alternatively just to a slot or token, in which case a search for a suitable private key will be performed\&. In this case if multiple suitable objects are found the token is refused\&. The keyfile configured in the third column of the line is used as is (i\&.e\&. in binary form, unprocessed)\&. The resulting decrypted key (for RSA) or derived shared secret (for ECC) is then Base64 encoded before it is used to unlock the LUKS volume\&.
 .sp
 Use
 \fBsystemd\-cryptenroll \-\-pkcs11\-token\-uri=list\fR
@@ -852,7 +904,7 @@ stream socket in the file system, the key is acquired by connecting to the socke
 \fBAF_UNIX\fR
 socket name in the abstract namespace, see
 \fBunix\fR(7)
-for details\&. The source socket name is chosen according the following format:
+for details\&. The source socket name is chosen according to the following format:
 .sp
 .if n \{\
 .RS 4
@@ -910,7 +962,7 @@ external   /dev/sda3       keyfile:LABEL=keydev keyfile\-timeout=10s,cipher=xcha
 .PP
 \fBExample\ \&2.\ \&Yubikey\-based PKCS#11 Volume Unlocking Example\fR
 .PP
-The PKCS#11 logic allows hooking up any compatible security token that is capable of storing RSA decryption keys for unlocking an encrypted volume\&. Here\*(Aqs an example how to set up a Yubikey security token for this purpose on a LUKS2 volume, using
+The PKCS#11 logic allows hooking up any compatible security token that is capable of storing RSA or EC cryptographic keys for unlocking an encrypted volume\&. Here\*(Aqs an example how to set up a Yubikey security token for this purpose on a LUKS2 volume, using
 \fBykmap\fR(1)
 from the yubikey\-manager project to initialize the token and
 \fBsystemd-cryptenroll\fR(1)
@@ -1088,14 +1140,7 @@ sudo update\-initramfs \-u
 .\}
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-cryptsetup@.service\fR(8),
-\fBsystemd-cryptsetup-generator\fR(8),
-\fBsystemd-cryptenroll\fR(1),
-\fBfstab\fR(5),
-\fBcryptsetup\fR(8),
-\fBmkswap\fR(8),
-\fBmke2fs\fR(8)
+\fBsystemd\fR(1), \fBsystemd-cryptsetup@.service\fR(8), \fBsystemd-cryptsetup-generator\fR(8), \fBsystemd-cryptenroll\fR(1), \fBfstab\fR(5), \fBcryptsetup\fR(8), \fBmkswap\fR(8), \fBmke2fs\fR(8)
 .SH "NOTES"
 .IP " 1." 4
 Veracrypt Personal Iterations Multiplier
diff --git a/upstream/fedora-rawhide/man5/dir_colors.5 b/upstream/fedora-rawhide/man5/dir_colors.5
index a492f644..7c49f314 100644
--- a/upstream/fedora-rawhide/man5/dir_colors.5
+++ b/upstream/fedora-rawhide/man5/dir_colors.5
@@ -3,7 +3,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-2.0-or-later
 .\"
-.TH dir_colors 5 2024-01-28 "Linux man-pages 6.06"
+.TH dir_colors 5 2024-01-28 "Linux man-pages 6.7"
 .SH NAME
 dir_colors \- configuration file for dircolors(1)
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/dnssec-trust-anchors.d.5 b/upstream/fedora-rawhide/man5/dnssec-trust-anchors.d.5
index 4671d2f5..4f4eadf8 100644
--- a/upstream/fedora-rawhide/man5/dnssec-trust-anchors.d.5
+++ b/upstream/fedora-rawhide/man5/dnssec-trust-anchors.d.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "DNSSEC\-TRUST\-ANCHORS\&.D" "5" "" "systemd 255" "dnssec-trust-anchors.d"
+.TH "DNSSEC\-TRUST\-ANCHORS\&.D" "5" "" "systemd 256~rc3" "dnssec-trust-anchors.d"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,17 +23,24 @@
 dnssec-trust-anchors.d, systemd.positive, systemd.negative \- DNSSEC trust anchor configuration files
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/dnssec\-trust\-anchors\&.d/*\&.positive
-.PP
+.RE
+.RS 4
 /run/dnssec\-trust\-anchors\&.d/*\&.positive
-.PP
+.RE
+.RS 4
 /usr/lib/dnssec\-trust\-anchors\&.d/*\&.positive
-.PP
+.RE
+.RS 4
 /etc/dnssec\-trust\-anchors\&.d/*\&.negative
-.PP
+.RE
+.RS 4
 /run/dnssec\-trust\-anchors\&.d/*\&.negative
-.PP
+.RE
+.RS 4
 /usr/lib/dnssec\-trust\-anchors\&.d/*\&.negative
+.RE
 .SH "DESCRIPTION"
 .PP
 The DNSSEC trust anchor configuration files define positive and negative trust anchors
@@ -185,10 +192,7 @@ setting in
 files\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-resolved.service\fR(8),
-\fBresolved.conf\fR(5),
-\fBsystemd.network\fR(5)
+\fBsystemd\fR(1), \fBsystemd-resolved.service\fR(8), \fBresolved.conf\fR(5), \fBsystemd.network\fR(5)
 .SH "NOTES"
 .IP " 1." 4
 RFC 4035, Section 4.4
diff --git a/upstream/fedora-rawhide/man5/elf.5 b/upstream/fedora-rawhide/man5/elf.5
index 730d58cd..84c7f27c 100644
--- a/upstream/fedora-rawhide/man5/elf.5
+++ b/upstream/fedora-rawhide/man5/elf.5
@@ -32,7 +32,7 @@
 .\" 2007-10-11, Mike Frysinger <vapier@gentoo.org>, various fixes
 .\" 2007-12-08, mtk, Converted from mdoc to man macros
 .\"
-.TH ELF 5 2023-10-31 "Linux man-pages 6.06"
+.TH ELF 5 2024-02-25 "Linux man-pages 6.7"
 .SH NAME
 elf \- format of Executable and Linking Format (ELF) files
 .SH SYNOPSIS
@@ -785,7 +785,7 @@ A readable segment.
 A text segment commonly has the flags
 .B PF_X
 and
-.B PF_R .
+.BR PF_R .
 A data segment commonly has
 .B PF_W
 and
diff --git a/upstream/fedora-rawhide/man5/environment.d.5 b/upstream/fedora-rawhide/man5/environment.d.5
index 063bfb25..c54bd5c6 100644
--- a/upstream/fedora-rawhide/man5/environment.d.5
+++ b/upstream/fedora-rawhide/man5/environment.d.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "ENVIRONMENT\&.D" "5" "" "systemd 255" "environment.d"
+.TH "ENVIRONMENT\&.D" "5" "" "systemd 256~rc3" "environment.d"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,15 +23,21 @@
 environment.d \- Definition of user service environment
 .SH "SYNOPSIS"
 .PP
+.RS 4
 ~/\&.config/environment\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /etc/environment\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /run/environment\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /usr/lib/environment\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /etc/environment
+.RE
 .SH "DESCRIPTION"
 .PP
 Configuration files in the
@@ -71,7 +77,12 @@ Packages should install their configuration files in
 /usr/local/lib/
 (local installs)\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. It is recommended to prefix all filenames with a two\-digit number and a dash, to simplify the ordering of the files\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. It is recommended to prefix all filenames with a two\-digit number and a dash, to simplify the ordering of the files\&. It is recommended to use the range 10\-40 for configuration files in
+/usr/
+and the range 60\-90 for configuration files in
+/etc/
+and
+/run/, to make sure that local and transient configuration files will always take priority over configuration files shipped by the OS vendor\&.
 .PP
 If the administrator wants to disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -146,6 +157,4 @@ service builds an environment that is a combination of variables forwarded from
 or the underlying D\-Bus call\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-environment-d-generator\fR(8),
-\fBsystemd.environment-generator\fR(7)
+\fBsystemd\fR(1), \fBsystemd-environment-d-generator\fR(8), \fBsystemd.environment-generator\fR(7)
diff --git a/upstream/fedora-rawhide/man5/erofs.5 b/upstream/fedora-rawhide/man5/erofs.5
index 12de0ec7..f0756c71 100644
--- a/upstream/fedora-rawhide/man5/erofs.5
+++ b/upstream/fedora-rawhide/man5/erofs.5
@@ -2,7 +2,7 @@
 .\"
 .\" SPDX-License-Identifier: Linux-man-pages-copyleft
 .\"
-.TH erofs 5 2023-10-31 "Linux man-pages 6.06"
+.TH erofs 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 erofs \- the Enhanced Read-Only File System
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/exports.5 b/upstream/fedora-rawhide/man5/exports.5
index 58537a22..c14769e5 100644
--- a/upstream/fedora-rawhide/man5/exports.5
+++ b/upstream/fedora-rawhide/man5/exports.5
@@ -445,6 +445,9 @@ the given list an alternative location for the filesystem.
 filesystem is not required; so, for example,
 .IR "mount --bind" " /path /path"
 is sufficient.)
+
+This option affects only NFSv4 clients. Other clients will ignore
+all "refer=" parts.
 .TP
 .IR replicas= path@host[+host][:path@host[+host]]
 If the client asks for alternative locations for the export point, it
diff --git a/upstream/fedora-rawhide/man5/filesystems.5 b/upstream/fedora-rawhide/man5/filesystems.5
index 5196cec5..14b4906d 100644
--- a/upstream/fedora-rawhide/man5/filesystems.5
+++ b/upstream/fedora-rawhide/man5/filesystems.5
@@ -4,7 +4,7 @@
 .\"
 .\" 2007-12-14 mtk Added Reiserfs, XFS, JFS.
 .\"
-.TH filesystems 5 2024-01-28 "Linux man-pages 6.06"
+.TH filesystems 5 2024-01-28 "Linux man-pages 6.7"
 .nh
 .SH NAME
 filesystems \- Linux filesystem types: ext, ext2, ext3, ext4, hpfs, iso9660,
diff --git a/upstream/fedora-rawhide/man5/ftpusers.5 b/upstream/fedora-rawhide/man5/ftpusers.5
index 9595622e..21b27061 100644
--- a/upstream/fedora-rawhide/man5/ftpusers.5
+++ b/upstream/fedora-rawhide/man5/ftpusers.5
@@ -2,7 +2,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-2.0-or-later
 .\"
-.TH ftpusers 5 2023-10-31 "Linux man-pages 6.06"
+.TH ftpusers 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 ftpusers \- list of users that may not log in via the FTP daemon
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/gai.conf.5 b/upstream/fedora-rawhide/man5/gai.conf.5
index 7fed47e4..0b2c2e3b 100644
--- a/upstream/fedora-rawhide/man5/gai.conf.5
+++ b/upstream/fedora-rawhide/man5/gai.conf.5
@@ -3,7 +3,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-2.0-only
 .\"
-.TH gai.conf 5 2023-10-31 "Linux man-pages 6.06"
+.TH gai.conf 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 gai.conf \- getaddrinfo(3) configuration file
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/group.5 b/upstream/fedora-rawhide/man5/group.5
index 41212819..233f3072 100644
--- a/upstream/fedora-rawhide/man5/group.5
+++ b/upstream/fedora-rawhide/man5/group.5
@@ -4,7 +4,7 @@
 .\" SPDX-License-Identifier: GPL-2.0-or-later
 .\"
 .\" Modified Sat Jul 24 17:06:03 1993 by Rik Faith (faith@cs.unc.edu)
-.TH group 5 2023-10-31 "Linux man-pages 6.06"
+.TH group 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 group \- user group file
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/homed.conf.5 b/upstream/fedora-rawhide/man5/homed.conf.5
index af99d452..caf235e2 100644
--- a/upstream/fedora-rawhide/man5/homed.conf.5
+++ b/upstream/fedora-rawhide/man5/homed.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "HOMED\&.CONF" "5" "" "systemd 255" "homed.conf"
+.TH "HOMED\&.CONF" "5" "" "systemd 256~rc3" "homed.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,29 +23,40 @@
 homed.conf, homed.conf.d \- Home area/user account manager configuration files
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/systemd/homed\&.conf
-.PP
+.RE
+.RS 4
+/run/systemd/homed\&.conf
+.RE
+.RS 4
+/usr/lib/systemd/homed\&.conf
+.RE
+.RS 4
 /etc/systemd/homed\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /run/systemd/homed\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /usr/lib/systemd/homed\&.conf\&.d/*\&.conf
+.RE
 .SH "DESCRIPTION"
 .PP
 These configuration files control default parameters for home areas/user accounts created and managed by
 \fBsystemd-homed.service\fR(8)\&.
 .SH "CONFIGURATION DIRECTORIES AND PRECEDENCE"
 .PP
-The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is either in
-/usr/lib/systemd/
-or
-/etc/systemd/
-and contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
+The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is loaded from one of the listed directories in order of priority, only the first file found is used:
+/etc/systemd/,
+/run/systemd/,
+/usr/local/lib/systemd/,
+/usr/lib/systemd/\&. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can also be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
 /etc/
-if it\*(Aqs shipped in
-/usr/) however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
+if it\*(Aqs shipped under
+/usr/), however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
 .PP
-In addition to the "main" configuration file, drop\-in configuration snippets are read from
+In addition to the main configuration file, drop\-in configuration snippets are read from
 /usr/lib/systemd/*\&.conf\&.d/,
 /usr/local/lib/systemd/*\&.conf\&.d/, and
 /etc/systemd/*\&.conf\&.d/\&. Those drop\-ins have higher precedence and override the main configuration file\&. Files in the
@@ -55,7 +66,12 @@ configuration subdirectories are sorted by their filename in lexicographic order
 When packages need to customize the configuration, they can install drop\-ins under
 /usr/\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defined a concept of drop\-in priority to allow distributions to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defines a concept of drop\-in priorities to allow OS vendors to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&. It is recommended to use the range 10\-40 for drop\-ins in
+/usr/
+and the range 60\-90 for drop\-ins in
+/etc/
+and
+/run/, to make sure that local and transient drop\-ins take priority over drop\-ins shipped by the OS vendor\&.
 .PP
 To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -106,5 +122,4 @@ Added in version 246\&.
 .RE
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-homed.service\fR(8)
+\fBsystemd\fR(1), \fBsystemd-homed.service\fR(8)
diff --git a/upstream/fedora-rawhide/man5/host.conf.5 b/upstream/fedora-rawhide/man5/host.conf.5
index 867c206f..73f29693 100644
--- a/upstream/fedora-rawhide/man5/host.conf.5
+++ b/upstream/fedora-rawhide/man5/host.conf.5
@@ -4,7 +4,7 @@
 .\" SPDX-License-Identifier: GPL-2.0-or-later
 .\"
 .\" 2003-08-23 Martin Schulze <joey@infodrom.org> Updated according to glibc 2.3.2
-.TH host.conf 5 2023-10-31 "Linux man-pages 6.06"
+.TH host.conf 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 host.conf \- resolver configuration file
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/hostname.5 b/upstream/fedora-rawhide/man5/hostname.5
index ff5139a9..7226f5c4 100644
--- a/upstream/fedora-rawhide/man5/hostname.5
+++ b/upstream/fedora-rawhide/man5/hostname.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "HOSTNAME" "5" "" "systemd 255" "hostname"
+.TH "HOSTNAME" "5" "" "systemd 256~rc3" "hostname"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -113,15 +113,7 @@ The simple configuration file format of
 originates from Debian GNU/Linux\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsethostname\fR(2),
-\fBhostname\fR(1),
-\fBhostname\fR(7),
-\fBmachine-id\fR(5),
-\fBmachine-info\fR(5),
-\fBhostnamectl\fR(1),
-\fBsystemd-hostnamed.service\fR(8),
-\fBsystemd-firstboot\fR(1)
+\fBsystemd\fR(1), \fBsethostname\fR(2), \fBhostname\fR(1), \fBhostname\fR(7), \fBmachine-id\fR(5), \fBmachine-info\fR(5), \fBhostnamectl\fR(1), \fBsystemd-hostnamed.service\fR(8), \fBsystemd-firstboot\fR(1)
 .SH "NOTES"
 .IP " 1." 4
 NetworkManager
diff --git a/upstream/fedora-rawhide/man5/hosts.5 b/upstream/fedora-rawhide/man5/hosts.5
index e111ccb8..b01c3467 100644
--- a/upstream/fedora-rawhide/man5/hosts.5
+++ b/upstream/fedora-rawhide/man5/hosts.5
@@ -5,7 +5,7 @@
 .\" Minor polishing, aeb
 .\" Modified, 2002-06-16, Mike Coleman
 .\"
-.TH hosts 5 2023-10-31 "Linux man-pages 6.06"
+.TH hosts 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 hosts \- static table lookup for hostnames
 .SH SYNOPSIS
diff --git a/upstream/fedora-rawhide/man5/hosts.equiv.5 b/upstream/fedora-rawhide/man5/hosts.equiv.5
index 53d79104..b8ff0f68 100644
--- a/upstream/fedora-rawhide/man5/hosts.equiv.5
+++ b/upstream/fedora-rawhide/man5/hosts.equiv.5
@@ -1,7 +1,7 @@
 .\" Copyright (c) 1995 Peter Tobias <tobias@et-inf.fho-emden.de>
 .\"
 .\" SPDX-License-Identifier: GPL-1.0-or-later
-.TH hosts.equiv 5 2023-10-31 "Linux man-pages 6.06"
+.TH hosts.equiv 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 hosts.equiv \- list of hosts and users that are granted "trusted"
 .B r
diff --git a/upstream/fedora-rawhide/man5/icewm-env.5 b/upstream/fedora-rawhide/man5/icewm-env.5
index 783678dc..dfaf4002 100644
--- a/upstream/fedora-rawhide/man5/icewm-env.5
+++ b/upstream/fedora-rawhide/man5/icewm-env.5
@@ -55,7 +55,7 @@
 .\" ========================================================================
 .\"
 .IX Title "ICEWM-ENV 5"
-.TH ICEWM-ENV 5 2024-01-24 "icewm\ 3.4.5" "Standards, Environments and Macros"
+.TH ICEWM-ENV 5 2024-05-20 "icewm\ 3.5.0" "Standards, Environments and Macros"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
diff --git a/upstream/fedora-rawhide/man5/icewm-focus_mode.5 b/upstream/fedora-rawhide/man5/icewm-focus_mode.5
index e4e9d6d2..1a0e3859 100644
--- a/upstream/fedora-rawhide/man5/icewm-focus_mode.5
+++ b/upstream/fedora-rawhide/man5/icewm-focus_mode.5
@@ -55,7 +55,7 @@
 .\" ========================================================================
 .\"
 .IX Title "ICEWM-FOCUS_MODE 5"
-.TH ICEWM-FOCUS_MODE 5 2024-01-24 "icewm\ 3.4.5" "Standards, Environments and Macros"
+.TH ICEWM-FOCUS_MODE 5 2024-05-20 "icewm\ 3.5.0" "Standards, Environments and Macros"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
diff --git a/upstream/fedora-rawhide/man5/icewm-keys.5 b/upstream/fedora-rawhide/man5/icewm-keys.5
index 2e942c95..f50dbfb3 100644
--- a/upstream/fedora-rawhide/man5/icewm-keys.5
+++ b/upstream/fedora-rawhide/man5/icewm-keys.5
@@ -55,7 +55,7 @@
 .\" ========================================================================
 .\"
 .IX Title "ICEWM-KEYS 5"
-.TH ICEWM-KEYS 5 2024-01-24 "icewm\ 3.4.5" "Standards, Environments and Macros"
+.TH ICEWM-KEYS 5 2024-05-20 "icewm\ 3.5.0" "Standards, Environments and Macros"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
@@ -102,7 +102,10 @@ following four ways, which are identical:
 \&    key "Ctrl++"            xterm
 .Ve
 .PP
-To bind the mouse use \f(CW\*(C`Pointer_Button1\*(C'\fR for button 1, and so on.
+To bind the mouse, use \f(CW\*(C`Pointer_Button1\*(C'\fR for button 1, and so on.
+This only works when the mouse is over the root window.
+See below for examples.
+.PP
 The command \f(CW\*(C`icesh keys\*(C'\fR instructs icewm to reload this file.
 .SS FORMAT
 .IX Subsection "FORMAT"
diff --git a/upstream/fedora-rawhide/man5/icewm-menu.5 b/upstream/fedora-rawhide/man5/icewm-menu.5
index e316d331..5fc8b5d9 100644
--- a/upstream/fedora-rawhide/man5/icewm-menu.5
+++ b/upstream/fedora-rawhide/man5/icewm-menu.5
@@ -55,7 +55,7 @@
 .\" ========================================================================
 .\"
 .IX Title "ICEWM-MENU 5"
-.TH ICEWM-MENU 5 2024-01-24 "icewm\ 3.4.5" "Standards, Environments and Macros"
+.TH ICEWM-MENU 5 2024-05-20 "icewm\ 3.5.0" "Standards, Environments and Macros"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
diff --git a/upstream/fedora-rawhide/man5/icewm-preferences.5 b/upstream/fedora-rawhide/man5/icewm-preferences.5
index 37190201..d1dac365 100644
--- a/upstream/fedora-rawhide/man5/icewm-preferences.5
+++ b/upstream/fedora-rawhide/man5/icewm-preferences.5
@@ -55,7 +55,7 @@
 .\" ========================================================================
 .\"
 .IX Title "ICEWM-PREFERENCES 5"
-.TH ICEWM-PREFERENCES 5 2024-01-24 "icewm\ 3.4.5" "Standards, Environments and Macros"
+.TH ICEWM-PREFERENCES 5 2024-05-20 "icewm\ 3.5.0" "Standards, Environments and Macros"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
diff --git a/upstream/fedora-rawhide/man5/icewm-prefoverride.5 b/upstream/fedora-rawhide/man5/icewm-prefoverride.5
index 52b7e8bd..fed32f60 100644
--- a/upstream/fedora-rawhide/man5/icewm-prefoverride.5
+++ b/upstream/fedora-rawhide/man5/icewm-prefoverride.5
@@ -55,7 +55,7 @@
 .\" ========================================================================
 .\"
 .IX Title "ICEWM-PREFOVERRIDE 5"
-.TH ICEWM-PREFOVERRIDE 5 2024-01-24 "icewm\ 3.4.5" "Standards, Environments and Macros"
+.TH ICEWM-PREFOVERRIDE 5 2024-05-20 "icewm\ 3.5.0" "Standards, Environments and Macros"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
diff --git a/upstream/fedora-rawhide/man5/icewm-programs.5 b/upstream/fedora-rawhide/man5/icewm-programs.5
index cf55983b..f993a328 100644
--- a/upstream/fedora-rawhide/man5/icewm-programs.5
+++ b/upstream/fedora-rawhide/man5/icewm-programs.5
@@ -55,7 +55,7 @@
 .\" ========================================================================
 .\"
 .IX Title "ICEWM-PROGRAMS 5"
-.TH ICEWM-PROGRAMS 5 2024-01-24 "icewm\ 3.4.5" "Standards, Environments and Macros"
+.TH ICEWM-PROGRAMS 5 2024-05-20 "icewm\ 3.5.0" "Standards, Environments and Macros"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
diff --git a/upstream/fedora-rawhide/man5/icewm-shutdown.5 b/upstream/fedora-rawhide/man5/icewm-shutdown.5
index 56cd4fa8..d870f304 100644
--- a/upstream/fedora-rawhide/man5/icewm-shutdown.5
+++ b/upstream/fedora-rawhide/man5/icewm-shutdown.5
@@ -55,7 +55,7 @@
 .\" ========================================================================
 .\"
 .IX Title "ICEWM-SHUTDOWN 5"
-.TH ICEWM-SHUTDOWN 5 2024-01-24 "icewm\ 3.4.5" "Standards, Environments and Macros"
+.TH ICEWM-SHUTDOWN 5 2024-05-20 "icewm\ 3.5.0" "Standards, Environments and Macros"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
diff --git a/upstream/fedora-rawhide/man5/icewm-startup.5 b/upstream/fedora-rawhide/man5/icewm-startup.5
index 6962672c..87b70744 100644
--- a/upstream/fedora-rawhide/man5/icewm-startup.5
+++ b/upstream/fedora-rawhide/man5/icewm-startup.5
@@ -55,7 +55,7 @@
 .\" ========================================================================
 .\"
 .IX Title "ICEWM-STARTUP 5"
-.TH ICEWM-STARTUP 5 2024-01-24 "icewm\ 3.4.5" "Standards, Environments and Macros"
+.TH ICEWM-STARTUP 5 2024-05-20 "icewm\ 3.5.0" "Standards, Environments and Macros"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
diff --git a/upstream/fedora-rawhide/man5/icewm-theme.5 b/upstream/fedora-rawhide/man5/icewm-theme.5
index e09988c5..962d9706 100644
--- a/upstream/fedora-rawhide/man5/icewm-theme.5
+++ b/upstream/fedora-rawhide/man5/icewm-theme.5
@@ -55,7 +55,7 @@
 .\" ========================================================================
 .\"
 .IX Title "ICEWM-THEME 5"
-.TH ICEWM-THEME 5 2024-01-24 "icewm\ 3.4.5" "Standards, Environments and Macros"
+.TH ICEWM-THEME 5 2024-05-20 "icewm\ 3.5.0" "Standards, Environments and Macros"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
diff --git a/upstream/fedora-rawhide/man5/icewm-toolbar.5 b/upstream/fedora-rawhide/man5/icewm-toolbar.5
index f2af59ab..7777a060 100644
--- a/upstream/fedora-rawhide/man5/icewm-toolbar.5
+++ b/upstream/fedora-rawhide/man5/icewm-toolbar.5
@@ -55,7 +55,7 @@
 .\" ========================================================================
 .\"
 .IX Title "ICEWM-TOOLBAR 5"
-.TH ICEWM-TOOLBAR 5 2024-01-24 "icewm\ 3.4.5" "Standards, Environments and Macros"
+.TH ICEWM-TOOLBAR 5 2024-05-20 "icewm\ 3.5.0" "Standards, Environments and Macros"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
diff --git a/upstream/fedora-rawhide/man5/icewm-winoptions.5 b/upstream/fedora-rawhide/man5/icewm-winoptions.5
index b305b885..ec9f3077 100644
--- a/upstream/fedora-rawhide/man5/icewm-winoptions.5
+++ b/upstream/fedora-rawhide/man5/icewm-winoptions.5
@@ -55,7 +55,7 @@
 .\" ========================================================================
 .\"
 .IX Title "ICEWM-WINOPTIONS 5"
-.TH ICEWM-WINOPTIONS 5 2024-01-24 "icewm\ 3.4.5" "Standards, Environments and Macros"
+.TH ICEWM-WINOPTIONS 5 2024-05-20 "icewm\ 3.5.0" "Standards, Environments and Macros"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
diff --git a/upstream/fedora-rawhide/man5/integritytab.5 b/upstream/fedora-rawhide/man5/integritytab.5
index 1272444a..d29162af 100644
--- a/upstream/fedora-rawhide/man5/integritytab.5
+++ b/upstream/fedora-rawhide/man5/integritytab.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "INTEGRITYTAB" "5" "" "systemd 255" "integritytab"
+.TH "INTEGRITYTAB" "5" "" "systemd 256~rc3" "integritytab"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -81,7 +81,7 @@ Added in version 250\&.
 .PP
 \fBmode=(journal|bitmap|direct)\fR
 .RS 4
-Enable journaled, bitmapped or direct (passthrough) mode\&. Journaled mode is the default when this option is not specified\&. It provides safety against crashes, but can be slow because all data has to be written twice\&. Bitmap mode is more efficient since it requires only a single write, but it is less reliable because if data corruption happens when the machine crashes, it may not be detected\&. Direct mode disables the journal and the bitmap\&. Corresponds to the "direct writes" mode documented in
+Enable journaled, bitmapped or direct (passthrough) mode\&. Journaled mode is the default when this option is not specified\&. It provides safety against crashes, but can be slow because all data has to be written twice\&. Bitmap mode is more efficient since it requires only a single write, but it is less reliable because if data corruption happens when the machine crashes, it might not be detected\&. Direct mode disables the journal and the bitmap\&. Corresponds to the "direct writes" mode documented in
 \m[blue]\fBthe dm\-integrity documentation\fR\m[]\&\s-2\u[1]\d\s+2\&. Note that without a journal, if there is a crash, it is possible that the integrity tags and data will not match\&. If used, the journal\-* options below will have no effect if passed\&.
 .sp
 Added in version 254\&.
@@ -177,10 +177,7 @@ home PARTUUID=4973d0b8\-1b15\-c449\-96ec\-94bab7f6a7b8 /etc/hmac\&.key
 .\}
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-integritysetup@.service\fR(8),
-\fBsystemd-integritysetup-generator\fR(8),
-\fBintegritysetup\fR(8),
+\fBsystemd\fR(1), \fBsystemd-integritysetup@.service\fR(8), \fBsystemd-integritysetup-generator\fR(8), \fBintegritysetup\fR(8)
 .SH "NOTES"
 .IP " 1." 4
 the dm-integrity documentation
diff --git a/upstream/fedora-rawhide/man5/intro.5 b/upstream/fedora-rawhide/man5/intro.5
index ada73a01..10e885b4 100644
--- a/upstream/fedora-rawhide/man5/intro.5
+++ b/upstream/fedora-rawhide/man5/intro.5
@@ -5,7 +5,7 @@
 .\"
 .\" Modified Sat Jul 24 17:06:52 1993 by Rik Faith (faith@cs.unc.edu)
 .\" Modified Sun Jan 14 00:34:09 1996 by Andries Brouwer (aeb@cwi.nl)
-.TH intro 5 2023-10-31 "Linux man-pages 6.06"
+.TH intro 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 intro \- introduction to file formats and filesystems
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/iocost.conf.5 b/upstream/fedora-rawhide/man5/iocost.conf.5
index 112f047f..94dafcef 100644
--- a/upstream/fedora-rawhide/man5/iocost.conf.5
+++ b/upstream/fedora-rawhide/man5/iocost.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "IOCOST\&.CONF" "5" "" "systemd 255" "iocost.conf"
+.TH "IOCOST\&.CONF" "5" "" "systemd 256~rc3" "iocost.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -38,16 +38,16 @@ The qos and model values are calculated based on benchmarks collected on the
 project and turned into a set of solutions that go from most to least isolated\&. Isolation allows the system to remain responsive in face of high I/O load\&. Which solutions are available for a device can be queried from the udev metadata attached to it\&. By default the naive solution is used, which provides the most bandwidth\&.
 .SH "CONFIGURATION DIRECTORIES AND PRECEDENCE"
 .PP
-The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is either in
-/usr/lib/systemd/
-or
-/etc/systemd/
-and contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
+The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is loaded from one of the listed directories in order of priority, only the first file found is used:
+/etc/systemd/,
+/run/systemd/,
+/usr/local/lib/systemd/,
+/usr/lib/systemd/\&. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can also be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
 /etc/
-if it\*(Aqs shipped in
-/usr/) however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
+if it\*(Aqs shipped under
+/usr/), however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
 .PP
-In addition to the "main" configuration file, drop\-in configuration snippets are read from
+In addition to the main configuration file, drop\-in configuration snippets are read from
 /usr/lib/systemd/*\&.conf\&.d/,
 /usr/local/lib/systemd/*\&.conf\&.d/, and
 /etc/systemd/*\&.conf\&.d/\&. Those drop\-ins have higher precedence and override the main configuration file\&. Files in the
@@ -57,7 +57,12 @@ configuration subdirectories are sorted by their filename in lexicographic order
 When packages need to customize the configuration, they can install drop\-ins under
 /usr/\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defined a concept of drop\-in priority to allow distributions to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defines a concept of drop\-in priorities to allow OS vendors to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&. It is recommended to use the range 10\-40 for drop\-ins in
+/usr/
+and the range 60\-90 for drop\-ins in
+/etc/
+and
+/run/, to make sure that local and transient drop\-ins take priority over drop\-ins shipped by the OS vendor\&.
 .PP
 To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -80,9 +85,7 @@ Added in version 254\&.
 .RE
 .SH "SEE ALSO"
 .PP
-\fBudevadm\fR(8),
-\m[blue]\fBThe iocost\-benchmarks github project\fR\m[]\&\s-2\u[1]\d\s+2,
-\m[blue]\fBThe resctl\-bench documentation details how the values are obtained\fR\m[]\&\s-2\u[2]\d\s+2
+\fBudevadm\fR(8), \m[blue]\fBThe iocost\-benchmarks github project\fR\m[]\&\s-2\u[1]\d\s+2, \m[blue]\fBThe resctl\-bench documentation details how the values are obtained\fR\m[]\&\s-2\u[2]\d\s+2
 .SH "NOTES"
 .IP " 1." 4
 iocost-benchmark
diff --git a/upstream/fedora-rawhide/man5/issue.5 b/upstream/fedora-rawhide/man5/issue.5
index e1d6352c..c5e2501c 100644
--- a/upstream/fedora-rawhide/man5/issue.5
+++ b/upstream/fedora-rawhide/man5/issue.5
@@ -5,7 +5,7 @@
 .\"
 .\" Modified Sun Jul 25 11:06:22 1993 by Rik Faith <faith@cs.unc.edu>
 .\" Modified Mon Oct 21 17:47:19 EDT 1996 by Eric S. Raymond <esr@thyrsus.com>
-.TH issue 5 2022-10-30 "Linux man-pages 6.06"
+.TH issue 5 2022-10-30 "Linux man-pages 6.7"
 .SH NAME
 issue \- prelogin message and identification file
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/journal-remote.conf.5 b/upstream/fedora-rawhide/man5/journal-remote.conf.5
index a2619006..4bfe1487 100644
--- a/upstream/fedora-rawhide/man5/journal-remote.conf.5
+++ b/upstream/fedora-rawhide/man5/journal-remote.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "JOURNAL\-REMOTE\&.CONF" "5" "" "systemd 255" "journal-remote.conf"
+.TH "JOURNAL\-REMOTE\&.CONF" "5" "" "systemd 256~rc3" "journal-remote.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,13 +23,24 @@
 journal-remote.conf, journal-remote.conf.d \- Configuration files for the service accepting remote journal uploads
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/systemd/journal\-remote\&.conf
-.PP
+.RE
+.RS 4
+/run/systemd/journal\-remote\&.conf
+.RE
+.RS 4
+/usr/lib/systemd/journal\-remote\&.conf
+.RE
+.RS 4
 /etc/systemd/journal\-remote\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /run/systemd/journal\-remote\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /usr/lib/systemd/journal\-remote\&.conf\&.d/*\&.conf
+.RE
 .SH "DESCRIPTION"
 .PP
 These files configure various parameters of
@@ -38,16 +49,16 @@ These files configure various parameters of
 for a general description of the syntax\&.
 .SH "CONFIGURATION DIRECTORIES AND PRECEDENCE"
 .PP
-The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is either in
-/usr/lib/systemd/
-or
-/etc/systemd/
-and contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
+The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is loaded from one of the listed directories in order of priority, only the first file found is used:
+/etc/systemd/,
+/run/systemd/,
+/usr/local/lib/systemd/,
+/usr/lib/systemd/\&. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can also be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
 /etc/
-if it\*(Aqs shipped in
-/usr/) however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
+if it\*(Aqs shipped under
+/usr/), however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
 .PP
-In addition to the "main" configuration file, drop\-in configuration snippets are read from
+In addition to the main configuration file, drop\-in configuration snippets are read from
 /usr/lib/systemd/*\&.conf\&.d/,
 /usr/local/lib/systemd/*\&.conf\&.d/, and
 /etc/systemd/*\&.conf\&.d/\&. Those drop\-ins have higher precedence and override the main configuration file\&. Files in the
@@ -57,7 +68,12 @@ configuration subdirectories are sorted by their filename in lexicographic order
 When packages need to customize the configuration, they can install drop\-ins under
 /usr/\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defined a concept of drop\-in priority to allow distributions to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defines a concept of drop\-in priorities to allow OS vendors to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&. It is recommended to use the range 10\-40 for drop\-ins in
+/usr/
+and the range 60\-90 for drop\-ins in
+/etc/
+and
+/run/, to make sure that local and transient drop\-ins take priority over drop\-ins shipped by the OS vendor\&.
 .PP
 To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -134,7 +150,4 @@ Added in version 253\&.
 .RE
 .SH "SEE ALSO"
 .PP
-\fBjournald.conf\fR(5),
-\fBsystemd\fR(1),
-\fBsystemd-journal-remote.service\fR(8),
-\fBsystemd-journald.service\fR(8)
+\fBjournald.conf\fR(5), \fBsystemd\fR(1), \fBsystemd-journal-remote.service\fR(8), \fBsystemd-journald.service\fR(8)
diff --git a/upstream/fedora-rawhide/man5/journal-upload.conf.5 b/upstream/fedora-rawhide/man5/journal-upload.conf.5
index 73889f48..c2e0c90f 100644
--- a/upstream/fedora-rawhide/man5/journal-upload.conf.5
+++ b/upstream/fedora-rawhide/man5/journal-upload.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "JOURNAL\-UPLOAD\&.CONF" "5" "" "systemd 255" "journal-upload.conf"
+.TH "JOURNAL\-UPLOAD\&.CONF" "5" "" "systemd 256~rc3" "journal-upload.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -25,6 +25,10 @@ journal-upload.conf, journal-upload.conf.d \- Configuration files for the journa
 .PP
 /etc/systemd/journal\-upload\&.conf
 .PP
+/run/systemd/journal\-upload\&.conf
+.PP
+/usr/lib/systemd/journal\-upload\&.conf
+.PP
 /etc/systemd/journal\-upload\&.conf\&.d/*\&.conf
 .PP
 /run/systemd/journal\-upload\&.conf\&.d/*\&.conf
@@ -38,16 +42,16 @@ These files configure various parameters of
 for a general description of the syntax\&.
 .SH "CONFIGURATION DIRECTORIES AND PRECEDENCE"
 .PP
-The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is either in
-/usr/lib/systemd/
-or
-/etc/systemd/
-and contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
+The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is loaded from one of the listed directories in order of priority, only the first file found is used:
+/etc/systemd/,
+/run/systemd/,
+/usr/local/lib/systemd/,
+/usr/lib/systemd/\&. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can also be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
 /etc/
-if it\*(Aqs shipped in
-/usr/) however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
+if it\*(Aqs shipped under
+/usr/), however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
 .PP
-In addition to the "main" configuration file, drop\-in configuration snippets are read from
+In addition to the main configuration file, drop\-in configuration snippets are read from
 /usr/lib/systemd/*\&.conf\&.d/,
 /usr/local/lib/systemd/*\&.conf\&.d/, and
 /etc/systemd/*\&.conf\&.d/\&. Those drop\-ins have higher precedence and override the main configuration file\&. Files in the
@@ -57,7 +61,12 @@ configuration subdirectories are sorted by their filename in lexicographic order
 When packages need to customize the configuration, they can install drop\-ins under
 /usr/\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defined a concept of drop\-in priority to allow distributions to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defines a concept of drop\-in priorities to allow OS vendors to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&. It is recommended to use the range 10\-40 for drop\-ins in
+/usr/
+and the range 60\-90 for drop\-ins in
+/etc/
+and
+/run/, to make sure that local and transient drop\-ins take priority over drop\-ins shipped by the OS vendor\&.
 .PP
 To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -110,6 +119,4 @@ Added in version 249\&.
 .RE
 .SH "SEE ALSO"
 .PP
-\fBsystemd-journal-upload.service\fR(8),
-\fBsystemd\fR(1),
-\fBsystemd-journald.service\fR(8)
+\fBsystemd-journal-upload.service\fR(8), \fBsystemd\fR(1), \fBsystemd-journald.service\fR(8)
diff --git a/upstream/fedora-rawhide/man5/journald.conf.5 b/upstream/fedora-rawhide/man5/journald.conf.5
index 911b6cdf..212b7e97 100644
--- a/upstream/fedora-rawhide/man5/journald.conf.5
+++ b/upstream/fedora-rawhide/man5/journald.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "JOURNALD\&.CONF" "5" "" "systemd 255" "journald.conf"
+.TH "JOURNALD\&.CONF" "5" "" "systemd 256~rc3" "journald.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,21 +23,36 @@
 journald.conf, journald.conf.d, journald@.conf \- Journal service configuration files
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/systemd/journald\&.conf
-.PP
+.RE
+.RS 4
+/run/systemd/journald\&.conf
+.RE
+.RS 4
+/usr/lib/systemd/journald\&.conf
+.RE
+.RS 4
 /etc/systemd/journald\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /run/systemd/journald\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /usr/lib/systemd/journald\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /etc/systemd/journald@\fINAMESPACE\fR\&.conf
-.PP
+.RE
+.RS 4
 /etc/systemd/journald@\fINAMESPACE\fR\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /run/systemd/journald@\fINAMESPACE\fR\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /usr/lib/systemd/journald@\fINAMESPACE\fR\&.conf\&.d/*\&.conf
+.RE
 .SH "DESCRIPTION"
 .PP
 These files configure various parameters of the systemd journal service,
@@ -56,16 +71,16 @@ and associated drop\-ins with the namespace identifier filled in\&. This allows
 for details about journal namespaces\&.
 .SH "CONFIGURATION DIRECTORIES AND PRECEDENCE"
 .PP
-The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is either in
-/usr/lib/systemd/
-or
-/etc/systemd/
-and contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
+The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is loaded from one of the listed directories in order of priority, only the first file found is used:
+/etc/systemd/,
+/run/systemd/,
+/usr/local/lib/systemd/,
+/usr/lib/systemd/\&. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can also be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
 /etc/
-if it\*(Aqs shipped in
-/usr/) however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
+if it\*(Aqs shipped under
+/usr/), however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
 .PP
-In addition to the "main" configuration file, drop\-in configuration snippets are read from
+In addition to the main configuration file, drop\-in configuration snippets are read from
 /usr/lib/systemd/*\&.conf\&.d/,
 /usr/local/lib/systemd/*\&.conf\&.d/, and
 /etc/systemd/*\&.conf\&.d/\&. Those drop\-ins have higher precedence and override the main configuration file\&. Files in the
@@ -75,7 +90,12 @@ configuration subdirectories are sorted by their filename in lexicographic order
 When packages need to customize the configuration, they can install drop\-ins under
 /usr/\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defined a concept of drop\-in priority to allow distributions to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defines a concept of drop\-in priorities to allow OS vendors to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&. It is recommended to use the range 10\-40 for drop\-ins in
+/usr/
+and the range 60\-90 for drop\-ins in
+/etc/
+and
+/run/, to make sure that local and transient drop\-ins take priority over drop\-ins shipped by the OS vendor\&.
 .PP
 To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -151,6 +171,10 @@ Note that per\-user journal files are not supported unless persistent storage is
 \fBjournalctl \-\-user\fR
 unavailable\&.
 .sp
+The storage to use can also be specified via the
+"journal\&.storage"
+credential\&. Values configured via configuration files take priority over values configured via the credential\&.
+.sp
 Added in version 186\&.
 .RE
 .PP
@@ -364,9 +388,11 @@ The timeout before synchronizing journal files to disk\&. After syncing, journal
 Added in version 199\&.
 .RE
 .PP
-\fIForwardToSyslog=\fR, \fIForwardToKMsg=\fR, \fIForwardToConsole=\fR, \fIForwardToWall=\fR
+\fIForwardToSyslog=\fR, \fIForwardToKMsg=\fR, \fIForwardToConsole=\fR, \fIForwardToWall=\fR, \fIForwardToSocket=\fR
 .RS 4
-Control whether log messages received by the journal daemon shall be forwarded to a traditional syslog daemon, to the kernel log buffer (kmsg), to the system console, or sent as wall messages to all logged\-in users\&. These options take boolean arguments\&. If forwarding to syslog is enabled but nothing reads messages from the socket, forwarding to syslog has no effect\&. By default, only forwarding to wall is enabled\&. These settings may be overridden at boot time with the kernel command line options
+Control whether log messages received by the journal daemon shall be forwarded to a traditional syslog daemon, to the kernel log buffer (kmsg), to the system console, sent as wall messages to all logged\-in users or sent over a socket\&. These options take boolean arguments except for
+"ForwardToSocket="
+which takes an address instead\&. If forwarding to syslog is enabled but nothing reads messages from the socket, forwarding to syslog has no effect\&. By default, only forwarding to wall is enabled\&. These settings may be overridden at boot time with the kernel command line options
 "systemd\&.journald\&.forward_to_syslog",
 "systemd\&.journald\&.forward_to_kmsg",
 "systemd\&.journald\&.forward_to_console", and
@@ -374,6 +400,11 @@ Control whether log messages received by the journal daemon shall be forwarded t
 "="
 and the following argument, true is assumed\&. Otherwise, the argument is parsed as a boolean\&.
 .sp
+The socket forwarding address can be specified with the credential
+"journal\&.forward_to_socket"\&. The following socket types are supported:
+.sp
+\fBAF_INET\fR (e\&.g\&. "192\&.168\&.0\&.11:4444"), \fBAF_INET6\fR (e\&.g\&. "[2001:db8::ff00:42:8329]:4444"), \fBAF_UNIX\fR (e\&.g\&. "/run/host/journal/socket"), \fBAF_VSOCK\fR (e\&.g\&. "vsock:2:1234")
+.sp
 When forwarding to the console, the TTY to log to can be changed with
 \fITTYPath=\fR, described below\&.
 .sp
@@ -383,15 +414,30 @@ to the kernel command line\&.
 \fBsystemd\fR
 will automatically disable kernel\*(Aqs rate\-limiting applied to userspace processes (equivalent to setting
 "printk\&.devkmsg=on")\&.
-.PP
+.sp
+When forwarding over a socket the
+\m[blue]\fBJournal Export Format\fR\m[]\&\s-2\u[3]\d\s+2
+is used when sending over the wire\&. Notably this includes the metadata field
+\fI__REALTIME_TIMESTAMP\fR
+so that
+\fBsystemd\-journal\-remote\fR
+(see
+\fBsystemd-journal-remote.service\fR(8)) can be used to receive the forwarded journal entries\&.
+.sp
 Note: Forwarding is performed synchronously within journald, and may significantly affect its performance\&. This is particularly relevant when using ForwardToConsole=yes in cloud environments, where the console is often a slow, virtual serial port\&. Since journald is implemented as a conventional single\-process daemon, forwarding to a completely hung console will block journald\&. This can have a cascading effect resulting in any services synchronously logging to the blocked journal also becoming blocked\&. Unless actively debugging/developing something, it\*(Aqs generally preferable to setup a
 \fBjournalctl \-\-follow\fR
 style service redirected to the console, instead of ForwardToConsole=yes, for production use\&.
+.PP
+Note: Using
+\fIForwardToSocket=\fR
+over IPv4/IPv6 links can be very slow due to the synchronous nature of the sockets\&. Take care to ensure your link is a low\-latency local link if possible\&. Typically IP networking is not available everywhere journald runs, e\&.g\&. in the initrd during boot\&. Consider using
+\fBAF_VSOCK\fR/\fBAF_UNIX\fR
+sockets for this if possible\&.
 .RE
 .PP
-\fIMaxLevelStore=\fR, \fIMaxLevelSyslog=\fR, \fIMaxLevelKMsg=\fR, \fIMaxLevelConsole=\fR, \fIMaxLevelWall=\fR
+\fIMaxLevelStore=\fR, \fIMaxLevelSyslog=\fR, \fIMaxLevelKMsg=\fR, \fIMaxLevelConsole=\fR, \fIMaxLevelWall=\fR, \fIMaxLevelSocket=\fR
 .RS 4
-Controls the maximum log level of messages that are stored in the journal, forwarded to syslog, kmsg, the console or wall (if that is enabled, see above)\&. As argument, takes one of
+Controls the maximum log level of messages that are stored in the journal, forwarded to syslog, kmsg, the console, the wall, or a socket (if that is enabled, see above)\&. As argument, takes one of
 "emerg",
 "alert",
 "crit",
@@ -402,9 +448,10 @@ Controls the maximum log level of messages that are stored in the journal, forwa
 "debug", or integer values in the range of 0\(en7 (corresponding to the same levels)\&. Messages equal or below the log level specified are stored/forwarded, messages above are dropped\&. Defaults to
 "debug"
 for
-\fIMaxLevelStore=\fR
+\fIMaxLevelStore=\fR,
+\fIMaxLevelSyslog=\fR
 and
-\fIMaxLevelSyslog=\fR, to ensure that the all messages are stored in the journal and forwarded to syslog\&. Defaults to
+\fIMaxLevelSocket=\fR, to ensure that the all messages are stored in the journal, forwarded to syslog and the socket if one exists\&. Defaults to
 "notice"
 for
 \fIMaxLevelKMsg=\fR,
@@ -418,7 +465,8 @@ for
 "systemd\&.journald\&.max_level_syslog=",
 "systemd\&.journald\&.max_level_kmsg=",
 "systemd\&.journald\&.max_level_console=",
-"systemd\&.journald\&.max_level_wall="\&.
+"systemd\&.journald\&.max_level_wall=",
+"systemd\&.journald\&.max_level_socket="\&.
 .sp
 Added in version 185\&.
 .RE
@@ -491,11 +539,7 @@ option, and not the
 option, is relevant for them\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-journald.service\fR(8),
-\fBjournalctl\fR(1),
-\fBsystemd.journal-fields\fR(7),
-\fBsystemd-system.conf\fR(5)
+\fBsystemd\fR(1), \fBsystemd-journald.service\fR(8), \fBjournalctl\fR(1), \fBsystemd.journal-fields\fR(7), \fBsystemd-system.conf\fR(5)
 .SH "NOTES"
 .IP " 1." 4
 Seekable Sequential Key Generators
@@ -507,3 +551,8 @@ Users, Groups, UIDs and GIDs on systemd systems
 .RS 4
 \%https://systemd.io/UIDS-GIDS
 .RE
+.IP " 3." 4
+Journal Export Format
+.RS 4
+\%https://systemd.io/JOURNAL_EXPORT_FORMATS/#journal-export-format
+.RE
diff --git a/upstream/fedora-rawhide/man5/lmhosts.5 b/upstream/fedora-rawhide/man5/lmhosts.5
index ccd4d9c3..497964dc 100644
--- a/upstream/fedora-rawhide/man5/lmhosts.5
+++ b/upstream/fedora-rawhide/man5/lmhosts.5
@@ -2,12 +2,12 @@
 .\"     Title: lmhosts
 .\"    Author: [see the "AUTHOR" section]
 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
-.\"      Date: 02/26/2024
+.\"      Date: 05/08/2024
 .\"    Manual: File Formats and Conventions
-.\"    Source: Samba 4.20.0rc3
+.\"    Source: Samba 4.20.1
 .\"  Language: English
 .\"
-.TH "LMHOSTS" "5" "02/26/2024" "Samba 4\&.20\&.0rc3" "File Formats and Conventions"
+.TH "LMHOSTS" "5" "05/08/2024" "Samba 4\&.20\&.1" "File Formats and Conventions"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -112,7 +112,7 @@ or
 /usr/local/samba/lib\&.
 .SH "VERSION"
 .PP
-This man page is part of version 4\&.20\&.0rc3 of the Samba suite\&.
+This man page is part of version 4\&.20\&.1 of the Samba suite\&.
 .SH "SEE ALSO"
 .PP
 \fBsmbclient\fR(1),
diff --git a/upstream/fedora-rawhide/man5/locale.5 b/upstream/fedora-rawhide/man5/locale.5
index 4c6f9a64..3dade710 100644
--- a/upstream/fedora-rawhide/man5/locale.5
+++ b/upstream/fedora-rawhide/man5/locale.5
@@ -7,7 +7,7 @@
 .\" 2008-06-17 Petr Baudis <pasky@suse.cz>
 .\"     LC_TIME: Describe first_weekday and first_workday
 .\"
-.TH locale 5 2024-01-28 "Linux man-pages 6.06"
+.TH locale 5 2024-01-28 "Linux man-pages 6.7"
 .SH NAME
 locale \- describes a locale definition file
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/locale.conf.5 b/upstream/fedora-rawhide/man5/locale.conf.5
index 531a8d8f..c3c2148c 100644
--- a/upstream/fedora-rawhide/man5/locale.conf.5
+++ b/upstream/fedora-rawhide/man5/locale.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "LOCALE\&.CONF" "5" "" "systemd 255" "locale.conf"
+.TH "LOCALE\&.CONF" "5" "" "systemd 256~rc3" "locale.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -108,8 +108,4 @@ LC_MESSAGES=en_US\&.UTF\-8
 .\}
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBlocale\fR(7),
-\fBlocalectl\fR(1),
-\fBsystemd-localed.service\fR(8),
-\fBsystemd-firstboot\fR(1)
+\fBsystemd\fR(1), \fBlocale\fR(7), \fBlocalectl\fR(1), \fBsystemd-localed.service\fR(8), \fBsystemd-firstboot\fR(1)
diff --git a/upstream/fedora-rawhide/man5/localtime.5 b/upstream/fedora-rawhide/man5/localtime.5
index 091dfcc0..9b8a0ed3 100644
--- a/upstream/fedora-rawhide/man5/localtime.5
+++ b/upstream/fedora-rawhide/man5/localtime.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "LOCALTIME" "5" "" "systemd 255" "localtime"
+.TH "LOCALTIME" "5" "" "systemd 256~rc3" "localtime"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -59,9 +59,4 @@ to change the settings of this file from the command line during runtime\&. Use
 to initialize the time zone on mounted (but not booted) system images\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBtzset\fR(3),
-\fBlocaltime\fR(3),
-\fBtimedatectl\fR(1),
-\fBsystemd-timedated.service\fR(8),
-\fBsystemd-firstboot\fR(1)
+\fBsystemd\fR(1), \fBtzset\fR(3), \fBlocaltime\fR(3), \fBtimedatectl\fR(1), \fBsystemd-timedated.service\fR(8), \fBsystemd-firstboot\fR(1)
diff --git a/upstream/fedora-rawhide/man5/logind.conf.5 b/upstream/fedora-rawhide/man5/logind.conf.5
index 5089cb9c..0572aa17 100644
--- a/upstream/fedora-rawhide/man5/logind.conf.5
+++ b/upstream/fedora-rawhide/man5/logind.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "LOGIND\&.CONF" "5" "" "systemd 255" "logind.conf"
+.TH "LOGIND\&.CONF" "5" "" "systemd 256~rc3" "logind.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,13 +23,24 @@
 logind.conf, logind.conf.d \- Login manager configuration files
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/systemd/logind\&.conf
-.PP
+.RE
+.RS 4
+/run/systemd/logind\&.conf
+.RE
+.RS 4
+/usr/lib/systemd/logind\&.conf
+.RE
+.RS 4
 /etc/systemd/logind\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /run/systemd/logind\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /usr/lib/systemd/logind\&.conf\&.d/*\&.conf
+.RE
 .SH "DESCRIPTION"
 .PP
 These files configure various parameters of the systemd login manager,
@@ -38,16 +49,16 @@ These files configure various parameters of the systemd login manager,
 for a general description of the syntax\&.
 .SH "CONFIGURATION DIRECTORIES AND PRECEDENCE"
 .PP
-The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is either in
-/usr/lib/systemd/
-or
-/etc/systemd/
-and contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
+The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is loaded from one of the listed directories in order of priority, only the first file found is used:
+/etc/systemd/,
+/run/systemd/,
+/usr/local/lib/systemd/,
+/usr/lib/systemd/\&. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can also be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
 /etc/
-if it\*(Aqs shipped in
-/usr/) however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
+if it\*(Aqs shipped under
+/usr/), however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
 .PP
-In addition to the "main" configuration file, drop\-in configuration snippets are read from
+In addition to the main configuration file, drop\-in configuration snippets are read from
 /usr/lib/systemd/*\&.conf\&.d/,
 /usr/local/lib/systemd/*\&.conf\&.d/, and
 /etc/systemd/*\&.conf\&.d/\&. Those drop\-ins have higher precedence and override the main configuration file\&. Files in the
@@ -57,7 +68,12 @@ configuration subdirectories are sorted by their filename in lexicographic order
 When packages need to customize the configuration, they can install drop\-ins under
 /usr/\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defined a concept of drop\-in priority to allow distributions to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defines a concept of drop\-in priorities to allow OS vendors to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&. It is recommended to use the range 10\-40 for drop\-ins in
+/usr/
+and the range 60\-90 for drop\-ins in
+/etc/
+and
+/run/, to make sure that local and transient drop\-ins take priority over drop\-ins shipped by the OS vendor\&.
 .PP
 To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -158,7 +174,8 @@ Configures the action to take when the system is idle\&. Takes one of
 "suspend",
 "hibernate",
 "hybrid\-sleep",
-"suspend\-then\-hibernate", and
+"suspend\-then\-hibernate",
+"sleep", and
 "lock"\&. Defaults to
 "ignore"\&.
 .sp
@@ -196,6 +213,28 @@ the per\-user service for a user is never terminated again after first login, an
 Added in version 240\&.
 .RE
 .PP
+\fISleepOperation=\fR
+.RS 4
+Takes a list of sleep operations\&. Possible values are
+"suspend",
+"hibernate",
+"hybrid\-sleep", and
+"suspend\-then\-hibernate"\&. Controls the candidate sleep operations for the
+"sleep"
+action\&. When
+"sleep"
+action is performed, the specified sleep operations are checked in a fixed order ("suspend\-then\-hibernate"
+→
+"hybrid\-sleep"
+→
+"suspend"
+→
+"hibernate"), and the first one supported by the machine is used to put the system into sleep\&. Defaults to
+"suspend\-then\-hibernate suspend hibernate"\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fIHandlePowerKey=\fR, \fIHandlePowerKeyLongPress=\fR, \fIHandleRebootKey=\fR, \fIHandleRebootKeyLongPress=\fR, \fIHandleSuspendKey=\fR, \fIHandleSuspendKeyLongPress=\fR, \fIHandleHibernateKey=\fR, \fIHandleHibernateKeyLongPress=\fR, \fIHandleLidSwitch=\fR, \fIHandleLidSwitchExternalPower=\fR, \fIHandleLidSwitchDocked=\fR
 .RS 4
 Controls how logind shall handle the system power, reboot and sleep keys and the lid switch to trigger actions such as system power\-off, reboot or suspend\&. Can be one of
@@ -208,6 +247,7 @@ Controls how logind shall handle the system power, reboot and sleep keys and the
 "hibernate",
 "hybrid\-sleep",
 "suspend\-then\-hibernate",
+"sleep",
 "lock", and
 "factory\-reset"\&. If
 "ignore",
@@ -354,7 +394,11 @@ Added in version 212\&.
 .RS 4
 Specifies a timeout in seconds, or a time span value after which
 systemd\-logind
-checks the idle state of all sessions\&. Every session that is idle for longer then the timeout will be stopped\&. Defaults to
+checks the idle state of all sessions\&. Every session that is idle for longer than the timeout will be stopped\&. Note that this option doesn\*(Aqt apply to
+"greeter"
+or
+"lock\-screen"
+sessions\&. Defaults to
 "infinity"
 (systemd\-logind
 is not checking the idle state of sessions)\&. For details about the syntax of time spans, see
@@ -364,7 +408,4 @@ Added in version 252\&.
 .RE
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-logind.service\fR(8),
-\fBloginctl\fR(1),
-\fBsystemd-system.conf\fR(5)
+\fBsystemd\fR(1), \fBsystemd-logind.service\fR(8), \fBloginctl\fR(1), \fBsystemd-system.conf\fR(5)
diff --git a/upstream/fedora-rawhide/man5/machine-id.5 b/upstream/fedora-rawhide/man5/machine-id.5
index a85e524b..10d5cd55 100644
--- a/upstream/fedora-rawhide/man5/machine-id.5
+++ b/upstream/fedora-rawhide/man5/machine-id.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "MACHINE\-ID" "5" "" "systemd 255" "machine-id"
+.TH "MACHINE\-ID" "5" "" "systemd 256~rc3" "machine-id"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -89,7 +89,8 @@ will attempt to use the D\-Bus machine ID from
 product_uuid
 or the devicetree
 vm,uuid
-(on KVM systems), and finally a randomly generated UUID\&.
+(on KVM systems), the Xen hypervisor
+uuid, and finally a randomly generated UUID\&.
 .PP
 After the machine ID is established,
 \fBsystemd\fR(1)
@@ -231,15 +232,7 @@ file introduced by D\-Bus\&. In fact, this latter file might be a symlink to
 /etc/machine\-id\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-machine-id-setup\fR(1),
-\fBgethostid\fR(3),
-\fBhostname\fR(5),
-\fBmachine-info\fR(5),
-\fBos-release\fR(5),
-\fBsd-id128\fR(3),
-\fBsd_id128_get_machine\fR(3),
-\fBsystemd-firstboot\fR(1)
+\fBsystemd\fR(1), \fBsystemd-machine-id-setup\fR(1), \fBgethostid\fR(3), \fBhostname\fR(5), \fBmachine-info\fR(5), \fBos-release\fR(5), \fBsd-id128\fR(3), \fBsd_id128_get_machine\fR(3), \fBsystemd-firstboot\fR(1)
 .SH "NOTES"
 .IP " 1." 4
 Safely Building Images
diff --git a/upstream/fedora-rawhide/man5/machine-info.5 b/upstream/fedora-rawhide/man5/machine-info.5
index f77dc12b..105e38cc 100644
--- a/upstream/fedora-rawhide/man5/machine-info.5
+++ b/upstream/fedora-rawhide/man5/machine-info.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "MACHINE\-INFO" "5" "" "systemd 255" "machine-info"
+.TH "MACHINE\-INFO" "5" "" "systemd 256~rc3" "machine-info"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -143,12 +143,7 @@ DEPLOYMENT=production
 .\}
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBos-release\fR(5),
-\fBhostname\fR(5),
-\fBmachine-id\fR(5),
-\fBhostnamectl\fR(1),
-\fBsystemd-hostnamed.service\fR(8)
+\fBsystemd\fR(1), \fBos-release\fR(5), \fBhostname\fR(5), \fBmachine-id\fR(5), \fBhostnamectl\fR(1), \fBsystemd-hostnamed.service\fR(8)
 .SH "NOTES"
 .IP " 1." 4
 XDG Icon Naming Specification
diff --git a/upstream/fedora-rawhide/man5/makepkg.conf.5 b/upstream/fedora-rawhide/man5/makepkg.conf.5
index 7c5fe2de..aad557bb 100644
--- a/upstream/fedora-rawhide/man5/makepkg.conf.5
+++ b/upstream/fedora-rawhide/man5/makepkg.conf.5
@@ -2,12 +2,12 @@
 .\"     Title: makepkg.conf
 .\"    Author: [see the "Authors" section]
 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
-.\"      Date: 2024-01-25
+.\"      Date: 2024-04-14
 .\"    Manual: Pacman Manual
-.\"    Source: Pacman 6.0.2
+.\"    Source: Pacman 6.1.0
 .\"  Language: English
 .\"
-.TH "MAKEPKG\&.CONF" "5" "2024\-01\-25" "Pacman 6\&.0\&.2" "Pacman Manual"
+.TH "MAKEPKG\&.CONF" "5" "2024\-04\-14" "Pacman 6\&.1\&.0" "Pacman Manual"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -107,13 +107,6 @@ in place of
 Flags used for the C++ compiler; see CFLAGS for more info\&.
 .RE
 .PP
-\fBRUSTFLAGS=\fR"rustflags"
-.RS 4
-Flags used for the Rust compiler, similar in spirit to CFLAGS\&. Read
-\fBrustc\fR(1)
-for more details on the available flags\&.
-.RE
-.PP
 \fBLDFLAGS=\fR"ldflags"
 .RS 4
 Flags used for the linker\&. Several options may be specified with common usage resembling \(lq\-Wl,\-\-hash\-style=gnu\(rq\&. Read ld(1) for more details on available linker flags\&.
@@ -147,15 +140,6 @@ for use in debugging\&. Usually this would include: \(lq\-g\(rq\&. Read gcc(1) f
 Debug flags used for the C++ compiler; see DEBUG_CFLAGS for more info\&.
 .RE
 .PP
-\fBDEBUG_RUSTFLAGS=\fR"debug_rustflags"
-.RS 4
-Additional compiler flags appended to
-RUSTFLAGS
-for use in debugging\&. Usually this would include: \(lq\-C debuginfo=2\(rq\&. Read
-\fBrustc\fR(1)
-for more details on the available flags\&.
-.RE
-.PP
 \fBBUILDENV=(\fR!distcc !color !ccache check !sign\fB)\fR
 .RS 4
 This array contains options that affect the build environment; the defaults are shown here\&. All options should always be left in the array; to enable or disable an option, simply remove or add an \(lq!\(rq at the front of the option\&. If an option is specified multiple times, the final value takes precedence\&. Each option works as follows:
@@ -216,7 +200,7 @@ Specify a key to use for GPG signing instead of the default key in the keyring\&
 option\&.
 .RE
 .PP
-\fBOPTIONS=(\fR!strip docs libtool staticlibs emptydirs !zipman !purge !debug\fB)\fR
+\fBOPTIONS=(\fR!strip docs libtool staticlibs emptydirs \&...\fB)\fR
 .RS 4
 This array contains options that affect default packaging\&. They are equivalent to options that can be placed in the PKGBUILD; the defaults are shown here\&. All options should always be left in the array; to enable or disable an option, simply remove or add an \(lq!\(rq at the front of the option\&. If an option is specified multiple times, the final value takes precedence\&. Each option works as follows:
 .PP
@@ -276,6 +260,11 @@ Add the user\-specified debug flags as specified in DEBUG_CFLAGS and DEBUG_CXXFL
 .RS 4
 Enable building packages using link time optimization\&. Adds the flags specified in LTOFLAGS to CFLAGS, CXXFLAGS and LDFLAGS (or \(lq\-flto\(rq if LTOFLAGS is empty)\&.
 .RE
+.PP
+\fBautodeps\fR
+.RS 4
+Enable the automatic addition of libraries to the depends and provides arrays\&. Search library directories are controlled by the LIB_DIRS variable defined below\&.
+.RE
 .RE
 .PP
 \fBINTEGRITY_CHECK=(\fRcheck1 \&...\fB)\fR
@@ -334,6 +323,17 @@ array, this variable will instruct makepkg where to look to remove docs\&. If yo
 Do not add the leading slash to the directory name\&.
 .RE
 .PP
+\fBLIB_DIRS=(\fRlib:usr/lib \&...\fB)\fR
+.RS 4
+If
+autodeps
+is specified in the
+OPTIONS
+array, this variable will instruct makepkg where to look to find libraries to add to the
+provides
+array\&. The format is "prefix:path", where provides will be added for libraries found in "path" with the specified prefix added\&.
+.RE
+.PP
 \fBPURGE_TARGETS=(\fRusr/{,share}/info/dir \&.podlist *\&.pod\&...\fB)\fR
 .RS 4
 If
@@ -388,6 +388,10 @@ Sets the command and options used when compressing compiled or source packages i
 \fBPKGEXT=\fR"\&.pkg\&.tar\&.gz", \fBSRCEXT=\fR"\&.src\&.tar\&.gz"
 .RS 4
 Sets the compression used when making compiled or source packages\&. Valid suffixes are
+\&.pkg
+or
+\&.src
+(for PKGEXT and SRCEXT resepectively) followed by one of
 \&.tar\&.gz,
 \&.tar\&.bz2,
 \&.tar\&.xz,
@@ -452,17 +456,6 @@ Andrew Gregory <andrew\&.gregory\&.8@gmail\&.com>
 .sp -1
 .IP \(bu 2.3
 .\}
-Eli Schwartz <eschwartz@archlinux\&.org>
-.RE
-.sp
-.RS 4
-.ie n \{\
-\h'-04'\(bu\h'+03'\c
-.\}
-.el \{\
-.sp -1
-.IP \(bu 2.3
-.\}
 Morgan Adamiec <morganamilo@archlinux\&.org>
 .RE
 .sp
@@ -545,4 +538,15 @@ Nagy Gabor <ngaba@bibl\&.u\-szeged\&.hu>
 Dave Reisner <dreisner@archlinux\&.org>
 .RE
 .sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+Eli Schwartz <eschwartz@archlinux\&.org>
+.RE
+.sp
 For additional contributors, use git shortlog \-s on the pacman\&.git repository\&.
diff --git a/upstream/fedora-rawhide/man5/mlocate.db.5 b/upstream/fedora-rawhide/man5/mlocate.db.5
deleted file mode 100644
index 60814d6b..00000000
--- a/upstream/fedora-rawhide/man5/mlocate.db.5
+++ /dev/null
@@ -1,131 +0,0 @@
-.\" A man page for mlocate.db. -*- nroff -*-
-.\"
-.\" Copyright (C) 2005, 2007 Red Hat, Inc. All rights reserved.
-.\"
-.\" This copyrighted material is made available to anyone wishing to use,
-.\" modify, copy, or redistribute it subject to the terms and conditions of the
-.\" GNU General Public License v.2.
-.\"
-.\" This program is distributed in the hope that it will be useful, but WITHOUT
-.\" ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or 
-.\" FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for 
-.\" more details.
-.\"
-.\" You should have received a copy of the GNU General Public License along
-.\" with this program; if not, write to the Free Software Foundation, Inc.,
-.\" 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-.\"
-.\" Author: Miloslav Trmac <mitr@redhat.com>
-.TH mlocate.db 5 "Jan 2007" mlocate
-
-.SH NAME
-mlocate.db \- a mlocate database
-
-.SH DESCRIPTION
-A mlocate database starts with a file header:
-8 bytes for a magic number (\fB"\\0mlocate"\fR like a C literal),
-4 bytes for the
-.I configuration block
-size in big endian,
-1 byte for file format version (\fB0\fR),
-1 byte for the \*(lqrequire visibility\*(rq flag (\fB0\fR or \fB1\fR),
-2 bytes padding,
-and a \f(SMNUL\fR-terminated path name of the root of the database.
-
-The header is followed by a \fIconfiguration block\fR,
-included to ensure databases are not reused
-if some configuration changes
-could affect their contents.
-The size of the configuration block in bytes is stored in the file header.
-The configuration block is a sequence of \fIvariable assignments\fR,
-ordered by variable name.
-Each 
-.I variable assignment
-consists of a \f(SMNUL\fR-terminated variable name
-and an ordered list of \f(SMNUL\fR-terminated values.
-The value list is terminated by one more
-.SM NUL
-character.
-The ordering used is defined by the
-.B strcmp ()
-function.
-
-Currently defined variables are:
-.TP
-\fBprune_bind_mounts\fR
-A single entry, the value of \fbPRUNE_BIND_MOUNTS\fR; one of the strings
-.B 0
-or \fB1\fR.
-
-.TP
-\fBprunefs\fR
-The value of \fBPRUNEFS\fR, each entry is converted to uppercase.
-
-.TP
-\fBprunepaths\fR
-The value of \fBPRUNEPATHS\fR.
-
-.P
-The rest of the file until
-.SM EOF
-describes directories and their contents.
-Each directory starts with a header:
-8 bytes for
-.I directory time
-(seconds) in big endian,
-4 bytes for
-.I directory time
-(nanoseconds) in big endian (0 if unknown, less than 1,000,000,000),
-4 bytes padding,
-and a \f(SMNUL\fR-terminated path name of the the directory.
-Directory contents, a sequence of
-.I file entries
-sorted by name, follow.
-
-.I Directory time
-is the maximum of
-.B st_ctime
-and
-.B st_mtime
-of the directory.
-.BR updatedb (8)
-uses the original data if the 
-.I directory time
-in the database and in the file system match exactly.
-.I Directory time
-equal to 0 always causes rescanning of the directory:
-this is necessary to handle directories
-which were being updated while building the database.
-
-Each
-.I file entry
-starts with a single byte, marking its type:
-.TP
-\fB0\fR
-A non-directory file.
-Followed by a \f(SMNUL\fR-terminated file (not path) name.
-
-.TP
-\fB1\fR
-A subdirectory.
-Followed by a \f(SMNUL\fR-terminated file (not path) name.
-
-.TP
-\fB2\fR
-Marks the end of the current directory.
-
-.P
-.BR locate(1)
-only reports file entries,
-directory names are not reported
-because they are reported as an entry in their parent directory.
-The only exception is the root directory of the database,
-which is stored in the file header.
-
-.SH AUTHOR
-Miloslav Trmac <mitr@redhat.com>
-
-.SH SEE ALSO
-.BR locate (1),
-.BR updatedb.conf (5),
-.BR updatedb (8)
diff --git a/upstream/fedora-rawhide/man5/modules-load.d.5 b/upstream/fedora-rawhide/man5/modules-load.d.5
index 1570e788..1b0af433 100644
--- a/upstream/fedora-rawhide/man5/modules-load.d.5
+++ b/upstream/fedora-rawhide/man5/modules-load.d.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "MODULES\-LOAD\&.D" "5" "" "systemd 255" "modules-load.d"
+.TH "MODULES\-LOAD\&.D" "5" "" "systemd 256~rc3" "modules-load.d"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,11 +23,15 @@
 modules-load.d \- Configure kernel modules to load at boot
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/modules\-load\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /run/modules\-load\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /usr/lib/modules\-load\&.d/*\&.conf
+.RE
 .SH "DESCRIPTION"
 .PP
 \fBsystemd-modules-load.service\fR(8)
@@ -62,7 +66,12 @@ Packages should install their configuration files in
 /usr/local/lib/
 (local installs)\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. It is recommended to prefix all filenames with a two\-digit number and a dash, to simplify the ordering of the files\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. It is recommended to prefix all filenames with a two\-digit number and a dash, to simplify the ordering of the files\&. It is recommended to use the range 10\-40 for configuration files in
+/usr/
+and the range 60\-90 for configuration files in
+/etc/
+and
+/run/, to make sure that local and transient configuration files will always take priority over configuration files shipped by the OS vendor\&.
 .PP
 If the administrator wants to disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -84,7 +93,4 @@ virtio\-net
 .\}
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-modules-load.service\fR(8),
-\fBsystemd-delta\fR(1),
-\fBmodprobe\fR(8)
+\fBsystemd\fR(1), \fBsystemd-modules-load.service\fR(8), \fBsystemd-delta\fR(1), \fBmodprobe\fR(8)
diff --git a/upstream/fedora-rawhide/man5/motd.5 b/upstream/fedora-rawhide/man5/motd.5
index e530f542..26dc74e9 100644
--- a/upstream/fedora-rawhide/man5/motd.5
+++ b/upstream/fedora-rawhide/man5/motd.5
@@ -5,7 +5,7 @@
 .\"
 .\" Modified Sat Jul 24 17:08:16 1993 by Rik Faith <faith@cs.unc.edu>
 .\" Modified Mon Oct 21 17:47:19 EDT 1996 by Eric S. Raymond <esr@thyrsus.com>
-.TH motd 5 2023-10-31 "Linux man-pages 6.06"
+.TH motd 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 motd \- message of the day
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/nanorc.5 b/upstream/fedora-rawhide/man5/nanorc.5
index 4416b7dd..672f6e16 100644
--- a/upstream/fedora-rawhide/man5/nanorc.5
+++ b/upstream/fedora-rawhide/man5/nanorc.5
@@ -1,4 +1,4 @@
-.\" Copyright (C) 2003-2011, 2013-2023 Free Software Foundation, Inc.
+.\" Copyright (C) 2003-2011, 2013-2024 Free Software Foundation, Inc.
 .\"
 .\" This document is dual-licensed.  You may distribute and/or modify it
 .\" under the terms of either of the following licenses:
@@ -16,14 +16,14 @@
 .\"   Documentation License along with this program.  If not, see
 .\"   <https://www.gnu.org/licenses/>.
 .\"
-.TH NANORC 5 "version 7.2" "January 2023"
+.TH NANORC 5 "version 8.0" "May 2024"
 
 .SH NAME
 nanorc \- GNU nano's configuration file
 
 .SH DESCRIPTION
 The \fInanorc\fP files contain the default settings for \fBnano\fP,
-a small and friendly editor.  During startup, if \fB\-\-rcfile\fR
+a small and friendly text editor.  During startup, if \fB\-\-rcfile\fR
 is not given, \fBnano\fR will read two files: first the
 system-wide settings, from \fI/etc/nanorc\fP (the exact path might be
 different on your system), and then the user-specific settings, either
@@ -32,6 +32,24 @@ or from \fI~/.config/nano/nanorc\fR, whichever is encountered first.
 If \fB\-\-rcfile\fR is given, \fBnano\fR will read just the specified
 settings file.
 
+.SH NOTICE
+Since version 8.0, to be newcomer friendly, \fB^F\fR starts a forward search,
+\fB^B\fR starts a backward search, \fBM\-F\fR searches the next occurrence
+forward, and \fBM\-B\fR searches the next occurrence backward.  If you want
+those keystrokes to do what they did before version 8.0, add the following
+lines at the end of your \fInanorc\fR file:
+.sp
+.RS 4
+.B bind ^F forward main
+.br
+.B bind ^B back main
+.br
+.B bind M\-F formatter main
+.br
+.B bind M\-B linter main
+.RE
+.sp
+
 .SH OPTIONS
 The configuration file accepts a series of \fBset\fP and \fBunset\fP
 commands, which can be used to configure nano on startup without using
@@ -80,10 +98,12 @@ with \fBset backup\fR or \fB\-\-backup\fR or \fB\-B\fR.
 The uniquely numbered files are stored in the specified \fIdirectory\fR.
 .TP
 .B set boldtext
-Use bold instead of reverse video for the title bar, status bar, key combos,
-function tags, line numbers, and selected text.  This can be overridden by
-setting the options \fBtitlecolor\fP, \fBstatuscolor\fP, \fBkeycolor\fP,
-\fBfunctioncolor\fP, \fBnumbercolor\fP, and \fBselectedcolor\fP.
+Use bold instead of reverse video for the title bar, status bar,
+prompt bar, mini bar, key combos, function tags, line numbers,
+and selected text.  This can be overridden by setting the options
+\fBtitlecolor\fP, \fBstatuscolor\fP,
+\fBpromptcolor\fP, \fBminicolor\fP, \fBkeycolor\fP, \fBfunctioncolor\fP,
+\fBnumbercolor\fP, and/or \fBselectedcolor\fP.
 .TP
 .B set bookstyle
 When justifying, treat any line that starts with whitespace as the
@@ -171,7 +191,7 @@ The default value is "\fB(<[{)>]}\fP".
 .B set minibar
 Suppress the title bar and instead show information about
 the current buffer at the bottom of the screen, in the space
-for the status bar.  In this "minibar" the filename is shown
+for the status bar.  In this "mini bar" the filename is shown
 on the left, followed by an asterisk if the buffer has been modified.
 On the right are displayed the current line and column number, the
 code of the character under the cursor (in Unicode format: U+xxxx),
@@ -186,7 +206,7 @@ The line plus column numbers and the character code are displayed only when
 The state flags are displayed only when \fBset stateflags\fR is used.
 .TP
 .B set minicolor \fR[\fBbold,\fR][\fBitalic,\fR]\fIfgcolor\fB,\fIbgcolor\fR
-Use this color combination for the minibar.
+Use this color combination for the mini bar.
 (When this option is not specified, the colors of the title bar are used.)
 See \fBset titlecolor\fR for more details.
 .TP
@@ -239,7 +259,7 @@ See \fBset titlecolor\fR for more details.
 .BI "set punct """ characters """
 Set the characters treated as closing punctuation when justifying
 paragraphs.  This may not include blank characters.  Only the
-specfified closing punctuation, optionally followed by closing brackets
+specified closing punctuation, optionally followed by closing brackets
 (see \fBbrackets\fP), can end sentences.  The default value is "\fB!.?\fP".
 .TP
 .B set quickblank
@@ -278,8 +298,6 @@ Save a changed buffer automatically on exit (\fB^X\fR); don't prompt.
 .TP
 .B set scrollercolor \fIfgcolor\fB,\fIbgcolor\fR
 Use this color combination for the indicator alias "scrollbar".
-(On terminal emulators that link to a libvte older than version 0.55,
-using a background color here does not work correctly.)
 See \fBset titlecolor\fR for more details.
 .TP
 .B set selectedcolor \fR[\fBbold,\fR][\fBitalic,\fR]\fIfgcolor\fB,\fIbgcolor\fR
@@ -335,6 +353,7 @@ greater than 0.  The default value is \fB8\fR.
 .B set tabstospaces
 Convert each typed tab to spaces -- to the number of spaces
 that a tab at that position would take up.
+(Note: pasted tabs are not converted.)
 .TP
 .B set titlecolor \fR[\fBbold,\fR][\fBitalic,\fR]\fIfgcolor\fB,\fIbgcolor\fR
 Use this color combination for the title bar.
@@ -345,6 +364,8 @@ Each of these eight names may be prefixed with the word \fBlight\fR
 to get a brighter version of that color.
 The word \fBgrey\fR or \fBgray\fR may be used
 as a synonym for \fBlightblack\fR.
+On a Linux console, \fBlight\fR does not have
+any effect for a background color.
 On terminal emulators that can do at least 256 colors,
 other valid (but unprefixable) color names are:
 .BR pink ", " purple ", " mauve ", " lagoon ", " mint ", "
@@ -398,12 +419,6 @@ and disappears after 1.5 seconds or upon the next keystroke.
 With \fBM\-Z\fR the title bar plus status bar can be toggled.
 With \fBM\-X\fR the help lines.
 
-.SH NOTES
-Option \fBset suspendable\fR has been removed.
-Suspension is enabled by default, reachable via \fB^T^Z\fR.
-(If you want a plain \fB^Z\fR to suspend nano,
-add \fBbind ^Z suspend main\fR to your nanorc.)
-
 .SH SYNTAX HIGHLIGHTING
 Coloring the different syntactic elements of a file
 is done via regular expressions (see the \fBcolor\fR command below).
@@ -444,9 +459,10 @@ will be added to this syntax, until a new \fBsyntax\fR
 command is encountered.
 .sp
 When \fBnano\fR is run, this syntax will be automatically
-activated if the current filename matches the extended regular
-expression \fIfileregex\fR.  Or the syntax can be explicitly
-activated by using the \fB\-Y\fR or \fB\-\-syntax\fR
+activated (for the relevant buffer) if the absolute filename
+matches the extended regular expression \fIfileregex\fR.
+Or the syntax can be explicitly activated (for all buffers)
+by using the \fB\-Y\fR or \fB\-\-syntax\fR
 command-line option followed by the \fIname\fR.
 .sp
 The syntax \fBdefault\fP is special: it takes no \fIfileregex\fR,
@@ -499,6 +515,8 @@ Each of these eight names may be prefixed with the word \fBlight\fR
 to get a brighter version of that color.
 The word \fBgrey\fR or \fBgray\fR may be used
 as a synonym for \fBlightblack\fR.
+On a Linux console, \fBlight\fR does not have
+any effect for a background color.
 On terminal emulators that can do at least 256 colors,
 other valid (but unprefixable) color names are:
 .BR pink ", " purple ", " mauve ", " lagoon ", " mint ", "
@@ -570,7 +588,7 @@ menus where the key exists when \fBall\fP is used).
 .sp
 Note that \fBbind \fIkey\fR \fB"{\fIfunction\fB}"\fR \fImenu\fR is equivalent
 to \fBbind \fIkey\fR \fIfunction\fR \fImenu\fR, except that for the latter form
-\fBnano\fR will check the availabilty of the \fIfunction\fR in the given \fImenu\fR
+\fBnano\fR will check the availability of the \fIfunction\fR in the given \fImenu\fR
 at startup time (and report an error if it does not exist there), whereas for the
 first form \fBnano\fR will check at execution time that the \fIfunction\fR exists
 but not whether it makes any sense in the current menu.  The user has to take care
@@ -791,6 +809,12 @@ Moves the cursor to the beginning of the current or preceding block of text.
 .B nextblock
 Moves the cursor to the beginning of the next block of text.
 .TP
+.B toprow
+Moves the cursor to the first row in the viewport.
+.TP
+.B bottomrow
+Moves the cursor to the last row in the viewport.
+.TP
 .B pageup
 Goes up one screenful.
 .TP
@@ -886,7 +910,7 @@ Toggles between searching for something and replacing something.
 Toggles between searching for text and targeting a line number.
 .TP
 .B flipexecute
-Toggles between inserting a file and executing a command.
+Switches from inserting a file to executing a command.
 .TP
 .B flippipe
 When executing a command, toggles whether the current buffer (or marked
@@ -1038,6 +1062,20 @@ For \fBbind\fR it means all menus where the specified \fIfunction\fR exists;
 for \fBunbind\fR it means all menus where the specified \fIkey\fR exists.
 .RE
 
+.SH EXAMPLES
+To make \fBCtrl+Z\fR suspend nano:
+.sp
+.RS
+.B bind ^Z suspend main
+.RE
+.sp
+To make \fBShift+Alt+C\fR copy the marked region to the system's clipboard:
+.sp
+.RS
+.B bind Sh-M-C """{execute}| xsel -ib {enter}{undo}""" main
+.RE
+.sp
+
 .SH FILES
 .TP
 .I /etc/nanorc
diff --git a/upstream/fedora-rawhide/man5/networkd.conf.5 b/upstream/fedora-rawhide/man5/networkd.conf.5
index caead9da..9064e702 100644
--- a/upstream/fedora-rawhide/man5/networkd.conf.5
+++ b/upstream/fedora-rawhide/man5/networkd.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "NETWORKD\&.CONF" "5" "" "systemd 255" "networkd.conf"
+.TH "NETWORKD\&.CONF" "5" "" "systemd 256~rc3" "networkd.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,26 +23,39 @@
 networkd.conf, networkd.conf.d \- Global Network configuration files
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/systemd/networkd\&.conf
-.PP
+.RE
+.RS 4
+/run/systemd/networkd\&.conf
+.RE
+.RS 4
+/usr/lib/systemd/networkd\&.conf
+.RE
+.RS 4
 /etc/systemd/networkd\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
+/run/systemd/networkd\&.conf\&.d/*\&.conf
+.RE
+.RS 4
 /usr/lib/systemd/networkd\&.conf\&.d/*\&.conf
+.RE
 .SH "DESCRIPTION"
 .PP
-These configuration files control global network parameters\&. Currently the DHCP Unique Identifier (DUID)\&.
+These configuration files control global network parameters\&.
 .SH "CONFIGURATION DIRECTORIES AND PRECEDENCE"
 .PP
-The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is either in
-/usr/lib/systemd/
-or
-/etc/systemd/
-and contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
+The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is loaded from one of the listed directories in order of priority, only the first file found is used:
+/etc/systemd/,
+/run/systemd/,
+/usr/local/lib/systemd/,
+/usr/lib/systemd/\&. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can also be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
 /etc/
-if it\*(Aqs shipped in
-/usr/) however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
+if it\*(Aqs shipped under
+/usr/), however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
 .PP
-In addition to the "main" configuration file, drop\-in configuration snippets are read from
+In addition to the main configuration file, drop\-in configuration snippets are read from
 /usr/lib/systemd/*\&.conf\&.d/,
 /usr/local/lib/systemd/*\&.conf\&.d/, and
 /etc/systemd/*\&.conf\&.d/\&. Those drop\-ins have higher precedence and override the main configuration file\&. Files in the
@@ -52,7 +65,12 @@ configuration subdirectories are sorted by their filename in lexicographic order
 When packages need to customize the configuration, they can install drop\-ins under
 /usr/\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defined a concept of drop\-in priority to allow distributions to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defines a concept of drop\-in priorities to allow OS vendors to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&. It is recommended to use the range 10\-40 for drop\-ins in
+/usr/
+and the range 60\-90 for drop\-ins in
+/etc/
+and
+/run/, to make sure that local and transient drop\-ins take priority over drop\-ins shipped by the OS vendor\&.
 .PP
 To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -111,6 +129,16 @@ is true or
 Added in version 246\&.
 .RE
 .PP
+\fIManageForeignNextHops=\fR
+.RS 4
+A boolean\&. When true,
+\fBsystemd\-networkd\fR
+will remove nexthops that are not configured in \&.network files (except for routes with protocol
+"kernel")\&. When false, it will not remove any foreign nexthops, keeping them even if they are not configured in a \&.network file\&. Defaults to yes\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fIRouteTable=\fR
 .RS 4
 Defines the route table name\&. Takes a whitespace\-separated list of the pairs of route table name and number\&. The route table name and number in each pair are separated with a colon, i\&.e\&.,
@@ -122,6 +150,31 @@ Defines the route table name\&. Takes a whitespace\-separated list of the pairs
 Added in version 248\&.
 .RE
 .PP
+\fIIPv4Forwarding=\fR
+.RS 4
+Configures IPv4 packet forwarding for the system\&. Takes a boolean value\&. This controls the
+net\&.ipv4\&.conf\&.default\&.forwarding
+and
+net\&.ipv4\&.conf\&.all\&.forwardingsysctl options\&. See
+\m[blue]\fBIP Sysctl\fR\m[]\&\s-2\u[1]\d\s+2
+for more details about the sysctl options\&. Defaults to unset and the sysctl options will not be changed\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
+\fIIPv6Forwarding=\fR
+.RS 4
+Configures IPv6 packet forwarding for the system\&. Takes a boolean value\&. This controls the
+net\&.ipv6\&.conf\&.default\&.forwarding
+and
+net\&.ipv6\&.conf\&.all\&.forwarding
+sysctl options\&. See
+\m[blue]\fBIP Sysctl\fR\m[]\&\s-2\u[1]\d\s+2
+for more details about the sysctl options\&. Defaults to unset and the sysctl options will not be changed\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fIIPv6PrivacyExtensions=\fR
 .RS 4
 Specifies the default value for per\-network
@@ -134,6 +187,30 @@ and
 .sp
 Added in version 254\&.
 .RE
+.PP
+\fIUseDomains=\fR
+.RS 4
+Specifies the network\- and protocol\-independent default value for the same settings in [IPv6AcceptRA], [DHCPv4], and [DHCPv6] sections below\&. Takes a boolean, or the special value
+\fBroute\fR\&. See the same setting in
+\fBsystemd.network\fR(5)\&. Defaults to
+"no"\&.
+.sp
+Added in version 256\&.
+.RE
+.SH "[IPV6ACCEPTRA] SECTION OPTIONS"
+.PP
+This section configures the default setting of the Neighbor Discovery\&. The following options are available in the [IPv6AcceptRA] section:
+.PP
+\fIUseDomains=\fR
+.RS 4
+Specifies the network\-independent default value for the same setting in the [IPv6AcceptRA] section in
+\fBsystemd.network\fR(5)\&. Takes a boolean, or the special value
+\fBroute\fR\&. When unspecified, the value specified in the [Network] section in
+\fBnetworkd.conf\fR(5), which defaults to
+"no", will be used\&.
+.sp
+Added in version 256\&.
+.RE
 .SH "[DHCPV4] SECTION OPTIONS"
 .PP
 This section configures the DHCP Unique Identifier (DUID) value used by DHCP protocol\&. DHCPv4 client protocol sends IAID and DUID to the DHCP server when acquiring a dynamic IPv4 address if
@@ -145,7 +222,7 @@ The following options are understood:
 \fIDUIDType=\fR
 .RS 4
 Specifies how the DUID should be generated\&. See
-\m[blue]\fBRFC 3315\fR\m[]\&\s-2\u[1]\d\s+2
+\m[blue]\fBRFC 3315\fR\m[]\&\s-2\u[2]\d\s+2
 for a description of all the options\&.
 .sp
 This takes an integer in the range 0\&...65535, or one of the following string values:
@@ -209,8 +286,8 @@ The DUID value specified here overrides the DUID that
 \fBsystemd-networkd.service\fR(8)
 generates from the machine ID\&. To configure DUID per\-network, see
 \fBsystemd.network\fR(5)\&. The configured DHCP DUID should conform to the specification in
-\m[blue]\fBRFC 3315\fR\m[]\&\s-2\u[2]\d\s+2,
-\m[blue]\fBRFC 6355\fR\m[]\&\s-2\u[3]\d\s+2\&. To configure IAID, see
+\m[blue]\fBRFC 3315\fR\m[]\&\s-2\u[3]\d\s+2,
+\m[blue]\fBRFC 6355\fR\m[]\&\s-2\u[4]\d\s+2\&. To configure IAID, see
 \fBsystemd.network\fR(5)\&.
 .PP
 \fBExample\ \&1.\ \&A DUIDType=vendor with a custom value\fR
@@ -231,6 +308,13 @@ This specifies a 14 byte DUID, with the type DUID\-EN ("00:02"), enterprise numb
 
 Added in version 230\&.
 .RE
+.PP
+\fIUseDomains=\fR
+.RS 4
+Same as the one in the [IPv6AcceptRA] section, but applied for DHCPv4 protocol\&.
+.sp
+Added in version 256\&.
+.RE
 .SH "[DHCPV6] SECTION OPTIONS"
 .PP
 This section configures the DHCP Unique Identifier (DUID) value used by DHCPv6 protocol\&. DHCPv6 client protocol sends the DHCP Unique Identifier and the interface Identity Association Identifier (IAID) to a DHCPv6 server when acquiring a dynamic IPv6 address\&. IAID and DUID allows a DHCPv6 server to uniquely identify the machine and the interface requesting a DHCP IP address\&. To configure IAID, see
@@ -244,25 +328,43 @@ As in the [DHCPv4] section\&.
 .sp
 Added in version 249\&.
 .RE
+.PP
+\fIUseDomains=\fR
+.RS 4
+As in the [DHCPv4] section\&.
+.sp
+Added in version 256\&.
+.RE
+.SH "[DHCPSERVER] SECTION OPTIONS"
+.PP
+This section configures the default setting of the DHCP server\&. The following options are available in the [DHCPServer] section:
+.PP
+\fIUseDomains=\fR
+.RS 4
+Same as the one in the [IPv6AcceptRA] section, but applied for DHCPv4 protocol\&.
+.sp
+Added in version 256\&.
+.RE
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd.network\fR(5),
-\fBsystemd-networkd.service\fR(8),
-\fBmachine-id\fR(5),
-\fBsd_id128_get_machine_app_specific\fR(3)
+\fBsystemd\fR(1), \fBsystemd.network\fR(5), \fBsystemd-networkd.service\fR(8), \fBmachine-id\fR(5), \fBsd_id128_get_machine_app_specific\fR(3)
 .SH "NOTES"
 .IP " 1." 4
+IP Sysctl
+.RS 4
+\%https://docs.kernel.org/networking/ip-sysctl.html
+.RE
+.IP " 2." 4
 RFC 3315
 .RS 4
 \%https://tools.ietf.org/html/rfc3315#section-9
 .RE
-.IP " 2." 4
+.IP " 3." 4
 RFC 3315
 .RS 4
 \%http://tools.ietf.org/html/rfc3315#section-9
 .RE
-.IP " 3." 4
+.IP " 4." 4
 RFC 6355
 .RS 4
 \%http://tools.ietf.org/html/rfc6355
diff --git a/upstream/fedora-rawhide/man5/networks.5 b/upstream/fedora-rawhide/man5/networks.5
index f30ceef9..168c2c58 100644
--- a/upstream/fedora-rawhide/man5/networks.5
+++ b/upstream/fedora-rawhide/man5/networks.5
@@ -4,7 +4,7 @@
 .\"
 .\" 2008-09-04, mtk, taken from Debian downstream, with a few light edits
 .\"
-.TH networks 5 2023-10-31 "Linux man-pages 6.06"
+.TH networks 5 2024-02-25 "Linux man-pages 6.7"
 .SH NAME
 networks \- network name information
 .SH DESCRIPTION
@@ -15,7 +15,7 @@ names for these networks.
 Each line represents a network and has the following structure:
 .P
 .RS
-.I name number aliases ...
+.I name number aliases .\|.\|.
 .RE
 .P
 where the fields are delimited by spaces or tabs.
diff --git a/upstream/fedora-rawhide/man5/nfs.5 b/upstream/fedora-rawhide/man5/nfs.5
index 7103d28e..233a7177 100644
--- a/upstream/fedora-rawhide/man5/nfs.5
+++ b/upstream/fedora-rawhide/man5/nfs.5
@@ -186,6 +186,10 @@ infrequently used request types are retried after 1.1 seconds.
 After each retransmission, the NFS client doubles the timeout for
 that request,
 up to a maximum timeout length of 60 seconds.
+.IP
+Any timeo value greater than default value will be set to the default value.
+For TCP and RDMA, default value is 600 (60 seconds).
+For UDP, default value is 60 (6 seconds).
 .TP 1.5i
 .BI retrans= n
 The number of times the NFS client retries a request before
diff --git a/upstream/fedora-rawhide/man5/nologin.5 b/upstream/fedora-rawhide/man5/nologin.5
index e5875188..b5242a4c 100644
--- a/upstream/fedora-rawhide/man5/nologin.5
+++ b/upstream/fedora-rawhide/man5/nologin.5
@@ -5,7 +5,7 @@
 .\"
 .\" Modified Sun Jul 25 11:06:34 1993 by Rik Faith (faith@cs.unc.edu)
 .\" Corrected Mon Oct 21 17:47:19 EDT 1996 by Eric S. Raymond (esr@thyrsus.com)
-.TH nologin 5 2022-10-30 "Linux man-pages 6.06"
+.TH nologin 5 2022-10-30 "Linux man-pages 6.7"
 .SH NAME
 nologin \- prevent unprivileged users from logging into the system
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/nscd.conf.5 b/upstream/fedora-rawhide/man5/nscd.conf.5
index 6f9695cd..c2a1d61e 100644
--- a/upstream/fedora-rawhide/man5/nscd.conf.5
+++ b/upstream/fedora-rawhide/man5/nscd.conf.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-2.0-or-later
 .\"
-.TH nscd.conf 5 2023-10-31 "Linux man-pages 6.06"
+.TH nscd.conf 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 nscd.conf \- name service cache daemon configuration file
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/nss.5 b/upstream/fedora-rawhide/man5/nss.5
index cf301fc3..00b9f0c7 100644
--- a/upstream/fedora-rawhide/man5/nss.5
+++ b/upstream/fedora-rawhide/man5/nss.5
@@ -3,7 +3,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-2.0-only
 .\"
-.TH nss 5 2023-10-31 "Linux man-pages 6.06"
+.TH nss 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 nss \- Name Service Switch configuration file
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/nsswitch.conf.5 b/upstream/fedora-rawhide/man5/nsswitch.conf.5
index 2d2bd64c..34dd7d7a 100644
--- a/upstream/fedora-rawhide/man5/nsswitch.conf.5
+++ b/upstream/fedora-rawhide/man5/nsswitch.conf.5
@@ -3,7 +3,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-2.0-or-later
 .\"
-.TH nsswitch.conf 5 2023-10-31 "Linux man-pages 6.06"
+.TH nsswitch.conf 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 nsswitch.conf \- Name Service Switch configuration file
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/oomd.conf.5 b/upstream/fedora-rawhide/man5/oomd.conf.5
index b6b0b1a8..706775a8 100644
--- a/upstream/fedora-rawhide/man5/oomd.conf.5
+++ b/upstream/fedora-rawhide/man5/oomd.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "OOMD\&.CONF" "5" "" "systemd 255" "oomd.conf"
+.TH "OOMD\&.CONF" "5" "" "systemd 256~rc3" "oomd.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,11 +23,24 @@
 oomd.conf, oomd.conf.d \- Global \fBsystemd\-oomd\fR configuration files
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/systemd/oomd\&.conf
-.PP
+.RE
+.RS 4
+/run/systemd/oomd\&.conf
+.RE
+.RS 4
+/usr/lib/systemd/oomd\&.conf
+.RE
+.RS 4
 /etc/systemd/oomd\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
+/run/systemd/oomd\&.conf\&.d/*\&.conf
+.RE
+.RS 4
 /usr/lib/systemd/oomd\&.conf\&.d/*\&.conf
+.RE
 .SH "DESCRIPTION"
 .PP
 These files configure the various parameters of the
@@ -38,16 +51,16 @@ userspace out\-of\-memory (OOM) killer,
 for a general description of the syntax\&.
 .SH "CONFIGURATION DIRECTORIES AND PRECEDENCE"
 .PP
-The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is either in
-/usr/lib/systemd/
-or
-/etc/systemd/
-and contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
+The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is loaded from one of the listed directories in order of priority, only the first file found is used:
+/etc/systemd/,
+/run/systemd/,
+/usr/local/lib/systemd/,
+/usr/lib/systemd/\&. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can also be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
 /etc/
-if it\*(Aqs shipped in
-/usr/) however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
+if it\*(Aqs shipped under
+/usr/), however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
 .PP
-In addition to the "main" configuration file, drop\-in configuration snippets are read from
+In addition to the main configuration file, drop\-in configuration snippets are read from
 /usr/lib/systemd/*\&.conf\&.d/,
 /usr/local/lib/systemd/*\&.conf\&.d/, and
 /etc/systemd/*\&.conf\&.d/\&. Those drop\-ins have higher precedence and override the main configuration file\&. Files in the
@@ -57,7 +70,12 @@ configuration subdirectories are sorted by their filename in lexicographic order
 When packages need to customize the configuration, they can install drop\-ins under
 /usr/\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defined a concept of drop\-in priority to allow distributions to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defines a concept of drop\-in priorities to allow OS vendors to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&. It is recommended to use the range 10\-40 for drop\-ins in
+/usr/
+and the range 60\-90 for drop\-ins in
+/etc/
+and
+/run/, to make sure that local and transient drop\-ins take priority over drop\-ins shipped by the OS vendor\&.
 .PP
 To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -108,7 +126,4 @@ Added in version 248\&.
 .RE
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd.resource-control\fR(5),
-\fBsystemd-oomd.service\fR(8),
-\fBoomctl\fR(1)
+\fBsystemd\fR(1), \fBsystemd.resource-control\fR(5), \fBsystemd-oomd.service\fR(8), \fBoomctl\fR(1)
diff --git a/upstream/fedora-rawhide/man5/org.freedesktop.LogControl1.5 b/upstream/fedora-rawhide/man5/org.freedesktop.LogControl1.5
index 70733a8e..30ea304e 100644
--- a/upstream/fedora-rawhide/man5/org.freedesktop.LogControl1.5
+++ b/upstream/fedora-rawhide/man5/org.freedesktop.LogControl1.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "ORG\&.FREEDESKTOP\&.LOGCONTROL1" "5" "" "systemd 255" "org.freedesktop.LogControl1"
+.TH "ORG\&.FREEDESKTOP\&.LOGCONTROL1" "5" "" "systemd 256~rc3" "org.freedesktop.LogControl1"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -181,13 +181,10 @@ for details about
 
 #define _cleanup_(f) __attribute__((cleanup(f)))
 
-#define check(log_level, x) ({                  \e
-  int _r = (x);                                 \e
-  errno = _r < 0 ? \-_r : 0;                     \e
-  sd_journal_print((log_level), #x ": %m");     \e
-  if (_r < 0)                                   \e
-    return EXIT_FAILURE;                        \e
-  })
+static int log_error(int log_level, int error, const char *str) {
+  sd_journal_print(log_level, "%s failed: %s", str, strerror(\-error));
+  return error;
+}
 
 typedef enum LogTarget {
   LOG_TARGET_JOURNAL,
@@ -265,7 +262,8 @@ static int property_set(
     return r;
 
   if (strcmp(property, "LogLevel") == 0) {
-    for (int i = 0; i < LOG_DEBUG + 1; i++)
+    int i;
+    for (i = 0; i < LOG_DEBUG + 1; i++)
       if (strcmp(value, log_level_table[i]) == 0) {
         o\->log_level = i;
         setlogmask(LOG_UPTO(i));
@@ -279,7 +277,8 @@ static int property_set(
   }
 
   if (strcmp(property, "LogTarget") == 0) {
-    for (LogTarget i = 0; i < _LOG_TARGET_MAX; i++)
+    LogTarget i;
+    for (i = 0; i < _LOG_TARGET_MAX; i++)
       if (strcmp(value, log_target_table[i]) == 0) {
         o\->log_target = i;
         return 0;
@@ -331,6 +330,7 @@ int main(int argc, char **argv) {
     \&.log_target = LOG_TARGET_JOURNAL,
     \&.syslog_identifier = "example",
   };
+  int r;
 
   /* https://man7\&.org/linux/man\-pages/man3/setlogmask\&.3\&.html
    * Programs using syslog() instead of sd_journal can use this API to cut logs
@@ -341,37 +341,49 @@ int main(int argc, char **argv) {
   /* Acquire a connection to the bus, letting the library work out the details\&.
    * https://www\&.freedesktop\&.org/software/systemd/man/sd_bus_default\&.html
    */
-  check(o\&.log_level, sd_bus_default(&bus));
+  r = sd_bus_default(&bus);
+  if (r < 0)
+    return log_error(o\&.log_level, r, "sd_bus_default()");
 
   /* Publish an interface on the bus, specifying our well\-known object access
    * path and public interface name\&.
    * https://www\&.freedesktop\&.org/software/systemd/man/sd_bus_add_object\&.html
    * https://dbus\&.freedesktop\&.org/doc/dbus\-tutorial\&.html
    */
-  check(o\&.log_level, sd_bus_add_object_vtable(bus, NULL,
-                                              "/org/freedesktop/LogControl1",
-                                              "org\&.freedesktop\&.LogControl1",
-                                              vtable,
-                                              &o));
+  r = sd_bus_add_object_vtable(bus, NULL,
+                               "/org/freedesktop/LogControl1",
+                               "org\&.freedesktop\&.LogControl1",
+                               vtable,
+                               &o);
+  if (r < 0)
+    return log_error(o\&.log_level, r, "sd_bus_add_object_vtable()");
 
   /* By default the service is assigned an ephemeral name\&. Also add a fixed
    * one, so that clients know whom to call\&.
    * https://www\&.freedesktop\&.org/software/systemd/man/sd_bus_request_name\&.html
    */
-  check(o\&.log_level, sd_bus_request_name(bus, "org\&.freedesktop\&.Example", 0));
+  r = sd_bus_request_name(bus, "org\&.freedesktop\&.Example", 0);
+  if (r < 0)
+    return log_error(o\&.log_level, r, "sd_bus_request_name()");
 
   for (;;) {
     /* https://www\&.freedesktop\&.org/software/systemd/man/sd_bus_wait\&.html
      */
-    check(o\&.log_level, sd_bus_wait(bus, UINT64_MAX));
+    r = sd_bus_wait(bus, UINT64_MAX);
+    if (r < 0)
+      return log_error(o\&.log_level, r, "sd_bus_wait()");
     /* https://www\&.freedesktop\&.org/software/systemd/man/sd_bus_process\&.html
      */
-    check(o\&.log_level, sd_bus_process(bus, NULL));
+    r = sd_bus_process(bus, NULL);
+    if (r < 0)
+      return log_error(o\&.log_level, r, "sd_bus_process()");
   }
 
   /* https://www\&.freedesktop\&.org/software/systemd/man/sd_bus_release_name\&.html
    */
-  check(o\&.log_level, sd_bus_release_name(bus, "org\&.freedesktop\&.Example"));
+  r = sd_bus_release_name(bus, "org\&.freedesktop\&.Example");
+  if (r < 0)
+    return log_error(o\&.log_level, r, "sd_bus_release_name()");
 
   return 0;
 }
@@ -384,8 +396,4 @@ This creates a simple server on the bus\&. It implements the LogControl1 interfa
 \fBsd_journal_print\fR(3)\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBjournalctl\fR(1),
-\fBsystemctl\fR(1),
-\fBsystemd.service\fR(5),
-\fBsyslog\fR(3)
+\fBsystemd\fR(1), \fBjournalctl\fR(1), \fBsystemctl\fR(1), \fBsystemd.service\fR(5), \fBsyslog\fR(3)
diff --git a/upstream/fedora-rawhide/man5/org.freedesktop.home1.5 b/upstream/fedora-rawhide/man5/org.freedesktop.home1.5
index b91e1d7e..fc16afb4 100644
--- a/upstream/fedora-rawhide/man5/org.freedesktop.home1.5
+++ b/upstream/fedora-rawhide/man5/org.freedesktop.home1.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "ORG\&.FREEDESKTOP\&.HOME1" "5" "" "systemd 255" "org.freedesktop.home1"
+.TH "ORG\&.FREEDESKTOP\&.HOME1" "5" "" "systemd 256~rc3" "org.freedesktop.home1"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -61,14 +61,18 @@ node /org/freedesktop/home1 {
                          out b incomplete,
                          out o bus_path);
       ListHomes(out a(susussso) home_areas);
-      @org\&.freedesktop\&.systemd1\&.Privileged("true")
       ActivateHome(in  s user_name,
                    in  s secret);
+      ActivateHomeIfReferenced(in  s user_name,
+                               in  s secret);
       @org\&.freedesktop\&.systemd1\&.Privileged("true")
       DeactivateHome(in  s user_name);
       RegisterHome(in  s user_record);
       UnregisterHome(in  s user_name);
       CreateHome(in  s user_record);
+      CreateHomeEx(in  s user_record,
+                   in  a{sh} blobs,
+                   in  t flags);
       RealizeHome(in  s user_name,
                   in  s secret);
       RemoveHome(in  s user_name);
@@ -78,6 +82,9 @@ node /org/freedesktop/home1 {
       AuthenticateHome(in  s user_name,
                        in  s secret);
       UpdateHome(in  s user_record);
+      UpdateHomeEx(in  s user_record,
+                   in  a{sh} blobs,
+                   in  t flags);
       ResizeHome(in  s user_name,
                  in  t size,
                  in  s secret);
@@ -98,6 +105,10 @@ node /org/freedesktop/home1 {
               in  b please_suspend,
               out h send_fd);
       @org\&.freedesktop\&.systemd1\&.Privileged("true")
+      RefHomeUnrestricted(in  s user_name,
+                          in  b please_suspend,
+                          out h send_fd);
+      @org\&.freedesktop\&.systemd1\&.Privileged("true")
       ReleaseHome(in  s user_name);
       @org\&.freedesktop\&.systemd1\&.Privileged("true")
       LockAllHomes();
@@ -144,6 +155,10 @@ node /org/freedesktop/home1 {
 
 
 
+
+
+
+
 .SS "Methods"
 .PP
 \fBGetHomeByName()\fR
@@ -151,7 +166,7 @@ returns basic user information (a minimal subset of the full user record), provi
 \fBgetpwnam\fR(3)
 returns: the numeric UID and GID, the real name, home directory and shell\&. In addition it returns a state identifier describing the state the user\*(Aqs home directory is in, as well as a bus path referring to the bus object encapsulating the user record and home directory\&. This object implements the
 org\&.freedesktop\&.home1\&.Home
-interface documented below\&.
+interface documented below\&. This method, and most others in this interface that take user names, will try to use the caller\*(Aqs home area if the specified user name is an empty string\&.
 .PP
 \fBGetHomeByUID()\fR
 is similar to
@@ -190,6 +205,11 @@ method on the
 org\&.freedesktop\&.home1\&.Home
 interface documented below, but may be called on the manager object and takes a user name as additional argument, instead\&.
 .PP
+\fBActivateHomeIfReferenced()\fR
+is identical to
+\fBActivateHome()\fR\&. However, the call only succeeds if the home directory is currently referenced\&. Useful in conjunction with
+\fBRefHomeUnrestricted()\fR, which allows creating a reference to a home directory even if the home directory is not active\&.
+.PP
 \fBDeactivateHome()\fR
 deactivates (i\&.e\&. unmounts) the home directory of the specified user\&. It is equivalent to the
 \fBDeactivate()\fR
@@ -222,6 +242,21 @@ registers and creates a new home directory\&. This takes a fully specified JSON
 "secret"
 section)\&. This registers the user record locally and creates a home directory matching it, depending on the settings specified in the record in combination with local configuration\&.
 .PP
+\fBCreateHomeEx()\fR
+is like
+\fBCreateHome()\fR, but it allows the home directory to be created with a pre\-populated blob directory (see
+\m[blue]\fBUser Record Blob Directories\fR\m[]\&\s-2\u[2]\d\s+2
+for more info)\&. This can be done via the dictionary passed as the
+\fIblobs\fR
+argument to this method: the values are open file descriptors to regular files, and the keys are the filenames that should contain their respective file\*(Aqs data in the blob directory\&. Note that for security reasons, the file descriptors passed into this method must have enough privileges to read their target file and thus cannot be
+"O_PATH"; this is done to ensure the caller is actually permitted to read the file they are asking to publish in the blob directories\&. If the user record passed as the first argument contains a
+"blobManifest"
+field it will be enforced; otherwise, a
+"blobManifest"
+field will be generated and inserted into the record\&. The
+\fIflags\fR
+argument may be used for future expansion, but for now pass 0\&.
+.PP
 \fBRealizeHome()\fR
 creates a home directory whose user record is already registered locally\&. This takes a user name plus a user record consisting only of the
 "secret"
@@ -268,7 +303,7 @@ org\&.freedesktop\&.home1\&.Home
 interface\&.
 .PP
 \fBUpdateHome()\fR
-updates a locally registered user record\&. Takes a fully specified JSON user record as argument (including the
+updates a locally registered user record\&. Takes a fully specified JSON user record as argument (possibly including the
 "secret"
 section)\&. A user with a matching name and realm must be registered locally already, and the last change timestamp of the newly supplied record must be newer than the previously existing user record\&. Note this operation updates the user record only, it does not propagate passwords/authentication tokens from the user record to the storage back\-end, or resizes the storage back\-end\&. Typically a home directory is first updated, and then the password of the underlying storage updated using
 \fBChangePasswordHome()\fR
@@ -279,10 +314,40 @@ on the
 org\&.freedesktop\&.home1\&.Home
 interface\&.
 .PP
+\fBUpdateHomeEx()\fR
+is like
+\fBUpdateHome()\fR, but it allows for changes to the blob directory (see
+\m[blue]\fBUser Record Blob Directories\fR\m[]\&\s-2\u[2]\d\s+2
+for more info)\&. The
+\fIblobs\fR
+argument works in the same way as
+\fBCreateHomeEx()\fR, so check there for details\&. The new blob directory contents passed into this method will completely replace the user\*(Aqs existing blob directory\&. The
+\fIflags\fR
+argument can be used to further customize the behavior of this method via flags defined as follows:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+#define SD_HOMED_UPDATE_OFFLINE (UINT64_C(1) << 0)
+      
+.fi
+.if n \{\
+.RE
+.\}
+.PP
+When
+\fBSD_HOMED_UPDATE_OFFLINE\fR
+(0x01) is set, no attempt is made to update the copies of the user record and blob directory that are embedded into the home directory\&. Changes will be stored, however, and may be propagated into the home directory the next time it is reconciled (most likely when the user next logs in)\&. Note that any changes made with this flag set may be lost if the home area has a newer record, which can happen if the home area is updated on another machine after this method call\&. This method is equivalent to
+\fBUpdateEx()\fR
+on the
+org\&.freedesktop\&.home1\&.Home
+interface\&.
+.PP
 \fBResizeHome()\fR
-resizes the storage associated with a user record\&. Takes a user name, a disk size in bytes and a user record consisting only of the
+resizes the storage associated with a user record\&. Takes a user name, a disk size in bytes, and optionally a user record consisting only of the
 "secret"
-section as argument\&. If the size is specified as
+section as arguments\&. If the size is specified as
 \fBUINT64_MAX\fR
 the storage is resized to the size already specified in the user record\&. Typically, if the user record is updated using
 \fBUpdateHome()\fR
@@ -306,7 +371,7 @@ org\&.freedesktop\&.home1\&.Home
 interface\&.
 .PP
 \fBLockHome()\fR
-temporarily suspends access to a home directory, flushing out any cryptographic keys from memory\&. This is only supported on some back\-ends, and usually done during system suspend, in order to effectively secure home directories while the system is sleeping\&. Takes a user name as single argument\&. If an application attempts to access a home directory while it is locked it will typically freeze until the home directory is unlocked again\&. This method is equivalent to
+temporarily suspends access to a home directory, flushing out any cryptographic keys from memory\&. This is only supported on some back\-ends, and is usually done during system suspend, in order to effectively secure home directories while the system is sleeping\&. Takes a user name as single argument\&. If an application attempts to access a home directory while it is locked it will typically freeze until the home directory is unlocked again\&. This method is equivalent to
 \fBLock()\fR
 on the
 org\&.freedesktop\&.home1\&.Home
@@ -342,6 +407,12 @@ on the
 org\&.freedesktop\&.home1\&.Home
 interface\&.
 .PP
+\fBRefHomeUnrestricted()\fR
+is identical to
+\fBRefHome()\fR
+but succeeds even if the home area is not active currently\&. This is useful on conjunction with
+\fBActivateHomeIfReferenced()\fR\&.
+.PP
 \fBReleaseHome()\fR
 releases a home directory again, if all file descriptors referencing it are already closed, that where acquired through
 \fBAcquireHome()\fR
@@ -375,8 +446,8 @@ field set are listed here, with the seat name they are associated with\&. A disp
 node /org/freedesktop/home1/home {
   interface org\&.freedesktop\&.home1\&.Home {
     methods:
-      @org\&.freedesktop\&.systemd1\&.Privileged("true")
       Activate(in  s secret);
+      ActivateIfReferenced(in  s secret);
       @org\&.freedesktop\&.systemd1\&.Privileged("true")
       Deactivate();
       Unregister();
@@ -386,6 +457,9 @@ node /org/freedesktop/home1/home {
       Fixate(in  s secret);
       Authenticate(in  s secret);
       Update(in  s user_record);
+      UpdateEx(in  s user_record,
+               in  a{sh} blobs,
+               in  t flags);
       Resize(in  t size,
              in  s secret);
       ChangePassword(in  s new_secret,
@@ -402,6 +476,9 @@ node /org/freedesktop/home1/home {
       Ref(in  b please_suspend,
           out h send_fd);
       @org\&.freedesktop\&.systemd1\&.Privileged("true")
+      RefUnrestricted(in  b please_suspend,
+                      out h send_fd);
+      @org\&.freedesktop\&.systemd1\&.Privileged("true")
       Release();
     properties:
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
@@ -446,9 +523,13 @@ node /org/freedesktop/home1/home {
 
 
 
+
+
+
 .SS "Methods"
 .PP
 \fBActivate()\fR,
+\fBActivateIfReferenced()\fR,
 \fBDeactivate()\fR,
 \fBUnregister()\fR,
 \fBRealize()\fR,
@@ -456,16 +537,17 @@ node /org/freedesktop/home1/home {
 \fBFixate()\fR,
 \fBAuthenticate()\fR,
 \fBUpdate()\fR,
+\fBUpdateEx()\fR,
 \fBResize()\fR,
 \fBChangePassword()\fR,
 \fBLock()\fR,
 \fBUnlock()\fR,
 \fBAcquire()\fR,
 \fBRef()\fR,
-\fBRelease()\fR
-operate like their matching counterparts on the
+\fBRefUnrestricted()\fR,
+\fBRelease()\fR, operate like their matching counterparts on the
 org\&.freedesktop\&.home1\&.Manager
-interface (see above)\&. The main difference is that they are methods of the home directory objects, and hence carry no additional user name parameter\&. Which of the two flavors of methods to call depends on the handles to the user known on the client side: if only the user name is known, it\*(Aqs preferable to use the methods on the manager object since they operate with user names only\&. If however the home object path was already acquired some way it is preferable to operate on the
+interface (see above)\&. The main difference is that they are methods of the home directory objects, and hence carry no additional user name parameter\&. Which of the two flavors of methods to call depends on the handles to the user known on the client side: if only the user name is known, it\*(Aqs preferable to use the methods on the manager object since they operate with user names only\&. Clients can also easily operate on their own home area by using the methods on the manager object with an empty string as the user name\&. If the client has the home\*(Aqs object path already acquired in some way, however, it is preferable to operate on the
 org\&.freedesktop\&.home1\&.Home
 objects instead\&.
 .SS "Properties"
@@ -489,12 +571,24 @@ contains the full JSON user record string of the user account\&.
 .SH "VERSIONING"
 .PP
 These D\-Bus interfaces follow
-\m[blue]\fBthe usual interface versioning guidelines\fR\m[]\&\s-2\u[2]\d\s+2\&.
+\m[blue]\fBthe usual interface versioning guidelines\fR\m[]\&\s-2\u[3]\d\s+2\&.
+.SH "HISTORY"
+.SS "The Manager Object"
+.PP
+\fBActivateHomeIfReferenced()\fR,
+\fBRefHomeUnrestricted()\fR,
+\fBCreateHomeEx()\fR, and
+\fBUpdateHomeEx()\fR
+were added in version 256\&.
+.SS "Home Objects"
+.PP
+\fBActivateIfReferenced()\fR,
+\fBRefUnrestricted()\fR, and
+\fBUpdateEx()\fR
+were added in version 256\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-homed.service\fR(8),
-\fBhomectl\fR(1)
+\fBsystemd\fR(1), \fBsystemd-homed.service\fR(8), \fBhomectl\fR(1)
 .SH "NOTES"
 .IP " 1." 4
 JSON User Records
@@ -502,6 +596,11 @@ JSON User Records
 \%https://systemd.io/USER_RECORD
 .RE
 .IP " 2." 4
+User Record Blob Directories
+.RS 4
+\%https://systemd.io/USER_RECORD_BLOB_DIRS
+.RE
+.IP " 3." 4
 the usual interface versioning guidelines
 .RS 4
 \%https://0pointer.de/blog/projects/versioning-dbus.html
diff --git a/upstream/fedora-rawhide/man5/org.freedesktop.hostname1.5 b/upstream/fedora-rawhide/man5/org.freedesktop.hostname1.5
index b0d8da1f..fb7782bc 100644
--- a/upstream/fedora-rawhide/man5/org.freedesktop.hostname1.5
+++ b/upstream/fedora-rawhide/man5/org.freedesktop.hostname1.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "ORG\&.FREEDESKTOP\&.HOSTNAME1" "5" "" "systemd 255" "org.freedesktop.hostname1"
+.TH "ORG\&.FREEDESKTOP\&.HOSTNAME1" "5" "" "systemd 256~rc3" "org.freedesktop.hostname1"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -93,6 +93,8 @@ node /org/freedesktop/hostname1 {
       readonly ay MachineID = [\&.\&.\&.];
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly ay BootID = [\&.\&.\&.];
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
+      readonly u VSockCID = \&.\&.\&.;
   };
   interface org\&.freedesktop\&.DBus\&.Peer { \&.\&.\&. };
   interface org\&.freedesktop\&.DBus\&.Introspectable { \&.\&.\&. };
@@ -138,6 +140,7 @@ node /org/freedesktop/hostname1 {
 
 
 
+
 .PP
 Whenever the hostname or other metadata is changed via the daemon,
 \fBPropertyChanged\fR
@@ -260,6 +263,42 @@ and
 \fIHOME_URL=\fR
 fields from
 \fBos-release\fR(5)\&. The purpose of those properties is to allow remote clients to access this information over D\-Bus\&. Local clients can access the information directly\&.
+.PP
+\fIMachineID\fR
+expose the 128bit machine ID, see
+\fBmachine-id\fR(5)
+for details\&.
+.PP
+\fIBootID\fR
+expose the 128bit boot ID, as per
+/proc/sys/kernel/random/boot_id\&.
+.PP
+\fIVSockCID\fR
+exposes the system\*(Aqs local
+\fBAF_VSOCK\fR
+CID (Context Identifier, i\&.e\&. address) for the system, if one is available in the virtual machine environment\&. Set to
+\fBUINT32_MAX\fR
+otherwise\&. See
+\fBvsock\fR(7)
+for details\&.
+.PP
+\fIOperatingSystemSupportEnd\fR
+exposes when the OS\*(Aq vendor support ends, if this information is known\&. It\*(Aqs an unsigned 64bit value, in \(mcs since the UNIX epoch, UTC\&. If this information is not known carries the value 2^64\-1, i\&.e\&.
+\fBUINT64_MAX\fR\&.
+.PP
+\fIHardwareVendor\fR
+and
+\fIHardwareModel\fR
+expose information about the vendor of the hardware of the system\&. If no such information can be determined these properties are set to empty strings\&.
+.PP
+\fIFirmwareVersion\fR
+and
+\fIFirmwareVendor\fR
+expose information about the system\*(Aqs firmware, i\&.e\&. a version string and a vendor name\&. If no such information can be determined these properties are set to empty strings\&.
+.PP
+\fIFirmwareDate\fR
+exposes the firmware build date, if that information is known\&. It\*(Aqs an unsigned 64bit value, in \(mcs since the UNIX epoch, UTC\&. If not known
+\fBUNIT64_MAX\fR\&.
 .SS "Methods"
 .PP
 \fBSetHostname()\fR
@@ -307,6 +346,9 @@ for the semantics of those settings\&.
 returns the "product UUID" as exposed by the kernel based on DMI information in
 /sys/class/dmi/id/product_uuid\&. Reading the file directly requires root privileges, and this method allows access to unprivileged clients through the polkit framework\&.
 .PP
+\fBGetHardwareSerial()\fR
+returns the "hardware serial" as exposed by the kernel based on DMI information\&. Reading the file directly requires root privileges, and this method allows access to unprivileged clients through the polkit framework\&.
+.PP
 \fBDescribe()\fR
 returns a JSON representation of all properties in one\&.
 .SS "Security"
@@ -597,8 +639,10 @@ were added in version 251\&.
 \fIFirmwareDate\fR
 were added in version 253\&.
 .PP
-\fIMachineID\fR, and
+\fIMachineID\fR,
 \fIBootID\fR
+and
+\fIVSockCID\fR
 were added in version 256\&.
 .SH "NOTES"
 .IP " 1." 4
diff --git a/upstream/fedora-rawhide/man5/org.freedesktop.import1.5 b/upstream/fedora-rawhide/man5/org.freedesktop.import1.5
index cbea124e..19745bde 100644
--- a/upstream/fedora-rawhide/man5/org.freedesktop.import1.5
+++ b/upstream/fedora-rawhide/man5/org.freedesktop.import1.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "ORG\&.FREEDESKTOP\&.IMPORT1" "5" "" "systemd 255" "org.freedesktop.import1"
+.TH "ORG\&.FREEDESKTOP\&.IMPORT1" "5" "" "systemd 256~rc3" "org.freedesktop.import1"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -24,11 +24,11 @@ org.freedesktop.import1 \- The D\-Bus interface of systemd\-importd
 .SH "INTRODUCTION"
 .PP
 \fBsystemd-importd.service\fR(8)
-is a system service which may be used to import, export and download additional system images\&. These images can be used by tools such as
+is a system service which may be used to import, export and download disk images\&. These images can be used by tools such as
 \fBsystemd-nspawn\fR(1)
 to run local containers\&. The service is used as the backend for
-\fBmachinectl pull\-raw\fR,
-\fBmachinectl pull\-tar\fR
+\fBimportctl pull\-raw\fR,
+\fBimportctl pull\-tar\fR
 and related commands\&. This page describes the D\-Bus interface\&.
 .PP
 Note that
@@ -55,42 +55,94 @@ node /org/freedesktop/import1 {
                 in  b read_only,
                 out u transfer_id,
                 out o transfer_path);
+      ImportTarEx(in  h fd,
+                  in  s local_name,
+                  in  s class,
+                  in  t flags,
+                  out u transfer_id,
+                  out o transfer_path);
       ImportRaw(in  h fd,
                 in  s local_name,
                 in  b force,
                 in  b read_only,
                 out u transfer_id,
                 out o transfer_path);
+      ImportRawEx(in  h fd,
+                  in  s local_name,
+                  in  s class,
+                  in  t flags,
+                  out u transfer_id,
+                  out o transfer_path);
       ImportFileSystem(in  h fd,
                        in  s local_name,
                        in  b force,
                        in  b read_only,
                        out u transfer_id,
                        out o transfer_path);
+      ImportFileSystemEx(in  h fd,
+                         in  s local_name,
+                         in  s class,
+                         in  t flags,
+                         out u transfer_id,
+                         out o transfer_path);
       ExportTar(in  s local_name,
                 in  h fd,
                 in  s format,
                 out u transfer_id,
                 out o transfer_path);
+      ExportTarEx(in  s local_name,
+                  in  s class,
+                  in  h fd,
+                  in  s format,
+                  in  t flags,
+                  out u transfer_id,
+                  out o transfer_path);
       ExportRaw(in  s local_name,
                 in  h fd,
                 in  s format,
                 out u transfer_id,
                 out o transfer_path);
+      ExportRawEx(in  s local_name,
+                  in  s class,
+                  in  h fd,
+                  in  s format,
+                  in  t flags,
+                  out u transfer_id,
+                  out o transfer_path);
       PullTar(in  s url,
               in  s local_name,
               in  s verify_mode,
               in  b force,
               out u transfer_id,
               out o transfer_path);
+      PullTarEx(in  s url,
+                in  s local_name,
+                in  s class,
+                in  s verify_mode,
+                in  t flags,
+                out u transfer_id,
+                out o transfer_path);
       PullRaw(in  s url,
               in  s local_name,
               in  s verify_mode,
               in  b force,
               out u transfer_id,
               out o transfer_path);
+      PullRawEx(in  s url,
+                in  s local_name,
+                in  s class,
+                in  s verify_mode,
+                in  t flags,
+                out u transfer_id,
+                out o transfer_path);
       ListTransfers(out a(usssdo) transfers);
+      ListTransfersEx(in  s class,
+                      in  t flags,
+                      out a(ussssdo) transfers);
       CancelTransfer(in  u transfer_id);
+      ListImages(in  s class,
+                 in  t flags,
+                 out a(ssssbtttttt) images);
     signals:
       TransferNew(u transfer_id,
                   o transfer_path);
@@ -119,68 +171,86 @@ node /org/freedesktop/import1 {
 
 
 
+
+
+
+
+
+
+
+
+
 .SS "Methods"
 .PP
-\fBImportTar()\fR
+\fBImportTar()\fR/\fBImportTarEx()\fR
 and
-\fBImportRaw()\fR
-import a system image and place it into
-/var/lib/machines/\&. The first argument should be a file descriptor (opened for reading) referring to the tar or raw file to import\&. It should reference a file on disk, a pipe or a socket\&. When
-\fBImportTar()\fR
+\fBImportRaw()\fR/\fBImportRawEx()\fR
+import a disk image and place it into the image directory\&. The first argument should be a file descriptor (opened for reading) referring to the tar or raw file to import\&. It should reference a file on disk, a pipe or a socket\&. When
+\fBImportTar()\fR/\fBImportTarEx()\fR
 is used the file descriptor should refer to a tar file, optionally compressed with
 \fBgzip\fR(1),
 \fBbzip2\fR(1), or
 \fBxz\fR(1)\&.
 \fBsystemd\-importd\fR
 will detect the used compression scheme (if any) automatically\&. When
-\fBImportRaw()\fR
+\fBImportRaw()\fR/\fBImportRawEx()\fR
 is used the file descriptor should refer to a raw or qcow2 disk image containing an MBR or GPT disk label, also optionally compressed with gzip, bzip2 or xz\&. In either case, if the file is specified as a file descriptor on disk, progress information is generated for the import operation (as in that case we know the total size on disk)\&. If a socket or pipe is specified, progress information is not available\&. The file descriptor argument is followed by a local name for the image\&. This should be a name suitable as a hostname and will be used to name the imported image below
 /var/lib/machines/\&. A tar import is placed as a directory tree or a
 \fBbtrfs\fR(8)
-subvolume below
-/var/lib/machines/
-under the specified name with no suffix appended\&. A raw import is placed as a file in
-/var/lib/machines/
-with the
+subvolume below the image directory under the specified name with no suffix appended\&. A raw import is placed as a file in the image directory with the
 \&.raw
-suffix appended\&. If the
+suffix appended\&. In case of
+\fBImportTar()\fR/\fBImportRaw()\fR, if the
 \fBforce\fR
-argument is true, any pre\-existing image with the same name is removed before starting the operation\&. Otherwise, the operation fails if an image with the same name already exists\&. Finally, the
+argument is true, any pre\-existing image with the same name is removed before starting the operation\&. Otherwise, the operation fails if an image with the same name already exists\&. The
 \fBread_only\fR
-argument controls whether to create a writable or read\-only image\&. Both methods return immediately after starting the import, with the import transfer ongoing\&. They return a pair of transfer identifier and object path, which may be used to retrieve progress information about the transfer or to cancel it\&. The transfer identifier is a simple numeric identifier, the object path references an
+argument controls whether to create a writable or read\-only image\&. In case of
+\fBImportTarEx()\fR/\fBImportRawEx()\fR
+these boolean flags are provided via a 64bit flags parameter instead, with bit 0 mapping to the
+\fBforce\fR
+parameter, and bit 1 mapping to
+\fBread_only\fR\&. The
+\fBclass\fR
+parameter specifies the image class, and takes one of
+"machine",
+"portable",
+"sysext",
+"confext"\&. All four methods return immediately after starting the import, with the import transfer ongoing\&. They return a pair of transfer identifier and object path, which may be used to retrieve progress information about the transfer or to cancel it\&. The transfer identifier is a simple numeric identifier, the object path references an
 org\&.freedesktop\&.import1\&.Transfer
 object, see below\&. Listen for a
-\fBTransferRemoved\fR
+\fBTransferRemoved()\fR
 signal for the transfer ID in order to detect when a transfer is complete\&. The returned transfer object is useful to determine the current progress or log output of the ongoing import operation\&.
 .PP
-\fBExportTar()\fR
+\fBExportTar()\fR/\fBExportTarEx()\fR
 and
-\fBExportRaw()\fR
+\fBExportRaw()\fR/\fBExportRaw()\fR
 implement the reverse operation, and may be used to export a system image in order to place it in a tar or raw image\&. They take the machine name to export as their first parameter, followed by a file descriptor (opened for writing) where the tar or raw file will be written\&. It may either reference a file on disk or a pipe/socket\&. The third argument specifies in which compression format to write the image\&. It takes one of
 "uncompressed",
 "xz",
 "bzip2"
 or
 "gzip", depending on which compression scheme is required\&. The image written to the specified file descriptor will be a tar file in case of
-\fBExportTar()\fR
+\fBExportTar()\fR/\fBExportTarEx()\fR
 or a raw disk image in case of
-\fBExportRaw()\fR\&. Note that currently raw disk images may not be exported as tar files, and vice versa\&. This restriction might be lifted eventually\&. The method returns a transfer identifier and object path for cancelling or tracking the export operation, similarly to
-\fBImportTar()\fR
+\fBExportRaw()\fR/\fBExportRawEx()\fR\&. Note that currently raw disk images may not be exported as tar files, and vice versa\&. This restriction might be lifted eventually\&. The method returns a transfer identifier and object path for cancelling or tracking the export operation, similarly to
+\fBImportTar()\fR/\fBImportTarEx()\fR
 or
-\fBImportRaw()\fR
+\fBImportRaw()\fR/\fBImportRawEx()\fR
 as described above\&.
+\fBExportTarEx()\fR/\fBExportRawEx()\fR
+expect the image class as additional parameter, as well as a 64bit flags parameter that currently must be specified as zero\&.
 .PP
-\fBPullTar()\fR
+\fBPullTar()\fR/\fBPullTarEx()\fR
 and
-\fBPullRaw()\fR
+\fBPullRaw()\fR/\fBPullRawEx()\fR
 may be used to download, verify and import a system image from a URL\&. They take a URL argument which should point to a tar or raw file on the
 "http://"
 or
 "https://"
 protocols, possibly compressed with xz, bzip2 or gzip\&. The second argument is a local name for the image\&. It should be suitable as a hostname, similarly to the matching argument of the
-\fBImportTar()\fR
+\fBImportTar()\fR/\fBImportTarEx()\fR
 and
-\fBImportRaw()\fR
+\fBImportRaw()\fR/\fBImportRawEx()\fR
 methods above\&. The third argument indicates the verification mode for the image\&. It may be one of
 "no",
 "checksum",
@@ -196,30 +266,55 @@ does the same but also tries to authenticate the
 SHA256SUM
 file via
 \fBgpg\fR(8)
-first\&. The last argument indicates whether to replace a possibly pre\-existing image with the same local name (if
+first\&. In case of
+\fBPullTar()\fR/\fBPullRaw()\fR
+the last argument indicates whether to replace a possibly pre\-existing image with the same local name (if
 "true"), or whether to fail (if
-"false")\&. Like the import and export calls above, these calls return a pair of transfer identifier and object path for the ongoing download\&.
+"false")\&. In case of
+\fBPullTarEx()\fR/\fBPullRawEx()\fR
+the last argument is a 64bit flags parameter, where bit 0 controls the
+"force"
+flag, bit 1 is a
+"read_only"
+flag that controls whether the created image shall be marked read\-only, and bit 2 is a
+"keep_download"
+flag that indicates whether a pristine, read\-only copy of the downloaded image shell be kept, in addition for the local copy of the image\&. The
+\fB\&..._Ex()\fR
+variants also expect an image class string (as above)\&. Like the import and export calls above, these calls return a pair of transfer identifier and object path for the ongoing download\&.
+.PP
+\fBImportFileSystem()\fR/\fBImportFileSystemEx()\fR
+are similar to
+\fBImportTar()\fR/\fBImportTarEx()\fR
+but import a directory tree\&. The first argument must refer to a directory file descriptor for the source hierarchy to import\&.
 .PP
-\fBListTransfers()\fR
-returns a list of ongoing import, export or download operations as created with the six calls described above\&. It returns an array of structures which consist of the numeric transfer identifier, a string indicating the operation (one of
+\fBListTransfers()\fR/\fBListTransfersEx()\fR
+return a list of ongoing import, export or download operations as created with the six calls described above\&. They return an array of structures which consist of the numeric transfer identifier, a string indicating the operation (one of
 "import\-tar",
 "import\-raw",
 "export\-tar",
 "export\-raw",
 "pull\-tar"
 or
-"pull\-raw"), a string describing the remote file (in case of download operations this is the source URL, in case of import/export operations this is a short string describing the file descriptor passed in), a string with the local machine image name, a progress value between 0\&.0 (for 0%) and 1\&.0 (for 100%), as well as the transfer object path\&.
+"pull\-raw"), a string describing the remote file (in case of download operations this is the source URL, in case of import/export operations this is a short string describing the file descriptor passed in), a string with the local machine image name, the image class (only in case of
+\fBListTransfersEx()\fR; one of
+"machine",
+"portable",
+"sysext",
+"confext"), a progress value between 0\&.0 (for 0%) and 1\&.0 (for 100%), as well as the transfer object path\&.
 .PP
 \fBCancelTransfer()\fR
 may be used to cancel an ongoing import, export or download operation\&. Simply specify the transfer identifier to cancel the ongoing operation\&.
+.PP
+\fBListImages()\fR
+returns a list of currently installed images\&. It takes a image class string and a flags parameter\&. The image class is either the empty string or specifies one of the four image classes, by which it will then filter\&. The flags parameter must be zero at this time\&. It returns an array of items, each describing one image\&. The item fields are in order: the image class, the local image name, the image type, the image path, the read\-only flag, the creation and modification times (in microseconds since the UNIX epoch), as well as the current disk usage in bytes (both overall, and exclusive), as well as any size limit in bytes set on the image (both overall and exclusive)\&.
 .SS "Signals"
 .PP
 The
-\fBTransferNew\fR
+\fBTransferNew()\fR
 signal is generated each time a new transfer is started with the import, export or download calls described above\&. It carries the transfer ID and object path that have just been created\&.
 .PP
 The
-\fBTransferRemoved\fR
+\fBTransferRemoved()\fR
 signal is sent each time a transfer finishes, is canceled or fails\&. It also carries the transfer ID and object path, followed by a string indicating the result of the operation, which is one of
 "done"
 (on success),
@@ -239,6 +334,7 @@ node /org/freedesktop/import1/transfer/_1 {
     signals:
       LogMessage(u priority,
                  s line);
+      ProgressUpdate(d progress);
     properties:
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly u Id = \&.\&.\&.;
@@ -271,6 +367,7 @@ node /org/freedesktop/import1/transfer/_1 {
 
 
 
+
 .SS "Methods"
 .PP
 The
@@ -304,6 +401,15 @@ property exposes the selected verification setting and is only defined for downl
 The
 \fIProgress\fR
 property exposes the current progress of the transfer as a value between 0\&.0 and 1\&.0\&. To show a progress bar on screen we recommend to query this value in regular intervals, for example every 500\ \&ms or so\&.
+.SS "Signals"
+.PP
+The
+\fBLogMessage()\fR
+signal is emitted for log messages generated by a transfer\&. It carries a pair of syslog log level integer and log string\&.
+.PP
+The
+\fBProgressUpdate()\fR
+signal is emitted in regular intervals when new download progress information is available for a transfer\&. It carries a double precision floating pointer number between 0\&.0 and 1\&.0 indicating the transfer progress\&.
 .SH "EXAMPLES"
 .PP
 \fBExample\ \&1.\ \&Introspect org\&.freedesktop\&.import1\&.Manager on the bus\fR
@@ -339,6 +445,23 @@ $ gdbus introspect \-\-system \e
 .PP
 These D\-Bus interfaces follow
 \m[blue]\fBthe usual interface versioning guidelines\fR\m[]\&\s-2\u[1]\d\s+2\&.
+.SH "HISTORY"
+.SS "The Manager Object"
+.PP
+\fBImportTarEx()\fR,
+\fBImportRawEx()\fR,
+\fBImportFileSystemEx()\fR,
+\fBExportTarEx()\fR,
+\fBExportRawEx()\fR,
+\fBPullTarEx()\fR,
+\fBPullRawEx()\fR,
+\fBListTransfersEx()\fR,
+\fBListImages()\fR
+were added in version 256\&.
+.SS "Transfer Objects"
+.PP
+\fBProgressUpdate()\fR
+was added in version 256\&.
 .SH "NOTES"
 .IP " 1." 4
 the usual interface versioning guidelines
diff --git a/upstream/fedora-rawhide/man5/org.freedesktop.locale1.5 b/upstream/fedora-rawhide/man5/org.freedesktop.locale1.5
index 4644366b..790618ee 100644
--- a/upstream/fedora-rawhide/man5/org.freedesktop.locale1.5
+++ b/upstream/fedora-rawhide/man5/org.freedesktop.locale1.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "ORG\&.FREEDESKTOP\&.LOCALE1" "5" "" "systemd 255" "org.freedesktop.locale1"
+.TH "ORG\&.FREEDESKTOP\&.LOCALE1" "5" "" "systemd 256~rc3" "org.freedesktop.locale1"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
diff --git a/upstream/fedora-rawhide/man5/org.freedesktop.login1.5 b/upstream/fedora-rawhide/man5/org.freedesktop.login1.5
index 135cb69b..fc4cda5b 100644
--- a/upstream/fedora-rawhide/man5/org.freedesktop.login1.5
+++ b/upstream/fedora-rawhide/man5/org.freedesktop.login1.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "ORG\&.FREEDESKTOP\&.LOGIN1" "5" "" "systemd 255" "org.freedesktop.login1"
+.TH "ORG\&.FREEDESKTOP\&.LOGIN1" "5" "" "systemd 256~rc3" "org.freedesktop.login1"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -50,6 +50,7 @@ node /org/freedesktop/login1 {
       GetSeat(in  s seat_id,
               out o object_path);
       ListSessions(out a(susso) sessions);
+      ListSessionsEx(out a(sussussbto) sessions);
       ListUsers(out a(uso) users);
       ListSeats(out a(so) seats);
       ListInhibitors(out a(ssssuu) inhibitors);
@@ -100,7 +101,6 @@ node /org/freedesktop/login1 {
                              out s seat_id,
                              out u vtnr,
                              out b existing);
-      @org\&.freedesktop\&.systemd1\&.Privileged("true")
       ReleaseSession(in  s session_id);
       ActivateSession(in  s session_id);
       ActivateSessionOnSeat(in  s session_id,
@@ -138,6 +138,7 @@ node /org/freedesktop/login1 {
       HybridSleepWithFlags(in  t flags);
       SuspendThenHibernate(in  b interactive);
       SuspendThenHibernateWithFlags(in  t flags);
+      Sleep(in  t flags);
       CanPowerOff(out s result);
       CanReboot(out s result);
       CanHalt(out s result);
@@ -145,6 +146,7 @@ node /org/freedesktop/login1 {
       CanHibernate(out s result);
       CanHybridSleep(out s result);
       CanSuspendThenHibernate(out s result);
+      CanSleep(out s result);
       ScheduleShutdown(in  s type,
                        in  t usec);
       CancelScheduledShutdown(out b cancelled);
@@ -215,6 +217,8 @@ node /org/freedesktop/login1 {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly t UserStopDelayUSec = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
+      readonly as SleepOperation = [\*(Aq\&.\&.\&.\*(Aq, \&.\&.\&.];
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly s HandlePowerKey = \*(Aq\&.\&.\&.\*(Aq;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly s HandlePowerKeyLongPress = \*(Aq\&.\&.\&.\*(Aq;
@@ -394,6 +398,10 @@ node /org/freedesktop/login1 {
 
 
 
+
+
+
+
 .SS "Methods"
 .PP
 \fBGetSession()\fR
@@ -408,7 +416,30 @@ and
 get the session/user object the specified PID belongs to if there is any\&.
 .PP
 \fBListSessions()\fR
-returns an array of all current sessions\&. The structures in the array consist of the following fields: session id, user id, user name, seat id, session object path\&. If a session does not have a seat attached, the seat id field will be an empty string\&.
+returns an array of all current sessions\&. The structures in the array consist of the following fields:
+\fIsession id\fR,
+\fIuser id\fR,
+\fIuser name\fR,
+\fIseat id\fR, and
+\fIsession object path\fR\&. If a session does not have a seat attached, the seat id field will be an empty string\&.
+.PP
+\fBListSessionsEx()\fR
+returns an array of all current sessions with more metadata than
+\fBListSessions()\fR\&. The structures in the array consist of the following fields:
+\fIsession id\fR,
+\fIuser id\fR,
+\fIuser name\fR,
+\fIseat id\fR,
+\fIleader pid\fR,
+\fIsession class\fR,
+\fItty name\fR,
+\fIidle hint\fR,
+\fIidle hint monotonic timestamp\fR, and
+\fIsession object path\fR\&.
+\fItty\fR
+and
+\fIseat id\fR
+fields could be empty, if the session has no associated tty or session has no seat attached, respectively\&.
 .PP
 \fBListUsers()\fR
 returns an array of all currently logged in users\&. The structures in the array consist of the following fields: user id, user name, user object path\&.
@@ -501,16 +532,21 @@ results in the system entering a hybrid\-sleep mode, i\&.e\&. the system is both
 \fBSuspendThenHibernate()\fR
 results in the system being suspended, then later woken using an RTC timer and hibernated\&. The only argument is the polkit interactivity boolean
 \fIinteractive\fR
-(see below)\&. The main purpose of these calls is that they enforce polkit policy and hence allow powering off/rebooting/suspending/hibernating even by unprivileged users\&. They also enforce inhibition locks for non\-privileged users\&. UIs should expose these calls as the primary mechanism to poweroff/reboot/suspend/hibernate the machine\&. Methods
+(see below)\&. The main purpose of these calls is that they enforce polkit policy and hence allow powering off/rebooting/suspending/hibernating even by unprivileged users\&. They also enforce inhibition locks for non\-privileged users\&.
+\fBSleep()\fR
+automatically selects the most suitable sleep operation supported by the machine\&. The candidate sleep operations to check for support can be configured through
+\fISleepOperation=\fR
+setting in
+\fBlogind.conf\fR(5)\&. UIs should expose these calls as the primary mechanism to poweroff/reboot/suspend/hibernate the machine\&. Methods
 \fBPowerOffWithFlags()\fR,
 \fBRebootWithFlags()\fR,
 \fBHaltWithFlags()\fR,
 \fBSuspendWithFlags()\fR,
 \fBHibernateWithFlags()\fR,
-\fBHybridSleepWithFlags()\fR
-and
-\fBSuspendThenHibernateWithFlags()\fR
-add
+\fBHybridSleepWithFlags()\fR,
+\fBSuspendThenHibernateWithFlags()\fR, and
+\fBSleep()\fR
+take
 \fIflags\fR
 to allow for extendability, defined as follows:
 .sp
@@ -572,6 +608,7 @@ for the corresponding command line interface\&.
 \fBCanHibernate()\fR,
 \fBCanHybridSleep()\fR,
 \fBCanSuspendThenHibernate()\fR,
+\fBCanSleep()\fR,
 \fBCanRebootParameter()\fR,
 \fBCanRebootToFirmwareSetup()\fR,
 \fBCanRebootToBootLoaderMenu()\fR, and
@@ -653,18 +690,18 @@ Whenever the inhibition state or idle hint changes,
 signals are sent out to which clients can subscribe\&.
 .PP
 The
-\fBSessionNew\fR,
-\fBSessionRemoved\fR,
-\fBUserNew\fR,
-\fBUserRemoved\fR,
-\fBSeatNew\fR, and
-\fBSeatRemoved\fR
+\fBSessionNew()\fR,
+\fBSessionRemoved()\fR,
+\fBUserNew()\fR,
+\fBUserRemoved()\fR,
+\fBSeatNew()\fR, and
+\fBSeatRemoved()\fR
 signals are sent each time a session is created or removed, a user logs in or out, or a seat is added or removed\&. They each contain the ID of the object plus the object path\&.
 .PP
 The
-\fBPrepareForShutdown\fR,
-\fBPrepareForShutdownWithMetadata\fR, and
-\fBPrepareForSleep\fR
+\fBPrepareForShutdown()\fR,
+\fBPrepareForShutdownWithMetadata()\fR, and
+\fBPrepareForSleep()\fR
 signals are sent right before (with the argument
 "true") or after (with the argument
 "false") the system goes down for reboot/poweroff and suspend/hibernate, respectively\&. This may be used by applications to save data on disk, release memory, or do other jobs that should be done shortly before shutdown/sleep, in conjunction with delay inhibitor locks\&. After completion of this work they should release their inhibition locks in order to not delay the operation any further\&. For more information see
@@ -679,7 +716,7 @@ string which defines the type of shutdown\&. The type can be one of
 "kexec"
 or
 "soft\-reboot"\&. This signal is sent first, followed by
-\fBPrepareForShutdown\fR
+\fBPrepareForShutdown()\fR
 (for backward compatibility)\&.
 .SS "Properties"
 .PP
@@ -746,9 +783,9 @@ The
 and
 \fIPreparingForSleep\fR
 boolean properties are true during the interval between the two
-\fBPrepareForShutdown\fR
+\fBPrepareForShutdown()\fR
 and
-\fBPrepareForSleep\fR
+\fBPrepareForSleep()\fR
 signals respectively\&. Note that these properties do not send out
 \fBPropertyChanged\fR
 signals\&.
@@ -768,9 +805,9 @@ method described above\&.
 \fIRebootToBootLoaderMenu\fR, and
 \fIRebootToBootLoaderEntry\fR
 are true when the resprective post\-reboot operation was selected with
-\fBSetRebootToFirmwareSetup\fR,
-\fBSetRebootToBootLoaderMenu\fR, or
-\fBSetRebootToBootLoaderEntry\fR\&.
+\fBSetRebootToFirmwareSetup()\fR,
+\fBSetRebootToBootLoaderMenu()\fR, or
+\fBSetRebootToBootLoaderEntry()\fR\&.
 .PP
 The
 \fIWallMessage\fR
@@ -826,23 +863,25 @@ and
 \fBSuspendThenHibernate()\fR
 use the same privileges as
 \fBHibernate()\fR\&.
+\fBSleep()\fR
+uses the inhibits of the auto\-selected sleep operation\&.
 \fBSetRebootParameter()\fR
 requires
 org\&.freedesktop\&.login1\&.set\-reboot\-parameter\&.
 .PP
-\fBSetRebootToFirmwareSetup\fR
+\fBSetRebootToFirmwareSetup()\fR
 requires
 org\&.freedesktop\&.login1\&.set\-reboot\-to\-firmware\-setup\&.
-\fBSetRebootToBootLoaderMenu\fR
+\fBSetRebootToBootLoaderMenu()\fR
 requires
 org\&.freedesktop\&.login1\&.set\-reboot\-to\-boot\-loader\-menu\&.
-\fBSetRebootToBootLoaderEntry\fR
+\fBSetRebootToBootLoaderEntry()\fR
 requires
 org\&.freedesktop\&.login1\&.set\-reboot\-to\-boot\-loader\-entry\&.
 .PP
-\fBScheduleShutdown\fR
+\fBScheduleShutdown()\fR
 and
-\fBCancelScheduledShutdown\fR
+\fBCancelScheduledShutdown()\fR
 require the same privileges (listed above) as the immediate poweroff/reboot/halt operations\&.
 .PP
 \fBInhibit()\fR
@@ -1125,6 +1164,7 @@ node /org/freedesktop/login1/session/1 {
       TakeControl(in  b force);
       ReleaseControl();
       SetType(in  s type);
+      SetClass(in  s class);
       SetDisplay(in  s display);
       SetTTY(in  h tty_fd);
       TakeDevice(in  u major,
@@ -1181,7 +1221,6 @@ node /org/freedesktop/login1/session/1 {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly u Audit = \&.\&.\&.;
       readonly s Type = \*(Aq\&.\&.\&.\*(Aq;
-      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly s Class = \*(Aq\&.\&.\&.\*(Aq;
       readonly b Active = \&.\&.\&.;
       readonly s State = \*(Aq\&.\&.\&.\*(Aq;
@@ -1245,6 +1284,7 @@ node /org/freedesktop/login1/session/1 {
 
 
 
+
 .SS "Methods"
 .PP
 \fBTerminate()\fR,
@@ -1279,6 +1319,14 @@ or closing the D\-Bus connection\&. This should help prevent a session from ente
 \fItype\fR
 is the new session type\&.
 .PP
+\fBSetClass()\fR
+allows the caller to change the class of the session dynamically\&. It may only be called by session\*(Aqs owening user\&. Currently, this call may be exclusively used to change the class from
+"user\-incomplete"
+to
+"user"\&. The call is synchronous, and will return only once the user\*(Aqs service manager has successfully been started, if necessary\&. The only argument
+\fItype\fR
+is the new session type\&.
+.PP
 \fBSetDisplay()\fR
 allows the display name of the graphical session to be changed\&. This is useful if the display server is started as part of the session\&. It can only be called by session\*(Aqs current controller\&. If
 \fBTakeControl()\fR
@@ -1339,23 +1387,23 @@ parameter specifies the brightness\&. The range is defined by individual drivers
 .SS "Signals"
 .PP
 The active session controller exclusively gets
-\fBPauseDevice\fR
+\fBPauseDevice()\fR
 and
-\fBResumeDevice\fR
+\fBResumeDevice()\fR
 events for any device it requested via
 \fBTakeDevice()\fR\&. They notify the controller whenever a device is paused or resumed\&. A device is never resumed if its session is inactive\&. Also note that
-\fBPauseDevice\fR
+\fBPauseDevice()\fR
 signals are sent before the
 \fBPropertyChanged\fR
 signal for the
 \fBActive\fR
 state\&. The inverse is true for
-\fBResumeDevice\fR\&. A device may remain paused for unknown reasons even though the
+\fBResumeDevice()\fR\&. A device may remain paused for unknown reasons even though the
 Session
 is active\&.
 .PP
 A
-\fBPauseDevice\fR
+\fBPauseDevice()\fR
 signal carries the major and minor numbers and a string describing the type as arguments\&.
 \fBforce\fR
 means the device was already paused by
@@ -1368,7 +1416,7 @@ grants you a limited amount of time to pause the device\&. You must respond to t
 \fBPauseDeviceComplete()\fR\&. This synchronous pausing mechanism is used for backwards\-compatibility to VTs and
 systemd\-logind
 is free to not make use of it\&. It is also free to send a forced
-\fBPauseDevice\fR
+\fBPauseDevice()\fR
 if you don\*(Aqt respond in a timely manner (or for any other reason)\&.
 \fBgone\fR
 means the device was unplugged from the system and you will no longer get any notifications about it\&. There is no need to call
@@ -1376,7 +1424,7 @@ means the device was unplugged from the system and you will no longer get any no
 \fBTakeDevice()\fR
 again if a new device is assigned the major+minor combination\&.
 .PP
-\fBResumeDevice\fR
+\fBResumeDevice()\fR
 is sent whenever a session is active and a device is resumed\&. It carries the major/minor numbers as arguments and provides a new open file descriptor\&. You should switch to the new descriptor and close the old one\&. They are not guaranteed to have the same underlying open file descriptor in the kernel (except for a limited set of device types)\&.
 .PP
 Whenever
@@ -1385,7 +1433,7 @@ or the idle state changes,
 \fBPropertyChanged\fR
 signals are sent out to which clients can subscribe\&.
 .PP
-\fBLock\fR/\fBUnlock\fR
+\fBLock()\fR/\fBUnlock()\fR
 is sent when the session is asked to be screen\-locked/unlocked\&. A session manager of the session should listen to this signal and act accordingly\&. This signal is sent out as a result of the
 \fBLock()\fR
 and
@@ -1615,10 +1663,16 @@ were added in version 251\&.
 \fIStopIdleSessionUSec\fR
 was added in version 252\&.
 .PP
-\fBPrepareForShutdownWithMetadata\fR
+\fBPrepareForShutdownWithMetadata()\fR
 and
 \fBCreateSessionWithPIDFD()\fR
 were added in version 255\&.
+.PP
+\fBSleep()\fR,
+\fBCanSleep()\fR,
+\fISleepOperation\fR, and
+\fBListSessionsEx()\fR
+were added in version 256\&.
 .SS "Session Objects"
 .PP
 \fBSetDisplay()\fR
@@ -1626,6 +1680,9 @@ was added in version 252\&.
 .PP
 \fBSetTTY()\fR
 was added in version 254\&.
+.PP
+\fBSetClass()\fR
+was added in version 256\&.
 .SH "NOTES"
 .IP " 1." 4
 polkit
diff --git a/upstream/fedora-rawhide/man5/org.freedesktop.machine1.5 b/upstream/fedora-rawhide/man5/org.freedesktop.machine1.5
index a63a4960..3b35991c 100644
--- a/upstream/fedora-rawhide/man5/org.freedesktop.machine1.5
+++ b/upstream/fedora-rawhide/man5/org.freedesktop.machine1.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "ORG\&.FREEDESKTOP\&.MACHINE1" "5" "" "systemd 255" "org.freedesktop.machine1"
+.TH "ORG\&.FREEDESKTOP\&.MACHINE1" "5" "" "systemd 256~rc3" "org.freedesktop.machine1"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -87,6 +87,9 @@ node /org/freedesktop/machine1 {
                   in  i signal);
       GetMachineAddresses(in  s name,
                           out a(iay) addresses);
+      GetMachineSSHInfo(in  s name,
+                        out s ssh_address,
+                        out s ssh_private_key_path);
       GetMachineOSRelease(in  s name,
                           out a{ss} fields);
       @org\&.freedesktop\&.systemd1\&.Privileged("true")
@@ -228,6 +231,7 @@ node /org/freedesktop/machine1 {
 
 
 
+
 .SS "Methods"
 .PP
 \fBGetMachine()\fR
@@ -300,6 +304,9 @@ retrieves the IP addresses of a container\&. This method returns an array of pai
 or
 \fBAF_INET6\fR) and a byte array containing the addresses\&. This is only supported for containers that make use of network namespacing\&.
 .PP
+\fBGetMachineSSHInfo()\fR
+retrieves the SSH information of a machine\&. This method returns two strings, the SSH address which can be used to tell SSH where to connect, and the path to the SSH private key required for the connection to succeed\&.
+.PP
 \fBGetMachineOSRelease()\fR
 retrieves the OS release information of a container\&. This method returns an array of key value pairs read from the
 \fBos-release\fR(5)
@@ -324,7 +331,7 @@ copies files or directories from a container into the host\&. It takes a contain
 does the opposite and copies files from a source directory on the host into a destination directory in the container\&.
 \fBCopyFromMachineWithFlags()\fR
 and
-\fBCopyToMachineWithFlags\fR
+\fBCopyToMachineWithFlags()\fR
 do the same but take an additional flags argument\&.
 .PP
 \fBRemoveImage()\fR
@@ -352,9 +359,9 @@ sets a per\-image quota limit\&.
 may be used to map UIDs/GIDs from the host user namespace to a container user namespace or vice versa\&.
 .SS "Signals"
 .PP
-\fBMachineNew\fR
+\fBMachineNew()\fR
 and
-\fBMachineRemoved\fR
+\fBMachineRemoved()\fR
 are sent whenever a new machine is registered or removed\&. These signals carry the machine name and the object path to the corresponding
 org\&.freedesktop\&.machine1\&.Machine
 interface (see below)\&.
@@ -381,6 +388,8 @@ node /org/freedesktop/machine1/machine/rawhide {
       Kill(in  s who,
            in  i signal);
       GetAddresses(out a(iay) addresses);
+      GetSSHInfo(out s ssh_address,
+                 out s ssh_private_key_path);
       GetOSRelease(out a{ss} fields);
       GetUIDShift(out u shift);
       OpenPTY(out h pty,
@@ -429,6 +438,12 @@ node /org/freedesktop/machine1/machine/rawhide {
       readonly s RootDirectory = \*(Aq\&.\&.\&.\*(Aq;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly ai NetworkInterfaces = [\&.\&.\&.];
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
+      readonly u VSockCID = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
+      readonly s SSHAddress = \*(Aq\&.\&.\&.\*(Aq;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
+      readonly s SSHPrivateKeyPath = \*(Aq\&.\&.\&.\*(Aq;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly s State = \*(Aq\&.\&.\&.\*(Aq;
   };
@@ -467,6 +482,10 @@ node /org/freedesktop/machine1/machine/rawhide {
 
 
 
+
+
+
+
 .SS "Methods"
 .PP
 \fBTerminate()\fR
@@ -478,11 +497,13 @@ and
 \fBKillMachine()\fR
 on the Manager interface, respectively\&.
 .PP
-\fBGetAddresses()\fR
+\fBGetAddresses()\fR,
+\fBGetSSHInfo()\fR
 and
 \fBGetOSRelease()\fR
-get the IP address and OS release information from the machine\&. These methods take the same arguments as
-\fBGetMachineAddresses()\fR
+get the IP address, SSH connection and OS release information from the machine\&. These methods take the same arguments as
+\fBGetMachineAddresses()\fR,
+\fBGetMachineSSHInfo()\fR
 and
 \fBGetMachineOSRelease()\fR
 of the Manager interface, respectively\&.
@@ -521,6 +542,19 @@ contains an array of network interface indices that point towards the container,
 \fBCreateMachineWithNetwork()\fR
 above\&.
 .PP
+\fIVSockCID\fR
+is the VSOCK CID of the VM if it is known, or
+\fBVMADDR_CID_ANY\fR
+otherwise\&.
+.PP
+\fISSHAddress\fR
+is the address of the VM in a format
+\fBssh\fR
+can understand if it is known or the empty string\&.
+.PP
+\fISSHPrivateKeyPath\fR
+is the path to the SSH private key of the VM if it is known or the empty string\&.
+.PP
 \fIState\fR
 is the state of the machine and is one of
 "opening",
@@ -568,12 +602,22 @@ These D\-Bus interfaces follow
 and
 \fBCopyToMachineWithFlags()\fR
 were added in version 252\&.
+.PP
+\fBGetMachineSSHInfo()\fR
+was added in version 256\&.
 .SS "Machine Objects"
 .PP
 \fBCopyFromWithFlags()\fR
 and
 \fBCopyToWithFlags()\fR
 were added in version 252\&.
+.PP
+\fBGetSSHInfo()\fR,
+\fIVSockCID\fR,
+\fISSHAddress\fR
+and
+\fISSHPrivateKeyPath\fR
+were added in version 256\&.
 .SH "NOTES"
 .IP " 1." 4
 New Control Group Interfaces
diff --git a/upstream/fedora-rawhide/man5/org.freedesktop.network1.5 b/upstream/fedora-rawhide/man5/org.freedesktop.network1.5
index 46092e21..4c227ef8 100644
--- a/upstream/fedora-rawhide/man5/org.freedesktop.network1.5
+++ b/upstream/fedora-rawhide/man5/org.freedesktop.network1.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "ORG\&.FREEDESKTOP\&.NETWORK1" "5" "" "systemd 255" "org.freedesktop.network1"
+.TH "ORG\&.FREEDESKTOP\&.NETWORK1" "5" "" "systemd 256~rc3" "org.freedesktop.network1"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -81,6 +81,8 @@ node /org/freedesktop/network1 {
       readonly s OnlineState = \*(Aq\&.\&.\&.\*(Aq;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly t NamespaceId = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly u NamespaceNSID = \&.\&.\&.;
   };
   interface org\&.freedesktop\&.DBus\&.Peer { \&.\&.\&. };
   interface org\&.freedesktop\&.DBus\&.Introspectable { \&.\&.\&. };
@@ -121,8 +123,16 @@ node /org/freedesktop/network1 {
 
 
 
+
 .PP
 Provides information about the manager\&.
+.SS "Properties"
+.PP
+\fINamespaceId\fR
+contains the inode number of the network namespace that the network service runs in\&. A client may compare this with the inode number of its own network namespace to verify whether the service manages the same network namespace\&.
+.PP
+\fINamespaceNSID\fR
+contains the "nsid" identifier the kernel maintains for the network namespace, if there\*(Aqs one assigned\&.
 .SH "LINK OBJECT"
 .sp
 .if n \{\
@@ -368,6 +378,10 @@ was added in version 255\&.
 .PP
 \fIState\fR
 was added in version 255\&.
+.SS "Manager Object"
+.PP
+\fINamespaceNSID\fR
+was added in version 256\&.
 .SH "NOTES"
 .IP " 1." 4
 the usual interface versioning guidelines
diff --git a/upstream/fedora-rawhide/man5/org.freedesktop.oom1.5 b/upstream/fedora-rawhide/man5/org.freedesktop.oom1.5
index 85840abb..a1131c84 100644
--- a/upstream/fedora-rawhide/man5/org.freedesktop.oom1.5
+++ b/upstream/fedora-rawhide/man5/org.freedesktop.oom1.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "ORG\&.FREEDESKTOP\&.OOM1" "5" "" "systemd 255" "org.freedesktop.oom1"
+.TH "ORG\&.FREEDESKTOP\&.OOM1" "5" "" "systemd 256~rc3" "org.freedesktop.oom1"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -55,7 +55,7 @@ node /org/freedesktop/oom1 {
 
 .SS "Methods"
 .PP
-\fBKilled\fR
+\fBKilled()\fR
 signal is sent when any cgroup is killed by oomd\&.
 .PP
 Note that more reasons will be added in the future, and the table below will be expanded accordingly\&.
@@ -95,7 +95,7 @@ These D\-Bus interfaces follow
 .SH "HISTORY"
 .SS "The Manager Object"
 .PP
-\fBKilled\fR
+\fBKilled()\fR
 was added in version 252\&.
 .SH "NOTES"
 .IP " 1." 4
diff --git a/upstream/fedora-rawhide/man5/org.freedesktop.portable1.5 b/upstream/fedora-rawhide/man5/org.freedesktop.portable1.5
index 5fa495f0..12d7a7cb 100644
--- a/upstream/fedora-rawhide/man5/org.freedesktop.portable1.5
+++ b/upstream/fedora-rawhide/man5/org.freedesktop.portable1.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "ORG\&.FREEDESKTOP\&.PORTABLE1" "5" "" "systemd 255" "org.freedesktop.portable1"
+.TH "ORG\&.FREEDESKTOP\&.PORTABLE1" "5" "" "systemd 256~rc3" "org.freedesktop.portable1"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -265,7 +265,7 @@ property for a list of available profiles), a boolean indicating whether to atta
 .sp -1
 .IP \(bu 2.3
 .\}
-(null)
+(empty)
 .RE
 .sp
 .RS 4
@@ -290,7 +290,24 @@ copy
 symlink
 .RE
 .sp
-This method returns the list of changes applied to the system (for example, which unit was added and is now available as a system service)\&. Each change is represented as a triplet of strings: the type of change applied, the path on which it was applied, and the source (if any)\&. The type of change applied will be one of the following possible values:
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+mixed
+.RE
+.sp
+If an empty string is passed the security profile drop\-ins and images will be symlinked while unit files will be copied,
+\fIcopy\fR
+will copy,
+\fIsymlink\fR
+will prefer linking if possible (e\&.g\&.: a unit has to be copied out of an image), and
+\fImixed\fR
+will prefer linking the resources owned by the OS (e\&.g\&.: the portable profile located within the host\*(Aqs /usr/ tree) but will copy the resources owned by the portable image (e\&.g\&.: the unit files and the images)\&. This method returns the list of changes applied to the system (for example, which unit was added and is now available as a system service)\&. Each change is represented as a triplet of strings: the type of change applied, the path on which it was applied, and the source (if any)\&. The type of change applied will be one of the following possible values:
 .sp
 .RS 4
 .ie n \{\
@@ -336,7 +353,19 @@ write
 mkdir
 .RE
 .sp
-Note that an image cannot be attached if a unit that it contains is already present on the system\&.
+Note that an image cannot be attached if a unit that it contains is already present on the system\&. Note that this method returns only after all the listed operations are completed, and due to the I/O involved it might take some time\&.
+.PP
+In place of the image path a
+"\&.v/"
+versioned directory may be specified, see
+\fBsystemd.v\fR(7)
+for details\&.
+.PP
+In place of the directory path a
+"\&.v/"
+versioned directory may be specified, see
+\fBsystemd.v\fR(7)
+for details\&.
 .PP
 \fBAttachImageWithExtensions()\fR
 attaches a portable image to the system\&. This method is a superset of
@@ -364,15 +393,13 @@ detaches a portable image from the system\&. This method takes an image path or
 unlink
 .RE
 .sp
-Note that an image cannot be detached if a unit that it contains is running\&.
+Note that an image cannot be detached if a unit that it contains is running\&. Note that this method returns only after all the listed operations are completed, and due to the I/O involved it might take some time\&.
 .PP
 \fBDetachImageWithExtensions()\fR
 detaches a portable image from the system\&. This method is a superset of
 \fBDetachImage()\fR
 with the addition of a list of extensions as input parameter, which were overlaid on top of the main image via
-\fBAttachImageWithExtensions()\fR\&. The
-\fIflag\fR
-parameter is currently unused and reserved for future purposes\&.
+\fBAttachImageWithExtensions()\fR\&.
 .PP
 \fBReattachImage()\fR
 combines the effects of the
@@ -395,9 +422,7 @@ with the addition of a list of extensions as input parameter, which will be over
 entry on
 \fBsystemd.exec\fR(5)
 and
-\fBsystemd-sysext\fR(8)\&. The
-\fIflag\fR
-parameter is currently unused and reserved for future purposes
+\fBsystemd-sysext\fR(8)\&.
 .PP
 \fBRemoveImage()\fR
 removes the image with the specified name\&.
@@ -418,11 +443,11 @@ and
 \fBReattachImageWithExtensions()\fR
 methods take in options as flags instead of booleans to allow for extendability\&.
 \fISD_SYSTEMD_PORTABLE_FORCE_ATTACH\fR
-will cause safety checks that ensure the units are not running while the new image is attached or detached to be skipped\&.
+will bypass the safety checks that ensure the units are not running while the image is attached or detached\&.
 \fISD_SYSTEMD_PORTABLE_FORCE_EXTENSION\fR
-will cause the check that the
+will bypass the check that ensures the
 extension\-release\&.\fINAME\fR
-file in the extension image matches the image name to be skipped\&. They are defined as follows:
+file in the extension image matches the image name\&. They are defined as follows:
 .sp
 .if n \{\
 .RS 4
diff --git a/upstream/fedora-rawhide/man5/org.freedesktop.resolve1.5 b/upstream/fedora-rawhide/man5/org.freedesktop.resolve1.5
index 4f3b397f..69b4a36e 100644
--- a/upstream/fedora-rawhide/man5/org.freedesktop.resolve1.5
+++ b/upstream/fedora-rawhide/man5/org.freedesktop.resolve1.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "ORG\&.FREEDESKTOP\&.RESOLVE1" "5" "" "systemd 255" "org.freedesktop.resolve1"
+.TH "ORG\&.FREEDESKTOP\&.RESOLVE1" "5" "" "systemd 256~rc3" "org.freedesktop.resolve1"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -94,7 +94,7 @@ node /org/freedesktop/resolve1 {
       SetLinkDNSSECNegativeTrustAnchors(in  i ifindex,
                                         in  as names);
       RevertLink(in  i ifindex);
-      RegisterService(in  s name,
+      RegisterService(in  s id,
                       in  s name_template,
                       in  s type,
                       in  q service_port,
@@ -420,6 +420,32 @@ set) so that all settings take effect during the full time the network interface
 The
 \fBRevertLink()\fR
 method may be used to revert all per\-link settings described above to the defaults\&.
+.PP
+The
+\fBFlushCaches()\fR
+flushes all resource record caches maintained by the resolver, and ensures that any subsequent lookups re\-request their responses from their sources\&.
+.PP
+The
+\fBResetServerFeatures()\fR
+flushes any feature information learned about remote DNS servers\&. This ensures that subsequent lookups will be initially attempted at the highest DNS protocol feature level again, possibly requiring a (potentially slow) downgrade cycle to recognize the supported feature level again\&.
+.PP
+The
+\fBRegisterService()\fR
+method may be used to register a DNS\-SD service on the host\&. This functionality is closely related to the functionality provided by
+\fBsystemd.dnssd\fR(5)
+files\&. It takes a server identifier string as first parameter (this is just a local identifier, and should be chosen so that it neither collides with the basename of
+*\&.dnssd
+files nor with names chosen by other IPC clients)\&. It also takes a name template string for the DNS\-SD service name visible on the network\&. This string is subject to specifier expansation, as documented for the
+\fIName=\fR
+setting in
+*\&.dnssd
+files\&. It also takes a service type string containing the DNS\-SD service type, as well as an IP port, a priority/weight pair for the DNS\-SD SRV record\&. Finally, it takes an array of TXT record data\&. It returns an object path which may be used as handle to the registered service\&.
+.PP
+The
+\fBUnregisterService()\fR
+method undoes the effect of
+\fBRegisterService()\fR
+and deletes a DNS\-SD service previously created via IPC again\&.
 .sp
 .it 1 an-trap
 .nr an-no-space-flag 1
@@ -436,35 +462,36 @@ The four methods above accept and return a 64\-bit flags value\&. In most cases
 .\}
 .nf
 /* Input+Output: Protocol/scope */
-#define SD_RESOLVED_DNS               (UINT64_C(1) <<  0)
-#define SD_RESOLVED_LLMNR_IPV4        (UINT64_C(1) <<  1)
-#define SD_RESOLVED_LLMNR_IPV6        (UINT64_C(1) <<  2)
-#define SD_RESOLVED_MDNS_IPV4         (UINT64_C(1) <<  3)
-#define SD_RESOLVED_MDNS_IPV6         (UINT64_C(1) <<  4)
+#define SD_RESOLVED_DNS                (UINT64_C(1) <<  0)
+#define SD_RESOLVED_LLMNR_IPV4         (UINT64_C(1) <<  1)
+#define SD_RESOLVED_LLMNR_IPV6         (UINT64_C(1) <<  2)
+#define SD_RESOLVED_MDNS_IPV4          (UINT64_C(1) <<  3)
+#define SD_RESOLVED_MDNS_IPV6          (UINT64_C(1) <<  4)
 
 /* Input: Restrictions */
-#define SD_RESOLVED_NO_CNAME          (UINT64_C(1) <<  5)
-#define SD_RESOLVED_NO_TXT            (UINT64_C(1) <<  6)
-#define SD_RESOLVED_NO_ADDRESS        (UINT64_C(1) <<  7)
-#define SD_RESOLVED_NO_SEARCH         (UINT64_C(1) <<  8)
-#define SD_RESOLVED_NO_VALIDATE       (UINT64_C(1) << 10)
-#define SD_RESOLVED_NO_SYNTHESIZE     (UINT64_C(1) << 11)
-#define SD_RESOLVED_NO_CACHE          (UINT64_C(1) << 12)
-#define SD_RESOLVED_NO_ZONE           (UINT64_C(1) << 13)
-#define SD_RESOLVED_NO_TRUST_ANCHOR   (UINT64_C(1) << 14)
-#define SD_RESOLVED_NO_NETWORK        (UINT64_C(1) << 15)
-#define SD_RESOLVED_NO_STALE          (UINT64_C(1) << 24)
+#define SD_RESOLVED_NO_CNAME           (UINT64_C(1) <<  5)
+#define SD_RESOLVED_NO_TXT             (UINT64_C(1) <<  6)
+#define SD_RESOLVED_NO_ADDRESS         (UINT64_C(1) <<  7)
+#define SD_RESOLVED_NO_SEARCH          (UINT64_C(1) <<  8)
+#define SD_RESOLVED_NO_VALIDATE        (UINT64_C(1) << 10)
+#define SD_RESOLVED_NO_SYNTHESIZE      (UINT64_C(1) << 11)
+#define SD_RESOLVED_NO_CACHE           (UINT64_C(1) << 12)
+#define SD_RESOLVED_NO_ZONE            (UINT64_C(1) << 13)
+#define SD_RESOLVED_NO_TRUST_ANCHOR    (UINT64_C(1) << 14)
+#define SD_RESOLVED_NO_NETWORK         (UINT64_C(1) << 15)
+#define SD_RESOLVED_NO_STALE           (UINT64_C(1) << 24)
+#define SD_RESOLVED_RELAX_SINGLE_LABEL (UINT64_C(1) << 25)
 
 /* Output: Security */
-#define SD_RESOLVED_AUTHENTICATED     (UINT64_C(1) <<  9)
-#define SD_RESOLVED_CONFIDENTIAL      (UINT64_C(1) << 18)
+#define SD_RESOLVED_AUTHENTICATED      (UINT64_C(1) <<  9)
+#define SD_RESOLVED_CONFIDENTIAL       (UINT64_C(1) << 18)
 
 /* Output: Origin */
-#define SD_RESOLVED_SYNTHETIC         (UINT64_C(1) << 19)
-#define SD_RESOLVED_FROM_CACHE        (UINT64_C(1) << 20)
-#define SD_RESOLVED_FROM_ZONE         (UINT64_C(1) << 21)
-#define SD_RESOLVED_FROM_TRUST_ANCHOR (UINT64_C(1) << 22)
-#define SD_RESOLVED_FROM_NETWORK      (UINT64_C(1) << 23)
+#define SD_RESOLVED_SYNTHETIC          (UINT64_C(1) << 19)
+#define SD_RESOLVED_FROM_CACHE         (UINT64_C(1) << 20)
+#define SD_RESOLVED_FROM_ZONE          (UINT64_C(1) << 21)
+#define SD_RESOLVED_FROM_TRUST_ANCHOR  (UINT64_C(1) << 22)
+#define SD_RESOLVED_FROM_NETWORK       (UINT64_C(1) << 23)
 .fi
 .if n \{\
 .RE
@@ -646,6 +673,10 @@ property reports whether the stub listener on port 53 is enabled\&. Possible val
 (only the UDP listener is enabled), and
 "tcp"
 (only the TCP listener is enabled)\&.
+.PP
+The
+\fIDNSSECNegativeTrustAnchors\fR
+property contains a list of recognized DNSSEC negative trust anchors and contains a list of domains\&.
 .SH "LINK OBJECT"
 .sp
 .if n \{\
diff --git a/upstream/fedora-rawhide/man5/org.freedesktop.systemd1.5 b/upstream/fedora-rawhide/man5/org.freedesktop.systemd1.5
index 7f3378a8..ddfee8e9 100644
--- a/upstream/fedora-rawhide/man5/org.freedesktop.systemd1.5
+++ b/upstream/fedora-rawhide/man5/org.freedesktop.systemd1.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "ORG\&.FREEDESKTOP\&.SYSTEMD1" "5" "" "systemd 255" "org.freedesktop.systemd1"
+.TH "ORG\&.FREEDESKTOP\&.SYSTEMD1" "5" "" "systemd 256~rc3" "org.freedesktop.systemd1"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -274,6 +274,11 @@ node /org/freedesktop/systemd1 {
       GetDynamicUsers(out a(us) users);
       DumpUnitFileDescriptorStore(in  s name,
                                   out a(suuutuusu) entries);
+      StartAuxiliaryScope(in  s name,
+                          in  ah pidfds,
+                          in  t flags,
+                          in  a(sv) properties,
+                          out o job);
     signals:
       UnitNew(s id,
               o unit);
@@ -332,6 +337,10 @@ node /org/freedesktop/systemd1 {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly t FinishTimestampMonotonic = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
+      readonly t ShutdownStartTimestamp = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
+      readonly t ShutdownStartTimestampMonotonic = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly t SecurityStartTimestamp = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly t SecurityStartTimestampMonotonic = \&.\&.\&.;
@@ -548,6 +557,8 @@ node /org/freedesktop/systemd1 {
       readonly i DefaultOOMScoreAdjust = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly s CtrlAltDelBurstAction = \*(Aq\&.\&.\&.\*(Aq;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
+      readonly u SoftRebootsCount = \&.\&.\&.;
   };
   interface org\&.freedesktop\&.DBus\&.Peer { \&.\&.\&. };
   interface org\&.freedesktop\&.DBus\&.Introspectable { \&.\&.\&. };
@@ -776,6 +787,10 @@ node /org/freedesktop/systemd1 {
 
 
 
+
+
+
+
 .SS "Methods"
 .PP
 Note that many of the methods exist twice: once on the
@@ -807,7 +822,13 @@ enqueues a start job and possibly depending jobs\&. It takes the unit to activat
 "fail", the method will start the unit and its dependencies, but will fail if this would change an already queued job\&. If
 "isolate", the method will start the unit in question and terminate all units that aren\*(Aqt dependencies of it\&. If
 "ignore\-dependencies", it will start a unit but ignore all its dependencies\&. If
-"ignore\-requirements", it will start a unit but only ignore the requirement dependencies\&. It is not recommended to make use of the latter two options\&. On completion, this method returns the newly created job object\&.
+"ignore\-requirements", it will start a unit but only ignore the requirement dependencies\&. It is not recommended to make use of the latter two options\&. On reply, if successful, this method returns the newly created job object which has been enqueued for asynchronous activation\&. Callers that want to track the outcome of the actual start operation need to monitor the result of this job\&. This can be achieved in a race\-free manner by first subscribing to the
+\fBJobRemoved()\fR
+signal, then calling
+\fBStartUnit()\fR
+and using the returned job object to filter out unrelated
+\fBJobRemoved()\fR
+signals, until the desired one is received, which will then carry the result of the start operation\&.
 .PP
 \fBStartUnitReplace()\fR
 is similar to
@@ -1287,6 +1308,21 @@ returns an array with information about the file descriptors currently in the fi
 \fBDumpFileDescriptorStore()\fR
 on the
 org\&.freedesktop\&.systemd1\&.Service\&. For further details, see below\&.
+.PP
+\fBStartAuxiliaryScope()\fR
+creates a new scope unit from a service where calling process resides\&. Set of processes that will be migrated to newly created scope is passed in as an array of pidfds\&. This is useful for creating auxiliary scopes that should contain worker processes and their lifecycle shouldn\*(Aqt be bound to a lifecycle of the service, e\&.g\&. they should continue running after the restart of the service\&. Note that the main PID of the service can not be migrated to an auxiliary scope\&. Also,
+\fIflags\fR
+argument must be 0 and is reserved for future extensions\&.
+.PP
+\fBCleanUnit()\fR
+deletes the configuration, state, logs, cache and runtime data directories and clear out the file descriptors store for the unit, as specified in the mask parameters\&. The possible values are
+"configuration",
+"state",
+"logs",
+"cache",
+"runtime",
+"fdstore", and
+"all"\&.
 .SS "Signals"
 .PP
 Note that most signals are sent out only after
@@ -1371,16 +1407,29 @@ are not symlinks to their counterparts under
 Added in version 252\&.
 .RE
 .PP
-"cgroups\-missing"
+"unmerged\-bin"
 .RS 4
-Support for cgroups is unavailable\&.
+/usr/sbin
+is not a symlink to
+/usr/bin/\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
+"var\-run\-bad"
+.RS 4
+/run/
+does not exist or
+/var/run
+is not a symlink to
+/run/\&.
 .sp
 Added in version 252\&.
 .RE
 .PP
 "cgroupsv1"
 .RS 4
-The system is using the old cgroup hierarchy\&.
+The system is using the deprecated cgroup v1 hierarchy\&.
 .sp
 Added in version 252\&.
 .RE
@@ -1409,17 +1458,6 @@ The system is running a kernel version that is older than the minimum supported
 Added in version 252\&.
 .RE
 .PP
-"var\-run\-bad"
-.RS 4
-/run/
-does not exist or
-/var/run
-is not a symlink to
-/run/\&.
-.sp
-Added in version 252\&.
-.RE
-.PP
 "overflowuid\-not\-65534", "overflowgid\-not\-65534"
 .RS 4
 The kernel overflow UID or GID have a value other than 65534\&.
@@ -1444,13 +1482,16 @@ Added in version 252\&.
 \fIInitRDTimestampMonotonic\fR,
 \fIUserspaceTimestamp\fR,
 \fIUserspaceTimestampMonotonic\fR,
-\fIFinishTimestamp\fR, and
-\fIFinishTimestampMonotonic\fR
+\fIFinishTimestamp\fR,
+\fIFinishTimestampMonotonic\fR,
+\fIShutdownStartTimestamp\fR
+and
+\fIShutdownStartTimestampMonotonic\fR
 encode
 \fBCLOCK_REALTIME\fR
 and
 \fBCLOCK_MONOTONIC\fR
-microsecond timestamps taken when the firmware first began execution, when the boot loader first began execution, when the kernel first began execution, when the initrd first began execution, when the main systemd instance began execution and finally, when all queued startup jobs finished execution\&. These values are useful for determining boot\-time performance\&. Note that as monotonic time begins with the kernel startup, the
+microsecond timestamps taken when the firmware first began execution, when the boot loader first began execution, when the kernel first began execution, when the initrd first began execution, when the main systemd instance began execution, when all queued startup jobs finished execution and finally, when a shutdown operation first began execution\&. These values are useful for determining boot\-time performance\&. Note that as monotonic time begins with the kernel startup, the
 \fIKernelTimestampMonotonic\fR
 timestamp will always be 0 and
 \fIFirmwareTimestampMonotonic\fR
@@ -1497,6 +1538,10 @@ encodes the environment block passed to all executed services\&. It may be alter
 \fIUnitPath\fR
 encodes the currently active unit file search path\&. It is an array of file system paths encoded as strings\&.
 .PP
+\fISoftRebootsCount\fR
+encodes how many soft\-reboots were successfully completed since the last full boot\&. Starts at
+"0"\&.
+.PP
 \fIVirtualization\fR
 contains a short ID string describing the virtualization technology the system runs in\&. On bare\-metal hardware this is the empty string\&. Otherwise, it contains an identifier such as
 "kvm",
@@ -1579,8 +1624,8 @@ org\&.freedesktop\&.systemd1\&.manage\-units\&. Operations which modify unit fil
 \fBDisableUnitFilesWithFlags()\fR,
 \fBReenableUnitFiles()\fR,
 \fBLinkUnitFiles()\fR,
-\fBPresetUnitFiles\fR,
-\fBMaskUnitFiles\fR, and similar) require
+\fBPresetUnitFiles()\fR,
+\fBMaskUnitFiles()\fR, and similar) require
 org\&.freedesktop\&.systemd1\&.manage\-unit\-files\&. Operations which modify the exported environment (\fBSetEnvironment()\fR,
 \fBUnsetEnvironment()\fR,
 \fBUnsetAndSetEnvironment()\fR) require
@@ -1702,6 +1747,8 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly as RequiresMountsFor = [\*(Aq\&.\&.\&.\*(Aq, \&.\&.\&.];
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
+      readonly as WantsMountsFor = [\*(Aq\&.\&.\&.\*(Aq, \&.\&.\&.];
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly as Documentation = [\*(Aq\&.\&.\&.\*(Aq, \&.\&.\&.];
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly s Description = \*(Aq\&.\&.\&.\*(Aq;
@@ -1940,6 +1987,7 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice {
 
 
 
+
 .SS "Methods"
 .PP
 \fBStart()\fR,
@@ -2316,6 +2364,8 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice {
       readonly t ExecMainStartTimestampMonotonic = \&.\&.\&.;
       readonly t ExecMainExitTimestamp = \&.\&.\&.;
       readonly t ExecMainExitTimestampMonotonic = \&.\&.\&.;
+      readonly t ExecMainHandoffTimestamp = \&.\&.\&.;
+      readonly t ExecMainHandoffTimestampMonotonic = \&.\&.\&.;
       readonly u ExecMainPID = \&.\&.\&.;
       readonly i ExecMainCode = \&.\&.\&.;
       readonly i ExecMainStatus = \&.\&.\&.;
@@ -2366,6 +2416,10 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t MemoryAvailable = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveMemoryMax = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveMemoryHigh = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t CPUUsageNSec = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly ay EffectiveCPUs = [\&.\&.\&.];
@@ -2374,6 +2428,8 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t TasksCurrent = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveTasksMax = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t IPIngressBytes = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t IPIngressPackets = \&.\&.\&.;
@@ -2478,6 +2534,8 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t StartupMemoryZSwapMax = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly b MemoryZSwapWriteback = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t MemoryLimit = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly s DevicePolicy = \*(Aq\&.\&.\&.\*(Aq;
@@ -3236,6 +3294,12 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice {
 
 
 
+
+
+
+
+
+
 .SS "Methods"
 .PP
 \fBBindMount()\fR
@@ -3303,13 +3367,28 @@ also correspond to the configured settings of the unit files, but instead of bei
 \fIExecMainStartTimestampMonotonic\fR,
 \fIExecMainExitTimestamp\fR,
 \fIExecMainExitTimestampMonotonic\fR,
+\fIExecMainHandoffTimestamp\fR,
+\fIExecMainHandoffTimestampMonotonic\fR,
 \fIExecMainPID\fR,
 \fIExecMainCode\fR,
 \fIExecMainStatus\fR
-contain information about the main process of the service as far as it is known\&. This is often the same runtime information that is stored in
-\fIExecStart\fR\&. However, it deviates for
+contain information about the main process of the service as far as it is known\&. The
+\fIExecMainStartTimestamp\fR
+timestamps record when the main process of the service is created\&.
+\fIExecMainExitTimestamp\fR
+timestamps record when the main process exit has been detected by the service manager\&.
+\fIExecMainHandoffTimestamp\fR
+timestamps records when the service binary is about to be executed by
+\fBsystemd\-executor\fR
+(this timestamp is recorded regardless if the immediately following
+\fBexecve()\fR
+system call succeeds or fails)\&. This is often the same runtime information that is also maintained for
+\fIExecStart=\fR\&. However, it deviates for services with
 \fIType=forking\fR
-services where the main process of the service is not forked off systemd directly\&. These fields either contain information of the last run of the process or of the current running process\&.
+as well as services that use
+\fIMAINPID=\fR
+\fBsd_notify()\fR
+messages as the main process of the service is not forked off by the service manager directly in that case\&. These fields either contain information of the last run of the process or of the current running process\&.
 .PP
 \fIMainPID\fR
 and
@@ -3457,6 +3536,8 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2esocket {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly b PassCredentials = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
+      readonly b PassFileDescriptorsToExec = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly b PassSecurity = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("const")
       readonly b PassPacketInfo = \&.\&.\&.;
@@ -3537,6 +3618,10 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2esocket {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t MemoryAvailable = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveMemoryMax = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveMemoryHigh = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t CPUUsageNSec = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly ay EffectiveCPUs = [\&.\&.\&.];
@@ -3545,6 +3630,8 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2esocket {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t TasksCurrent = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveTasksMax = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t IPIngressBytes = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t IPIngressPackets = \&.\&.\&.;
@@ -3649,6 +3736,8 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2esocket {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t StartupMemoryZSwapMax = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly b MemoryZSwapWriteback = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t MemoryLimit = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly s DevicePolicy = \*(Aq\&.\&.\&.\*(Aq;
@@ -4399,6 +4488,11 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2esocket {
 
 
 
+
+
+
+
+
 .PP
 \fIPollLimitIntervalUSec\fR/\fIPollLimitBurst\fR
 properties configure the polling limit for the socket unit\&. Expects a time in \(mcs, resp\&. an unsigned integer\&. If either is set to zero the limiting feature is turned off\&.
@@ -4568,6 +4662,10 @@ node /org/freedesktop/systemd1/unit/home_2emount {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t MemoryAvailable = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveMemoryMax = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveMemoryHigh = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t CPUUsageNSec = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly ay EffectiveCPUs = [\&.\&.\&.];
@@ -4576,6 +4674,8 @@ node /org/freedesktop/systemd1/unit/home_2emount {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t TasksCurrent = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveTasksMax = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t IPIngressBytes = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t IPIngressPackets = \&.\&.\&.;
@@ -4680,6 +4780,8 @@ node /org/freedesktop/systemd1/unit/home_2emount {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t StartupMemoryZSwapMax = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly b MemoryZSwapWriteback = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t MemoryLimit = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly s DevicePolicy = \*(Aq\&.\&.\&.\*(Aq;
@@ -5386,6 +5488,10 @@ node /org/freedesktop/systemd1/unit/home_2emount {
 
 
 
+
+
+
+
 .SS "Properties"
 .PP
 Most of the properties map directly to the corresponding settings in mount unit files\&. As mount units invoke the
@@ -5626,6 +5732,10 @@ node /org/freedesktop/systemd1/unit/dev_2dsda3_2eswap {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t MemoryAvailable = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveMemoryMax = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveMemoryHigh = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t CPUUsageNSec = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly ay EffectiveCPUs = [\&.\&.\&.];
@@ -5634,6 +5744,8 @@ node /org/freedesktop/systemd1/unit/dev_2dsda3_2eswap {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t TasksCurrent = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveTasksMax = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t IPIngressBytes = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t IPIngressPackets = \&.\&.\&.;
@@ -5738,6 +5850,8 @@ node /org/freedesktop/systemd1/unit/dev_2dsda3_2eswap {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t StartupMemoryZSwapMax = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly b MemoryZSwapWriteback = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t MemoryLimit = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly s DevicePolicy = \*(Aq\&.\&.\&.\*(Aq;
@@ -6437,6 +6551,10 @@ node /org/freedesktop/systemd1/unit/dev_2dsda3_2eswap {
 
 
 
+
+
+
+
 .SS "Properties"
 .PP
 Most of the properties map directly to the corresponding settings in swap unit files\&. As mount units invoke the
@@ -6563,6 +6681,10 @@ node /org/freedesktop/systemd1/unit/system_2eslice {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t MemoryAvailable = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveMemoryMax = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveMemoryHigh = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t CPUUsageNSec = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly ay EffectiveCPUs = [\&.\&.\&.];
@@ -6571,6 +6693,8 @@ node /org/freedesktop/systemd1/unit/system_2eslice {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t TasksCurrent = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveTasksMax = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t IPIngressBytes = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t IPIngressPackets = \&.\&.\&.;
@@ -6675,6 +6799,8 @@ node /org/freedesktop/systemd1/unit/system_2eslice {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t StartupMemoryZSwapMax = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly b MemoryZSwapWriteback = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t MemoryLimit = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly s DevicePolicy = \*(Aq\&.\&.\&.\*(Aq;
@@ -6824,6 +6950,10 @@ node /org/freedesktop/systemd1/unit/system_2eslice {
 
 
 
+
+
+
+
 .SS "Properties"
 .PP
 Most properties correspond directly with the matching settings in slice unit files\&.
@@ -6878,6 +7008,10 @@ node /org/freedesktop/systemd1/unit/session_2d1_2escope {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t MemoryAvailable = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveMemoryMax = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveMemoryHigh = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t CPUUsageNSec = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly ay EffectiveCPUs = [\&.\&.\&.];
@@ -6886,6 +7020,8 @@ node /org/freedesktop/systemd1/unit/session_2d1_2escope {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t TasksCurrent = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly t EffectiveTasksMax = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t IPIngressBytes = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t IPIngressPackets = \&.\&.\&.;
@@ -6990,6 +7126,8 @@ node /org/freedesktop/systemd1/unit/session_2d1_2escope {
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t StartupMemoryZSwapMax = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
+      readonly b MemoryZSwapWriteback = \&.\&.\&.;
+      @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly t MemoryLimit = \&.\&.\&.;
       @org\&.freedesktop\&.DBus\&.Property\&.EmitsChangedSignal("false")
       readonly s DevicePolicy = \*(Aq\&.\&.\&.\*(Aq;
@@ -7168,13 +7306,17 @@ node /org/freedesktop/systemd1/unit/session_2d1_2escope {
 
 
 
+
+
+
+
 .SS "Methods"
 .PP
 \fBAbandon()\fR
 may be used to place a scope unit in the "abandoned" state\&. This may be used to inform the system manager that the manager that created the scope lost interest in the scope (for example, because it is terminating), without wanting to shut down the scope entirely\&.
 .SS "Signals"
 .PP
-\fBRequestStop\fR
+\fBRequestStop()\fR
 is sent to the peer that is configured in the
 \fIController\fR
 property when systemd is requested to terminate the scope unit\&. A program registering a scope can use this to cleanly shut down the processes it added to the scope instead of letting systemd do it with the usual
@@ -7186,7 +7328,7 @@ All properties correspond directly with the matching properties of service units
 .PP
 \fIController\fR
 contains the bus name (unique or well\-known) that is notified when the scope unit is to be shut down via a
-\fBRequestStop\fR
+\fBRequestStop()\fR
 signal (see below)\&. This is set when the scope is created\&. If not set, the scope\*(Aqs processes will terminated with
 \fBSIGTERM\fR
 directly\&.
@@ -7348,6 +7490,13 @@ were added in version 253\&.
 \fBSoftReboot()\fR, and
 \fBDumpUnitFileDescriptorStore()\fR
 were added in version 254\&.
+.PP
+\fBStartAuxiliaryScope()\fR,
+\fIShutdownStartTimestamp\fR,
+\fIShutdownStartTimestampMonotonic\fR
+and
+\fISoftRebootsCount\fR
+were added in version 256\&.
 .SS "Unit Objects"
 .PP
 \fIUpholds\fR
@@ -7365,6 +7514,9 @@ was added in version 254\&.
 .PP
 \fISurviveFinalKillSignal\fR
 was added in version 255\&.
+.PP
+\fIWantsMountsFor\fR
+was added in version 256\&.
 .SS "Service Unit Objects"
 .PP
 \fIControlGroupId\fR
@@ -7409,6 +7561,14 @@ were added in version 254\&.
 \fIMemorySwapPeak\fR, and
 \fIMemoryZSwapCurrent\fR
 were added in version 255\&.
+.PP
+\fIEffectiveMemoryHigh\fR,
+\fIEffectiveMemoryMax\fR,
+\fIEffectiveTasksMax\fR,
+\fIMemoryZSwapWriteback\fR,
+\fIExecMainHandoffTimestampMonotonic\fR, and
+\fIExecMainHandoffTimestamp\fR
+were added in version 256\&.
 .SS "Socket Unit Objects"
 .PP
 \fIControlGroupId\fR
@@ -7448,6 +7608,13 @@ were added in version 254\&.
 \fIMemorySwapPeak\fR, and
 \fIMemoryZSwapCurrent\fR
 were added in version 255\&.
+.PP
+\fIEffectiveMemoryHigh\fR,
+\fIEffectiveMemoryMax\fR,
+\fIEffectiveTasksMax\fR,
+\fIMemoryZSwapWriteback\fR, and
+\fIPassFileDescriptorsToExec\fR
+were added in version 256\&.
 .SS "Mount Unit Objects"
 .PP
 \fIControlGroupId\fR
@@ -7485,6 +7652,12 @@ were added in version 254\&.
 \fIMemorySwapPeak\fR, and
 \fIMemoryZSwapCurrent\fR
 were added in version 255\&.
+.PP
+\fIEffectiveMemoryHigh\fR,
+\fIEffectiveMemoryMax\fR,
+\fIEffectiveTasksMax\fR, and
+\fIMemoryZSwapWriteback\fR
+were added in version 256\&.
 .SS "Swap Unit Objects"
 .PP
 \fIControlGroupId\fR
@@ -7522,6 +7695,12 @@ were added in version 254\&.
 \fIMemorySwapPeak\fR, and
 \fIMemoryZSwapCurrent\fR
 were added in version 255\&.
+.PP
+\fIEffectiveMemoryHigh\fR,
+\fIEffectiveMemoryMax\fR,
+\fIEffectiveTasksMax\fR, and
+\fIMemoryZSwapWriteback\fR
+were added in version 256\&.
 .SS "Slice Unit Objects"
 .PP
 \fIControlGroupId\fR
@@ -7548,6 +7727,12 @@ were added in version 254\&.
 \fIMemorySwapPeak\fR, and
 \fIMemoryZSwapCurrent\fR
 were added in version 255\&.
+.PP
+\fIEffectiveMemoryHigh\fR,
+\fIEffectiveMemoryMax\fR,
+\fIEffectiveTasksMax\fR, and
+\fIMemoryZSwapWriteback\fR
+were added in version 256\&.
 .SS "Scope Unit Objects"
 .PP
 \fIControlGroupId\fR
@@ -7576,6 +7761,12 @@ were added in version 254\&.
 \fIMemorySwapPeak\fR, and
 \fIMemoryZSwapCurrent\fR
 were added in version 255\&.
+.PP
+\fIEffectiveMemoryHigh\fR,
+\fIEffectiveMemoryMax\fR,
+\fIEffectiveTasksMax\fR, and
+\fIMemoryZSwapWriteback\fR
+were added in version 256\&.
 .SS "Job Objects"
 .PP
 \fIActivationDetails\fR
diff --git a/upstream/fedora-rawhide/man5/org.freedesktop.timedate1.5 b/upstream/fedora-rawhide/man5/org.freedesktop.timedate1.5
index 63adbcd7..cca2dc94 100644
--- a/upstream/fedora-rawhide/man5/org.freedesktop.timedate1.5
+++ b/upstream/fedora-rawhide/man5/org.freedesktop.timedate1.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "ORG\&.FREEDESKTOP\&.TIMEDATE1" "5" "" "systemd 255" "org.freedesktop.timedate1"
+.TH "ORG\&.FREEDESKTOP\&.TIMEDATE1" "5" "" "systemd 256~rc3" "org.freedesktop.timedate1"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
diff --git a/upstream/fedora-rawhide/man5/os-release.5 b/upstream/fedora-rawhide/man5/os-release.5
index 795363d3..fc3297c4 100644
--- a/upstream/fedora-rawhide/man5/os-release.5
+++ b/upstream/fedora-rawhide/man5/os-release.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "OS\-RELEASE" "5" "" "systemd 255" "os-release"
+.TH "OS\-RELEASE" "5" "" "systemd 256~rc3" "os-release"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,13 +23,18 @@
 os-release, initrd-release, extension-release \- Operating system identification
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/os\-release
-.PP
+.RE
+.RS 4
 /usr/lib/os\-release
-.PP
+.RE
+.RS 4
 /etc/initrd\-release
-.PP
+.RE
+.RS 4
 /usr/lib/extension\-release\&.d/extension\-release\&.\fIIMAGE\fR
+.RE
 .SH "DESCRIPTION"
 .PP
 The
@@ -53,7 +58,7 @@ is the recommended place to store OS release information as part of vendor trees
 /etc/os\-release
 should be a relative symlink to
 /usr/lib/os\-release, to provide compatibility with applications only looking at
-/etc/\&. A relative symlink instead of an absolute symlink is necessary to avoid breaking the link in a chroot or initrd environment such as dracut\&.
+/etc/\&. A relative symlink instead of an absolute symlink is necessary to avoid breaking the link in a chroot or initrd environment\&.
 .PP
 os\-release
 contains data that is defined by the operating system vendor and should generally not be changed by the administrator\&.
@@ -674,11 +679,7 @@ if \*(Aqdebian\*(Aq in [os_release\&.get(\*(AqID\*(Aq, \*(Aqlinux\*(Aq),
 Note that the above version that uses the built\-in implementation is preferred in most cases, and the open\-coded version here is provided for reference\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBlsb_release\fR(1),
-\fBhostname\fR(5),
-\fBmachine-id\fR(5),
-\fBmachine-info\fR(5)
+\fBsystemd\fR(1), \fBlsb_release\fR(1), \fBhostname\fR(5), \fBmachine-id\fR(5), \fBmachine-info\fR(5)
 .SH "NOTES"
 .IP " 1." 4
 Announcement of /etc/os-release
diff --git a/upstream/fedora-rawhide/man5/pacman.conf.5 b/upstream/fedora-rawhide/man5/pacman.conf.5
index 9e994376..0471f092 100644
--- a/upstream/fedora-rawhide/man5/pacman.conf.5
+++ b/upstream/fedora-rawhide/man5/pacman.conf.5
@@ -2,12 +2,12 @@
 .\"     Title: pacman.conf
 .\"    Author: [see the "Authors" section]
 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
-.\"      Date: 2024-01-25
+.\"      Date: 2024-04-14
 .\"    Manual: Pacman Manual
-.\"    Source: Pacman 6.0.2
+.\"    Source: Pacman 6.1.0
 .\"  Language: English
 .\"
-.TH "PACMAN\&.CONF" "5" "2024\-01\-25" "Pacman 6\&.0\&.2" "Pacman Manual"
+.TH "PACMAN\&.CONF" "5" "2024\-04\-14" "Pacman 6\&.1\&.0" "Pacman Manual"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -165,7 +165,7 @@ will use the system architecture, provided via \(lquname \-m\(rq\&. If unset, no
 can always be installed, as they are meant to be architecture independent\&.
 .RE
 .PP
-\fBXferCommand =\fR /path/to/command %u
+\fBXferCommand =\fR /path/to/command %u [%o]
 .RS 4
 If set, an external program will be used to download all remote files\&. All instances of
 %u
@@ -291,6 +291,11 @@ Include another config file\&. This file can include repositories or general con
 rules\&.
 .RE
 .PP
+\fBCacheServer =\fR url
+.RS 4
+A full URL to a location where the packages, and signatures (if available) for this repository can be found\&. Cache servers will be tried before any non\-cache servers, will not be removed from the server pool for 404 download errors, and will not be used for database files\&.
+.RE
+.PP
 \fBServer =\fR url
 .RS 4
 A full URL to a location where the database, packages, and signatures (if available) for this repository can be found\&.
@@ -499,17 +504,6 @@ Andrew Gregory <andrew\&.gregory\&.8@gmail\&.com>
 .sp -1
 .IP \(bu 2.3
 .\}
-Eli Schwartz <eschwartz@archlinux\&.org>
-.RE
-.sp
-.RS 4
-.ie n \{\
-\h'-04'\(bu\h'+03'\c
-.\}
-.el \{\
-.sp -1
-.IP \(bu 2.3
-.\}
 Morgan Adamiec <morganamilo@archlinux\&.org>
 .RE
 .sp
@@ -592,4 +586,15 @@ Nagy Gabor <ngaba@bibl\&.u\-szeged\&.hu>
 Dave Reisner <dreisner@archlinux\&.org>
 .RE
 .sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+Eli Schwartz <eschwartz@archlinux\&.org>
+.RE
+.sp
 For additional contributors, use git shortlog \-s on the pacman\&.git repository\&.
diff --git a/upstream/fedora-rawhide/man5/passwd.5 b/upstream/fedora-rawhide/man5/passwd.5
index e4bcb8e0..15703831 100644
--- a/upstream/fedora-rawhide/man5/passwd.5
+++ b/upstream/fedora-rawhide/man5/passwd.5
@@ -8,7 +8,7 @@
 .\" Modified Sun Jun 18 01:53:57 1995 by Andries Brouwer (aeb@cwi.nl)
 .\" Modified Mon Jan  5 20:24:40 MET 1998 by Michael Haardt
 .\"  (michael@cantor.informatik.rwth-aachen.de)
-.TH passwd 5 2023-10-31 "Linux man-pages 6.06"
+.TH passwd 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 passwd \- password file
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc.5 b/upstream/fedora-rawhide/man5/proc.5
index 788cb97e..ce072ee9 100644
--- a/upstream/fedora-rawhide/man5/proc.5
+++ b/upstream/fedora-rawhide/man5/proc.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc 5 2023-10-31 "Linux man-pages 6.06"
+.TH proc 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 proc \- process information, system information, and sysctl pseudo-filesystem
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_apm.5 b/upstream/fedora-rawhide/man5/proc_apm.5
index 03462ace..2987d2bd 100644
--- a/upstream/fedora-rawhide/man5/proc_apm.5
+++ b/upstream/fedora-rawhide/man5/proc_apm.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_apm 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_apm 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/apm \- advanced power management
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_buddyinfo.5 b/upstream/fedora-rawhide/man5/proc_buddyinfo.5
index 7b3db6c6..b98185c5 100644
--- a/upstream/fedora-rawhide/man5/proc_buddyinfo.5
+++ b/upstream/fedora-rawhide/man5/proc_buddyinfo.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_buddyinfo 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_buddyinfo 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/buddyinfo \- memory fragmentation
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_bus.5 b/upstream/fedora-rawhide/man5/proc_bus.5
index aeb8ec62..505b8ea4 100644
--- a/upstream/fedora-rawhide/man5/proc_bus.5
+++ b/upstream/fedora-rawhide/man5/proc_bus.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_bus 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_bus 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/bus/ \- installed buses
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_cgroups.5 b/upstream/fedora-rawhide/man5/proc_cgroups.5
index 61a675e0..b858a64c 100644
--- a/upstream/fedora-rawhide/man5/proc_cgroups.5
+++ b/upstream/fedora-rawhide/man5/proc_cgroups.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_cgroups 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_cgroups 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/cgroups \- control groups
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_cmdline.5 b/upstream/fedora-rawhide/man5/proc_cmdline.5
index f030d61b..55873f95 100644
--- a/upstream/fedora-rawhide/man5/proc_cmdline.5
+++ b/upstream/fedora-rawhide/man5/proc_cmdline.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_cmdline 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_cmdline 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/cmdline \- kernel boot arguments
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_config.gz.5 b/upstream/fedora-rawhide/man5/proc_config.gz.5
index eedafc80..1d894bd4 100644
--- a/upstream/fedora-rawhide/man5/proc_config.gz.5
+++ b/upstream/fedora-rawhide/man5/proc_config.gz.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_config.gz 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_config.gz 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/config.gz \- kernel build configuration
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_cpuinfo.5 b/upstream/fedora-rawhide/man5/proc_cpuinfo.5
index 648f5057..7d620ce8 100644
--- a/upstream/fedora-rawhide/man5/proc_cpuinfo.5
+++ b/upstream/fedora-rawhide/man5/proc_cpuinfo.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_cpuinfo 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_cpuinfo 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/cpuinfo \- CPU and system architecture information
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_crypto.5 b/upstream/fedora-rawhide/man5/proc_crypto.5
index a3e0096d..eeee62ef 100644
--- a/upstream/fedora-rawhide/man5/proc_crypto.5
+++ b/upstream/fedora-rawhide/man5/proc_crypto.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_crypto 5 2023-11-24 "Linux man-pages 6.06"
+.TH proc_crypto 5 2023-11-24 "Linux man-pages 6.7"
 .SH NAME
 /proc/crypto \- ciphers provided by kernel crypto API
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_devices.5 b/upstream/fedora-rawhide/man5/proc_devices.5
index b17fb81a..27280ca3 100644
--- a/upstream/fedora-rawhide/man5/proc_devices.5
+++ b/upstream/fedora-rawhide/man5/proc_devices.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_devices 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_devices 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/devices \- major numbers and device groups
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_diskstats.5 b/upstream/fedora-rawhide/man5/proc_diskstats.5
index 59c028f9..76f83470 100644
--- a/upstream/fedora-rawhide/man5/proc_diskstats.5
+++ b/upstream/fedora-rawhide/man5/proc_diskstats.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_diskstats 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_diskstats 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/diskstats \- disk I/O statistics
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_dma.5 b/upstream/fedora-rawhide/man5/proc_dma.5
index ddc4dd94..6882949b 100644
--- a/upstream/fedora-rawhide/man5/proc_dma.5
+++ b/upstream/fedora-rawhide/man5/proc_dma.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_dma 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_dma 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/dma \- ISA DMA channels
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_driver.5 b/upstream/fedora-rawhide/man5/proc_driver.5
index ec17a4c4..ec86255c 100644
--- a/upstream/fedora-rawhide/man5/proc_driver.5
+++ b/upstream/fedora-rawhide/man5/proc_driver.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_driver 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_driver 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/driver/ \- empty dir
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_execdomains.5 b/upstream/fedora-rawhide/man5/proc_execdomains.5
index f77465b3..945cbf3f 100644
--- a/upstream/fedora-rawhide/man5/proc_execdomains.5
+++ b/upstream/fedora-rawhide/man5/proc_execdomains.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_execdomains 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_execdomains 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/execdomains \- ABI personalities (obsolete)
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_fb.5 b/upstream/fedora-rawhide/man5/proc_fb.5
index 96336075..31ea1cee 100644
--- a/upstream/fedora-rawhide/man5/proc_fb.5
+++ b/upstream/fedora-rawhide/man5/proc_fb.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_fb 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_fb 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/fb \- frame buffer
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_filesystems.5 b/upstream/fedora-rawhide/man5/proc_filesystems.5
index c7f002a6..2ed6b54f 100644
--- a/upstream/fedora-rawhide/man5/proc_filesystems.5
+++ b/upstream/fedora-rawhide/man5/proc_filesystems.5
@@ -8,7 +8,7 @@
 .\" to see what information could be imported from that file
 .\" into this file.
 .\"
-.TH proc_filesystems 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_filesystems 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/filesystems \- supported filesystems
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_fs.5 b/upstream/fedora-rawhide/man5/proc_fs.5
index 57bcbfc9..31fe94c8 100644
--- a/upstream/fedora-rawhide/man5/proc_fs.5
+++ b/upstream/fedora-rawhide/man5/proc_fs.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_fs 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_fs 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/fs/ \- mounted filesystems
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_ide.5 b/upstream/fedora-rawhide/man5/proc_ide.5
index 41521a63..7e28acc3 100644
--- a/upstream/fedora-rawhide/man5/proc_ide.5
+++ b/upstream/fedora-rawhide/man5/proc_ide.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_ide 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_ide 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/ide/ \- IDE channels and attached devices
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_interrupts.5 b/upstream/fedora-rawhide/man5/proc_interrupts.5
index c9874bca..897399a5 100644
--- a/upstream/fedora-rawhide/man5/proc_interrupts.5
+++ b/upstream/fedora-rawhide/man5/proc_interrupts.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_interrupts 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_interrupts 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/interrupts \- number of interrupts
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_iomem.5 b/upstream/fedora-rawhide/man5/proc_iomem.5
index e9c17dfd..55414501 100644
--- a/upstream/fedora-rawhide/man5/proc_iomem.5
+++ b/upstream/fedora-rawhide/man5/proc_iomem.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_iomem 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_iomem 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/iomem \- I/O memory map
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_ioports.5 b/upstream/fedora-rawhide/man5/proc_ioports.5
index 968cf555..e07c2786 100644
--- a/upstream/fedora-rawhide/man5/proc_ioports.5
+++ b/upstream/fedora-rawhide/man5/proc_ioports.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_ioports 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_ioports 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/ioports \- I/O port regions
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_kallsyms.5 b/upstream/fedora-rawhide/man5/proc_kallsyms.5
index 91b53638..a4f30a45 100644
--- a/upstream/fedora-rawhide/man5/proc_kallsyms.5
+++ b/upstream/fedora-rawhide/man5/proc_kallsyms.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_kallsyms 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_kallsyms 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/kallsyms \- kernel exported symbols
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_kcore.5 b/upstream/fedora-rawhide/man5/proc_kcore.5
index 269b73c5..9a98a950 100644
--- a/upstream/fedora-rawhide/man5/proc_kcore.5
+++ b/upstream/fedora-rawhide/man5/proc_kcore.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_kcore 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_kcore 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/kcore \- physical memory
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_keys.5 b/upstream/fedora-rawhide/man5/proc_keys.5
index 9c4f2d5b..5cdcbee0 100644
--- a/upstream/fedora-rawhide/man5/proc_keys.5
+++ b/upstream/fedora-rawhide/man5/proc_keys.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_keys 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_keys 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/keys, /proc/key\-users \- in-kernel key management
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_kmsg.5 b/upstream/fedora-rawhide/man5/proc_kmsg.5
index a64e0361..1486552d 100644
--- a/upstream/fedora-rawhide/man5/proc_kmsg.5
+++ b/upstream/fedora-rawhide/man5/proc_kmsg.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_kmsg 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_kmsg 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/kmsg \- kernel messages
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_kpagecgroup.5 b/upstream/fedora-rawhide/man5/proc_kpagecgroup.5
index ee0877e6..41f32372 100644
--- a/upstream/fedora-rawhide/man5/proc_kpagecgroup.5
+++ b/upstream/fedora-rawhide/man5/proc_kpagecgroup.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_kpagecgroup 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_kpagecgroup 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/kpagecgroup \- memory cgroups
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_kpagecount.5 b/upstream/fedora-rawhide/man5/proc_kpagecount.5
index 8bb8230a..16cf080d 100644
--- a/upstream/fedora-rawhide/man5/proc_kpagecount.5
+++ b/upstream/fedora-rawhide/man5/proc_kpagecount.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_kpagecount 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_kpagecount 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/kpagecount \- count of mappings of physical pages
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_kpageflags.5 b/upstream/fedora-rawhide/man5/proc_kpageflags.5
index e0f9b751..5c23d024 100644
--- a/upstream/fedora-rawhide/man5/proc_kpageflags.5
+++ b/upstream/fedora-rawhide/man5/proc_kpageflags.5
@@ -5,7 +5,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_kpageflags 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_kpageflags 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/kpageflags \- physical pages frame masks
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_loadavg.5 b/upstream/fedora-rawhide/man5/proc_loadavg.5
index 3403a2b1..fba66031 100644
--- a/upstream/fedora-rawhide/man5/proc_loadavg.5
+++ b/upstream/fedora-rawhide/man5/proc_loadavg.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_loadavg 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_loadavg 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/loadavg \- load average
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_locks.5 b/upstream/fedora-rawhide/man5/proc_locks.5
index 5269cce1..c33ec82a 100644
--- a/upstream/fedora-rawhide/man5/proc_locks.5
+++ b/upstream/fedora-rawhide/man5/proc_locks.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_locks 5 2023-11-19 "Linux man-pages 6.06"
+.TH proc_locks 5 2023-11-19 "Linux man-pages 6.7"
 .SH NAME
 /proc/locks \- current file locks and leases
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_malloc.5 b/upstream/fedora-rawhide/man5/proc_malloc.5
index 9ed444e2..d6197dce 100644
--- a/upstream/fedora-rawhide/man5/proc_malloc.5
+++ b/upstream/fedora-rawhide/man5/proc_malloc.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_malloc 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_malloc 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/malloc \- debug malloc (obsolete)
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_meminfo.5 b/upstream/fedora-rawhide/man5/proc_meminfo.5
index d2454114..7a2e70eb 100644
--- a/upstream/fedora-rawhide/man5/proc_meminfo.5
+++ b/upstream/fedora-rawhide/man5/proc_meminfo.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_meminfo 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_meminfo 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/meminfo \- memory usage
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_modules.5 b/upstream/fedora-rawhide/man5/proc_modules.5
index 56ad8f9e..d040fde5 100644
--- a/upstream/fedora-rawhide/man5/proc_modules.5
+++ b/upstream/fedora-rawhide/man5/proc_modules.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_modules 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_modules 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/modules \- loaded modules
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_mtrr.5 b/upstream/fedora-rawhide/man5/proc_mtrr.5
index 6860d112..d2d1991b 100644
--- a/upstream/fedora-rawhide/man5/proc_mtrr.5
+++ b/upstream/fedora-rawhide/man5/proc_mtrr.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_mtrr 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_mtrr 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/mtrr \- memory type range registers
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_partitions.5 b/upstream/fedora-rawhide/man5/proc_partitions.5
index ef5874d8..ff58779a 100644
--- a/upstream/fedora-rawhide/man5/proc_partitions.5
+++ b/upstream/fedora-rawhide/man5/proc_partitions.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_partitions 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_partitions 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/partitions \- major and minor numbers of partitions
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pci.5 b/upstream/fedora-rawhide/man5/proc_pci.5
index 0fa2cc88..6977571f 100644
--- a/upstream/fedora-rawhide/man5/proc_pci.5
+++ b/upstream/fedora-rawhide/man5/proc_pci.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pci 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pci 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pci \- PCI devices
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid.5 b/upstream/fedora-rawhide/man5/proc_pid.5
index 172b7805..0d8cdafa 100644
--- a/upstream/fedora-rawhide/man5/proc_pid.5
+++ b/upstream/fedora-rawhide/man5/proc_pid.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/, /proc/self/ \- process information
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_attr.5 b/upstream/fedora-rawhide/man5/proc_pid_attr.5
index 2f8fa2a8..33993a88 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_attr.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_attr.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_attr 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_attr 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/attr/ \- security-related attributes
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_autogroup.5 b/upstream/fedora-rawhide/man5/proc_pid_autogroup.5
index 7765d533..cbf8e4d5 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_autogroup.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_autogroup.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_autogroup 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_autogroup 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 proc_pid_autogroup \- group tasks for the scheduler
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_auxv.5 b/upstream/fedora-rawhide/man5/proc_pid_auxv.5
index ce36368a..524414de 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_auxv.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_auxv.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_auxv 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_auxv 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/auxv \- exec(3) information
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_cgroup.5 b/upstream/fedora-rawhide/man5/proc_pid_cgroup.5
index 2605b502..c78fde4f 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_cgroup.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_cgroup.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_cgroup 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_cgroup 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/cgroup \- control group
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_clear_refs.5 b/upstream/fedora-rawhide/man5/proc_pid_clear_refs.5
index d98144aa..134a3b94 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_clear_refs.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_clear_refs.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_clear_refs 5 2023-09-07 "Linux man-pages 6.06"
+.TH proc_pid_clear_refs 5 2023-09-07 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/clear_refs \- reset the PG_Referenced and ACCESSED/YOUNG bits
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_cmdline.5 b/upstream/fedora-rawhide/man5/proc_pid_cmdline.5
index 25c43b5e..d9e5967e 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_cmdline.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_cmdline.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_cmdline 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_cmdline 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/cmdline \- command line
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_comm.5 b/upstream/fedora-rawhide/man5/proc_pid_comm.5
index 18566e95..492d4809 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_comm.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_comm.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_comm 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_comm 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/comm \- command name
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_coredump_filter.5 b/upstream/fedora-rawhide/man5/proc_pid_coredump_filter.5
index 638020bc..82f48ed6 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_coredump_filter.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_coredump_filter.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_coredump_filter 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_coredump_filter 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/coredump_filter \- core dump filter
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_cpuset.5 b/upstream/fedora-rawhide/man5/proc_pid_cpuset.5
index 26314704..2bdf32d9 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_cpuset.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_cpuset.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_cpuset 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_cpuset 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/cpuset \- CPU affinity sets
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_cwd.5 b/upstream/fedora-rawhide/man5/proc_pid_cwd.5
index 5ed1b137..df99f113 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_cwd.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_cwd.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_cwd 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_cwd 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/cwd \- symbolic link to current working directory
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_environ.5 b/upstream/fedora-rawhide/man5/proc_pid_environ.5
index 075a2674..104cbe08 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_environ.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_environ.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_environ 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_environ 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/environ \- initial environment
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_exe.5 b/upstream/fedora-rawhide/man5/proc_pid_exe.5
index ca9b7f09..21d2fbc1 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_exe.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_exe.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_exe 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_exe 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/exe \- symbolic link to program pathname
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_fd.5 b/upstream/fedora-rawhide/man5/proc_pid_fd.5
index bb86075d..0489169c 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_fd.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_fd.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_fd 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_fd 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/fd/ \- file descriptors
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_fdinfo.5 b/upstream/fedora-rawhide/man5/proc_pid_fdinfo.5
index 3703012b..1eeb895e 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_fdinfo.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_fdinfo.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_fdinfo 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_fdinfo 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/fdinfo/ \- information about file descriptors
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_io.5 b/upstream/fedora-rawhide/man5/proc_pid_io.5
index f989e493..4ad79f51 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_io.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_io.5
@@ -4,14 +4,16 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_io 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_io 5 2024-03-18 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/io \- I/O statistics
 .SH DESCRIPTION
 .TP
 .IR /proc/ pid /io " (since Linux 2.6.20)"
 .\" commit 7c3ab7381e79dfc7db14a67c6f4f3285664e1ec2
-This file contains I/O statistics for the process, for example:
+This file contains I/O statistics
+for the process and its waited-for children,
+for example:
 .IP
 .in +4n
 .EX
@@ -30,69 +32,69 @@ The fields are as follows:
 .RS
 .TP
 .IR rchar ": characters read"
-The number of bytes which this task has caused to be read from storage.
-This is simply the sum of bytes which this process passed to
+The number of bytes
+returned by successful
 .BR read (2)
 and similar system calls.
-It includes things such as terminal I/O and
-is unaffected by whether or not actual
-physical disk I/O was required (the read might have been satisfied from
-pagecache).
 .TP
 .IR wchar ": characters written"
-The number of bytes which this task has caused, or shall cause to be written
-to disk.
-Similar caveats apply here as with
-.IR rchar .
+The number of bytes
+returned by successful
+.BR write (2)
+and similar system calls.
 .TP
 .IR syscr ": read syscalls"
-Attempt to count the number of read I/O operations\[em]that is,
-system calls such as
+The number of "file read" system calls\[em]those from the
 .BR read (2)
+family,
+.BR sendfile (2),
+.BR copy_file_range (2),
 and
-.BR pread (2).
+.BR ioctl (2)
+.BR BTRFS_IOC_ENCODED_READ [ _32 ]
+(including when invoked by the kernel as part of other syscalls).
 .TP
 .IR syscw ": write syscalls"
-Attempt to count the number of write I/O operations\[em]that is,
-system calls such as
+The number of "file write" system calls\[em]those from the
 .BR write (2)
+family,
+.BR sendfile (2),
+.BR copy_file_range (2),
 and
-.BR pwrite (2).
+.BR ioctl (2)
+.BR BTRFS_IOC_ENCODED_WRITE [ _32 ]
+(including when invoked by the kernel as part of other syscalls).
 .TP
 .IR read_bytes ": bytes read"
-Attempt to count the number of bytes which this process really did cause to
-be fetched from the storage layer.
+The number of bytes really fetched from the storage layer.
 This is accurate for block-backed filesystems.
 .TP
 .IR write_bytes ": bytes written"
-Attempt to count the number of bytes which this process caused to be sent to
-the storage layer.
+The number of bytes really sent to the storage layer.
 .TP
 .IR cancelled_write_bytes :
-The big inaccuracy here is truncate.
-If a process writes 1 MB to a file and then deletes the file,
-it will in fact perform no writeout.
-But it will have been accounted as having caused 1 MB of write.
-In other words: this field represents the number of bytes which this process
-caused to not happen, by truncating pagecache.
-A task can cause "negative" I/O too.
-If this task truncates some dirty pagecache,
-some I/O which another task has been accounted for
-(in its
-.IR write_bytes )
-will not be happening.
+The above statistics fail to account for truncation:
+if a process writes 1 MB to a regular file and then removes it,
+said 1 MB will not be written, but
+.I will
+have nevertheless been accounted as a 1 MB write.
+This field represents the number of bytes "saved" from I/O writeback.
+This can yield to having done negative I/O
+if caches dirtied by another process are truncated.
+.I cancelled_write_bytes
+applies to I/O already accounted-for in
+.IR write_bytes .
 .RE
 .IP
-.IR Note :
-In the current implementation, things are a bit racy on 32-bit systems:
-if process A reads process B's
-.IR /proc/ pid /io
-while process B is updating one of these 64-bit counters,
-process A could see an intermediate result.
-.IP
-Permission to access this file is governed by a ptrace access mode
-.B PTRACE_MODE_READ_FSCREDS
-check; see
-.BR ptrace (2).
+Permission to access this file is governed by
+.BR ptrace (2)
+access mode
+.BR PTRACE_MODE_READ_FSCREDS .
+.SH CAVEATS
+These counters are not atomic:
+on systems where 64-bit integer operations may tear,
+a counter could be updated simultaneously with a read,
+yielding an incorrect intermediate value.
 .SH SEE ALSO
+.BR getrusage (2),
 .BR proc (5)
diff --git a/upstream/fedora-rawhide/man5/proc_pid_limits.5 b/upstream/fedora-rawhide/man5/proc_pid_limits.5
index 70ad07d0..a8ab93c2 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_limits.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_limits.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_oid_limits 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_oid_limits 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/limits \- resource limits
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_map_files.5 b/upstream/fedora-rawhide/man5/proc_pid_map_files.5
index e1ba8024..5b50c450 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_map_files.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_map_files.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_map_files 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_map_files 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/map_files/ \- memory-mapped files
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_maps.5 b/upstream/fedora-rawhide/man5/proc_pid_maps.5
index 22c220f3..25fbbde4 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_maps.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_maps.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_maps 5 2023-09-07 "Linux man-pages 6.06"
+.TH proc_pid_maps 5 2023-09-07 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/maps \- mapped memory regions
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_mem.5 b/upstream/fedora-rawhide/man5/proc_pid_mem.5
index 8cea82e2..b54206d4 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_mem.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_mem.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_mem 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_mem 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/mem \- memory
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_mountinfo.5 b/upstream/fedora-rawhide/man5/proc_pid_mountinfo.5
index 2ff0da3d..257c1db8 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_mountinfo.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_mountinfo.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_mountinfo 5 2023-11-24 "Linux man-pages 6.06"
+.TH proc_pid_mountinfo 5 2023-11-24 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/mountinfo \- mount information
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_mounts.5 b/upstream/fedora-rawhide/man5/proc_pid_mounts.5
index 3084ce13..bcb32f2e 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_mounts.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_mounts.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_mounts 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_mounts 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/mounts \- mounted filesystems
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_mountstats.5 b/upstream/fedora-rawhide/man5/proc_pid_mountstats.5
index 024d69a8..1205b14c 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_mountstats.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_mountstats.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_mountstats 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_mountstats 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/mountstats \- mount statistics
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_net.5 b/upstream/fedora-rawhide/man5/proc_pid_net.5
index 21ae4a6f..590e87d5 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_net.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_net.5
@@ -5,7 +5,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_net 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_net 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/net/, /proc/net/ \- network layer information
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_ns.5 b/upstream/fedora-rawhide/man5/proc_pid_ns.5
index 37517e35..bf83ab5e 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_ns.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_ns.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_ns 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_ns 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/ns/ \- namespaces
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_numa_maps.5 b/upstream/fedora-rawhide/man5/proc_pid_numa_maps.5
index cad08414..4b29fab8 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_numa_maps.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_numa_maps.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_numa_maps 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_numa_maps 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/numa_maps \- NUMA memory policy and allocation
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_oom_score.5 b/upstream/fedora-rawhide/man5/proc_pid_oom_score.5
index 96975fc6..ddaeddf9 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_oom_score.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_oom_score.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_oom_score 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_oom_score 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/oom_score \- OOM-killer score
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_oom_score_adj.5 b/upstream/fedora-rawhide/man5/proc_pid_oom_score_adj.5
index 8eb725e9..a068e33c 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_oom_score_adj.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_oom_score_adj.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_oom_score_adj 5 2023-11-24 "Linux man-pages 6.06"
+.TH proc_pid_oom_score_adj 5 2023-11-24 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/oom_score_adj \- OOM-killer score adjustment
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_pagemap.5 b/upstream/fedora-rawhide/man5/proc_pid_pagemap.5
index 85d4ea86..436e2c51 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_pagemap.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_pagemap.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_pagemap 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_pagemap 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/pagemap \- mapping of virtual pages
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_personality.5 b/upstream/fedora-rawhide/man5/proc_pid_personality.5
index 2bef64f9..4dccf0ce 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_personality.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_personality.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_personality 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_personality 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/personality \- execution domain
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_projid_map.5 b/upstream/fedora-rawhide/man5/proc_pid_projid_map.5
index 33090b5b..cf88aa47 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_projid_map.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_projid_map.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_projid_map 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_projid_map 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/projid_map \- project ID mappings
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_root.5 b/upstream/fedora-rawhide/man5/proc_pid_root.5
index b6b31752..5263329c 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_root.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_root.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_root 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_root 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/root/ \- symbolic link to root directory
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_seccomp.5 b/upstream/fedora-rawhide/man5/proc_pid_seccomp.5
index 031dc5ca..22c582c3 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_seccomp.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_seccomp.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_seccomp 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_seccomp 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/seccomp \- secure computing mode
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_setgroups.5 b/upstream/fedora-rawhide/man5/proc_pid_setgroups.5
index 10dda201..d90ad191 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_setgroups.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_setgroups.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_setgroups 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_setgroups 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/setgroups \- allow or deny setting groups
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_smaps.5 b/upstream/fedora-rawhide/man5/proc_pid_smaps.5
index f0e0b8ae..21d7d5c8 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_smaps.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_smaps.5
@@ -5,7 +5,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_smaps 5 2023-09-07 "Linux man-pages 6.06"
+.TH proc_pid_smaps 5 2023-09-07 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/smaps \- XXX: What does 's' in "smaps" stand for?
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_stack.5 b/upstream/fedora-rawhide/man5/proc_pid_stack.5
index b2e88261..bb1d3c29 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_stack.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_stack.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_stack 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_stack 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/stack \- kernel stack
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_stat.5 b/upstream/fedora-rawhide/man5/proc_pid_stat.5
index 85f42135..b08e441f 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_stat.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_stat.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_stat 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_stat 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/stat \- status information
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_statm.5 b/upstream/fedora-rawhide/man5/proc_pid_statm.5
index 6b02d572..5e3ca2e6 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_statm.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_statm.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_statm 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_statm 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/statm \- memory usage information
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_status.5 b/upstream/fedora-rawhide/man5/proc_pid_status.5
index eddd21b9..fdef4777 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_status.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_status.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_status 5 2023-10-23 "Linux man-pages 6.06"
+.TH proc_pid_status 5 2023-10-23 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/status \- memory usage and status information
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_syscall.5 b/upstream/fedora-rawhide/man5/proc_pid_syscall.5
index c5b6188c..c569293a 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_syscall.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_syscall.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_syscall 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_syscall 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/syscall \- currently executed system call
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_task.5 b/upstream/fedora-rawhide/man5/proc_pid_task.5
index 4b04c84f..70af355a 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_task.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_task.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_task 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_task 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/task/, /proc/tid/, /proc/thread\-self/ \- thread information
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_timers.5 b/upstream/fedora-rawhide/man5/proc_pid_timers.5
index ebee7769..981ba799 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_timers.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_timers.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_timers 5 2023-09-07 "Linux man-pages 6.06"
+.TH proc_pid_timers 5 2023-09-07 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/timers \- POSIX timers
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_timerslack_ns.5 b/upstream/fedora-rawhide/man5/proc_pid_timerslack_ns.5
index 60a51f57..94be8eb9 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_timerslack_ns.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_timerslack_ns.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_timerslack_ns 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_timerslack_ns 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/timerslack_ns \- timer slack in nanoseconds
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_uid_map.5 b/upstream/fedora-rawhide/man5/proc_pid_uid_map.5
index 14cfdf3e..68fd4ffc 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_uid_map.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_uid_map.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_uid_map 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_uid_map 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/gid_map, /proc/pid/uid_map \- user and group ID mappings
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_pid_wchan.5 b/upstream/fedora-rawhide/man5/proc_pid_wchan.5
index c9e018a6..e7ab9d40 100644
--- a/upstream/fedora-rawhide/man5/proc_pid_wchan.5
+++ b/upstream/fedora-rawhide/man5/proc_pid_wchan.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_pid_wchan 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_pid_wchan 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/pid/wchan \- wait channel
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_profile.5 b/upstream/fedora-rawhide/man5/proc_profile.5
index 0a97484a..bd206b41 100644
--- a/upstream/fedora-rawhide/man5/proc_profile.5
+++ b/upstream/fedora-rawhide/man5/proc_profile.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_profile 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_profile 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/profile \- kernel profiling
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_scsi.5 b/upstream/fedora-rawhide/man5/proc_scsi.5
index 753d0ff0..12f92aa8 100644
--- a/upstream/fedora-rawhide/man5/proc_scsi.5
+++ b/upstream/fedora-rawhide/man5/proc_scsi.5
@@ -5,7 +5,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_scsi 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_scsi 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/scsi/ \- SCSI
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_slabinfo.5 b/upstream/fedora-rawhide/man5/proc_slabinfo.5
index d551a431..18949318 100644
--- a/upstream/fedora-rawhide/man5/proc_slabinfo.5
+++ b/upstream/fedora-rawhide/man5/proc_slabinfo.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_slabinfo 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_slabinfo 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/slabinfo \- kernel caches
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_stat.5 b/upstream/fedora-rawhide/man5/proc_stat.5
index 52a14b4f..c7350f0f 100644
--- a/upstream/fedora-rawhide/man5/proc_stat.5
+++ b/upstream/fedora-rawhide/man5/proc_stat.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_stat 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_stat 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/stat \- kernel system statistics
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_swaps.5 b/upstream/fedora-rawhide/man5/proc_swaps.5
index cb411aac..e9569548 100644
--- a/upstream/fedora-rawhide/man5/proc_swaps.5
+++ b/upstream/fedora-rawhide/man5/proc_swaps.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_swaps 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_swaps 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/swaps \- swap areas
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_sys.5 b/upstream/fedora-rawhide/man5/proc_sys.5
index 130ec5bf..f467b30e 100644
--- a/upstream/fedora-rawhide/man5/proc_sys.5
+++ b/upstream/fedora-rawhide/man5/proc_sys.5
@@ -5,7 +5,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_sys 5 2023-09-30 "Linux man-pages 6.06"
+.TH proc_sys 5 2023-09-30 "Linux man-pages 6.7"
 .SH NAME
 /proc/sys/ \- system information, and sysctl pseudo-filesystem
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_sys_abi.5 b/upstream/fedora-rawhide/man5/proc_sys_abi.5
index 161413bf..a9bfd472 100644
--- a/upstream/fedora-rawhide/man5/proc_sys_abi.5
+++ b/upstream/fedora-rawhide/man5/proc_sys_abi.5
@@ -5,7 +5,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_sys_abi 5 2023-09-30 "Linux man-pages 6.06"
+.TH proc_sys_abi 5 2023-09-30 "Linux man-pages 6.7"
 .SH NAME
 /proc/sys/abi/ \- application binary information
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_sys_debug.5 b/upstream/fedora-rawhide/man5/proc_sys_debug.5
index cf2f458d..798da050 100644
--- a/upstream/fedora-rawhide/man5/proc_sys_debug.5
+++ b/upstream/fedora-rawhide/man5/proc_sys_debug.5
@@ -5,7 +5,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_sys_debug 5 2023-09-30 "Linux man-pages 6.06"
+.TH proc_sys_debug 5 2023-09-30 "Linux man-pages 6.7"
 .SH NAME
 /proc/sys/debug/ \- debug
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_sys_dev.5 b/upstream/fedora-rawhide/man5/proc_sys_dev.5
index 0f6c11f5..28ca8311 100644
--- a/upstream/fedora-rawhide/man5/proc_sys_dev.5
+++ b/upstream/fedora-rawhide/man5/proc_sys_dev.5
@@ -5,7 +5,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_sys_dev 5 2023-09-30 "Linux man-pages 6.06"
+.TH proc_sys_dev 5 2023-09-30 "Linux man-pages 6.7"
 .SH NAME
 /proc/sys/dev/ \- device-specific information
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_sys_fs.5 b/upstream/fedora-rawhide/man5/proc_sys_fs.5
index 9196d399..d6f5a4bb 100644
--- a/upstream/fedora-rawhide/man5/proc_sys_fs.5
+++ b/upstream/fedora-rawhide/man5/proc_sys_fs.5
@@ -5,7 +5,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_sys_fs 5 2023-09-30 "Linux man-pages 6.06"
+.TH proc_sys_fs 5 2023-09-30 "Linux man-pages 6.7"
 .SH NAME
 /proc/sys/fs/ \- kernel variables related to filesystems
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_sys_kernel.5 b/upstream/fedora-rawhide/man5/proc_sys_kernel.5
index 8563a761..334d3be2 100644
--- a/upstream/fedora-rawhide/man5/proc_sys_kernel.5
+++ b/upstream/fedora-rawhide/man5/proc_sys_kernel.5
@@ -5,7 +5,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_sys_kernel 5 2023-09-30 "Linux man-pages 6.06"
+.TH proc_sys_kernel 5 2023-09-30 "Linux man-pages 6.7"
 .SH NAME
 /proc/sys/kernel/ \- control a range of kernel parameters
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_sys_net.5 b/upstream/fedora-rawhide/man5/proc_sys_net.5
index ba5b8956..02214cc3 100644
--- a/upstream/fedora-rawhide/man5/proc_sys_net.5
+++ b/upstream/fedora-rawhide/man5/proc_sys_net.5
@@ -5,7 +5,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_sys_net 5 2023-09-30 "Linux man-pages 6.06"
+.TH proc_sys_net 5 2023-09-30 "Linux man-pages 6.7"
 .SH NAME
 /proc/sys/net/ \- networking
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_sys_proc.5 b/upstream/fedora-rawhide/man5/proc_sys_proc.5
index 758ace67..ad9b2329 100644
--- a/upstream/fedora-rawhide/man5/proc_sys_proc.5
+++ b/upstream/fedora-rawhide/man5/proc_sys_proc.5
@@ -5,7 +5,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_sys_proc 5 2023-09-30 "Linux man-pages 6.06"
+.TH proc_sys_proc 5 2023-09-30 "Linux man-pages 6.7"
 .SH NAME
 /proc/sys/proc/ \- ???
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_sys_sunrpc.5 b/upstream/fedora-rawhide/man5/proc_sys_sunrpc.5
index b6b207be..06e90d7e 100644
--- a/upstream/fedora-rawhide/man5/proc_sys_sunrpc.5
+++ b/upstream/fedora-rawhide/man5/proc_sys_sunrpc.5
@@ -5,7 +5,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_sys_sunrpc 5 2023-09-30 "Linux man-pages 6.06"
+.TH proc_sys_sunrpc 5 2023-09-30 "Linux man-pages 6.7"
 .SH NAME
 /proc/sys/sunrpc/ \- Sun remote procedure call for NFS
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_sys_user.5 b/upstream/fedora-rawhide/man5/proc_sys_user.5
index 3fe4e6ea..34d9f882 100644
--- a/upstream/fedora-rawhide/man5/proc_sys_user.5
+++ b/upstream/fedora-rawhide/man5/proc_sys_user.5
@@ -5,7 +5,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_sys_user 5 2023-11-24 "Linux man-pages 6.06"
+.TH proc_sys_user 5 2023-11-24 "Linux man-pages 6.7"
 .SH NAME
 /proc/sys/user/ \- limits on the number of namespaces of various types
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_sys_vm.5 b/upstream/fedora-rawhide/man5/proc_sys_vm.5
index 4f978478..cbd5cf14 100644
--- a/upstream/fedora-rawhide/man5/proc_sys_vm.5
+++ b/upstream/fedora-rawhide/man5/proc_sys_vm.5
@@ -5,7 +5,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_sys_vm 5 2023-09-30 "Linux man-pages 6.06"
+.TH proc_sys_vm 5 2023-09-30 "Linux man-pages 6.7"
 .SH NAME
 /proc/sys/vm/ \- virtual memory subsystem
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_sysrq-trigger.5 b/upstream/fedora-rawhide/man5/proc_sysrq-trigger.5
index 89c488c5..bca3173f 100644
--- a/upstream/fedora-rawhide/man5/proc_sysrq-trigger.5
+++ b/upstream/fedora-rawhide/man5/proc_sysrq-trigger.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_sysrq-trigger 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_sysrq-trigger 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/sysrq\-trigger \- SysRq function
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_sysvipc.5 b/upstream/fedora-rawhide/man5/proc_sysvipc.5
index 5fdf75f8..9ca6701a 100644
--- a/upstream/fedora-rawhide/man5/proc_sysvipc.5
+++ b/upstream/fedora-rawhide/man5/proc_sysvipc.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_sysvipc 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_sysvipc 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/sysvipc/ \- System V IPC
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_tid_children.5 b/upstream/fedora-rawhide/man5/proc_tid_children.5
index 67f984b9..6cb28331 100644
--- a/upstream/fedora-rawhide/man5/proc_tid_children.5
+++ b/upstream/fedora-rawhide/man5/proc_tid_children.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_tid_children 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_tid_children 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/tid/children \- child tasks
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_timer_list.5 b/upstream/fedora-rawhide/man5/proc_timer_list.5
index 51b9575b..e16fc5fd 100644
--- a/upstream/fedora-rawhide/man5/proc_timer_list.5
+++ b/upstream/fedora-rawhide/man5/proc_timer_list.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_timer_list 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_timer_list 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/timer_list \- pending timers
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_timer_stats.5 b/upstream/fedora-rawhide/man5/proc_timer_stats.5
index caf83856..3503f112 100644
--- a/upstream/fedora-rawhide/man5/proc_timer_stats.5
+++ b/upstream/fedora-rawhide/man5/proc_timer_stats.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_timer_stats 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_timer_stats 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/timer_stats \- timer statistics
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_tty.5 b/upstream/fedora-rawhide/man5/proc_tty.5
index e554541f..3b744718 100644
--- a/upstream/fedora-rawhide/man5/proc_tty.5
+++ b/upstream/fedora-rawhide/man5/proc_tty.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_tty 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_tty 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/tty/ \- tty
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_uptime.5 b/upstream/fedora-rawhide/man5/proc_uptime.5
index 7268029d..0fad2539 100644
--- a/upstream/fedora-rawhide/man5/proc_uptime.5
+++ b/upstream/fedora-rawhide/man5/proc_uptime.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_uptime 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_uptime 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/uptime \- system uptime
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_version.5 b/upstream/fedora-rawhide/man5/proc_version.5
index 5a4a703c..0f612d88 100644
--- a/upstream/fedora-rawhide/man5/proc_version.5
+++ b/upstream/fedora-rawhide/man5/proc_version.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_version 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_version 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/version \- kernel version
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_vmstat.5 b/upstream/fedora-rawhide/man5/proc_vmstat.5
index fe7dccdc..453ef1c7 100644
--- a/upstream/fedora-rawhide/man5/proc_vmstat.5
+++ b/upstream/fedora-rawhide/man5/proc_vmstat.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_vmstat 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_vmstat 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/vmstat \- virtual memory statistics
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/proc_zoneinfo.5 b/upstream/fedora-rawhide/man5/proc_zoneinfo.5
index ad3341d9..33e07a68 100644
--- a/upstream/fedora-rawhide/man5/proc_zoneinfo.5
+++ b/upstream/fedora-rawhide/man5/proc_zoneinfo.5
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-3.0-or-later
 .\"
-.TH proc_zoneinfo 5 2023-08-15 "Linux man-pages 6.06"
+.TH proc_zoneinfo 5 2023-08-15 "Linux man-pages 6.7"
 .SH NAME
 /proc/zoneinfo \- memory zones
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/protocols.5 b/upstream/fedora-rawhide/man5/protocols.5
index c30d0527..954f06d5 100644
--- a/upstream/fedora-rawhide/man5/protocols.5
+++ b/upstream/fedora-rawhide/man5/protocols.5
@@ -7,7 +7,7 @@
 .\" 2002-09-22  Seth W. Klein  <sk@sethwklein.net>
 .\"     * protocol numbers are now assigned by the IANA
 .\"
-.TH protocols 5 2023-10-31 "Linux man-pages 6.06"
+.TH protocols 5 2024-02-25 "Linux man-pages 6.7"
 .SH NAME
 protocols \- protocols definition file
 .SH DESCRIPTION
@@ -28,7 +28,7 @@ Protocol numbers and names are specified by the IANA
 Each line is of the following format:
 .P
 .RS
-.I protocol number aliases ...
+.I protocol number aliases .\|.\|.
 .RE
 .P
 where the fields are delimited by spaces or tabs.
diff --git a/upstream/fedora-rawhide/man5/pstore.conf.5 b/upstream/fedora-rawhide/man5/pstore.conf.5
index 247722c9..25858a09 100644
--- a/upstream/fedora-rawhide/man5/pstore.conf.5
+++ b/upstream/fedora-rawhide/man5/pstore.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "PSTORE\&.CONF" "5" "" "systemd 255" "pstore.conf"
+.TH "PSTORE\&.CONF" "5" "" "systemd 256~rc3" "pstore.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,8 +23,24 @@
 pstore.conf, pstore.conf.d \- PStore configuration file
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/systemd/pstore\&.conf
-/etc/systemd/pstore\&.conf\&.d/*
+.RE
+.RS 4
+/run/systemd/pstore\&.conf
+.RE
+.RS 4
+/usr/lib/systemd/pstore\&.conf
+.RE
+.RS 4
+/etc/systemd/pstore\&.conf\&.d/*\&.conf
+.RE
+.RS 4
+/run/systemd/pstore\&.conf\&.d/*\&.conf
+.RE
+.RS 4
+/usr/lib/systemd/pstore\&.conf\&.d/*\&.conf
+.RE
 .SH "DESCRIPTION"
 .PP
 This file configures the behavior of
@@ -32,16 +48,16 @@ This file configures the behavior of
 \m[blue]\fBpstore\fR\m[]\&\s-2\u[1]\d\s+2\&.
 .SH "CONFIGURATION DIRECTORIES AND PRECEDENCE"
 .PP
-The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is either in
-/usr/lib/systemd/
-or
-/etc/systemd/
-and contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
+The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is loaded from one of the listed directories in order of priority, only the first file found is used:
+/etc/systemd/,
+/run/systemd/,
+/usr/local/lib/systemd/,
+/usr/lib/systemd/\&. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can also be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
 /etc/
-if it\*(Aqs shipped in
-/usr/) however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
+if it\*(Aqs shipped under
+/usr/), however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
 .PP
-In addition to the "main" configuration file, drop\-in configuration snippets are read from
+In addition to the main configuration file, drop\-in configuration snippets are read from
 /usr/lib/systemd/*\&.conf\&.d/,
 /usr/local/lib/systemd/*\&.conf\&.d/, and
 /etc/systemd/*\&.conf\&.d/\&. Those drop\-ins have higher precedence and override the main configuration file\&. Files in the
@@ -51,7 +67,12 @@ configuration subdirectories are sorted by their filename in lexicographic order
 When packages need to customize the configuration, they can install drop\-ins under
 /usr/\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defined a concept of drop\-in priority to allow distributions to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defines a concept of drop\-in priorities to allow OS vendors to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&. It is recommended to use the range 10\-40 for drop\-ins in
+/usr/
+and the range 60\-90 for drop\-ins in
+/etc/
+and
+/run/, to make sure that local and transient drop\-ins take priority over drop\-ins shipped by the OS vendor\&.
 .PP
 To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
diff --git a/upstream/fedora-rawhide/man5/repart.d.5 b/upstream/fedora-rawhide/man5/repart.d.5
index 17e247f9..c2f5ff87 100644
--- a/upstream/fedora-rawhide/man5/repart.d.5
+++ b/upstream/fedora-rawhide/man5/repart.d.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "REPART\&.D" "5" "" "systemd 255" "repart.d"
+.TH "REPART\&.D" "5" "" "systemd 256~rc3" "repart.d"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,12 +23,15 @@
 repart.d \- Partition Definition Files for Automatic Boot\-Time Repartitioning
 .SH "SYNOPSIS"
 .PP
-.nf
+.RS 4
 /etc/repart\&.d/*\&.conf
+.RE
+.RS 4
 /run/repart\&.d/*\&.conf
+.RE
+.RS 4
 /usr/lib/repart\&.d/*\&.conf
-    
-.fi
+.RE
 .SH "DESCRIPTION"
 .PP
 repart\&.d/*\&.conf
@@ -366,7 +369,7 @@ too\&. The logic is capable of automatically tracking down the backing partition
 "CopyBlocks=auto"
 is useful for implementing "self\-replicating" systems, i\&.e\&. systems that are their own installer\&.
 .sp
-The file specified here must have a size that is a multiple of the basic block size 512 and not be empty\&. If this option is used, the size allocation algorithm is slightly altered: the partition is created as least as big as required to fit the data in, i\&.e\&. the data size is an additional minimum size value taken into consideration for the allocation algorithm, similar to and in addition to the
+The file specified here must have a size that is a multiple of the basic block size 512 and not be empty\&. If this option is used, the size allocation algorithm is slightly altered: the partition is created at least as big as required to fit the data in, i\&.e\&. the data size is an additional minimum size value taken into consideration for the allocation algorithm, similar to and in addition to the
 \fISizeMin=\fR
 value configured above\&.
 .sp
@@ -390,7 +393,7 @@ Takes a file system name, such as
 "erofs",
 "squashfs"
 or the special value
-"swap"\&. If specified and the partition is newly created it is formatted with the specified file system (or as swap device)\&. The file system UUID and label are automatically derived from the partition UUID and label\&. If this option is used, the size allocation algorithm is slightly altered: the partition is created as least as big as required for the minimal file system of the specified type (or 4KiB if the minimal size is not known)\&.
+"swap"\&. If specified and the partition is newly created it is formatted with the specified file system (or as swap device)\&. The file system UUID and label are automatically derived from the partition UUID and label\&. If this option is used, the size allocation algorithm is slightly altered: the partition is created at least as big as required for the minimal file system of the specified type (or 4KiB if the minimal size is not known)\&.
 .sp
 This option has no effect if the partition already exists\&.
 .sp
@@ -539,6 +542,21 @@ Note that due to limitations of
 Added in version 255\&.
 .RE
 .PP
+\fIDefaultSubvolume=\fR
+.RS 4
+Takes an absolute path specifying the default subvolume within the new filesystem\&. Note that this setting does not create the subvolume itself, that can be configured with
+\fISubvolumes=\fR\&.
+.sp
+Note that this option only takes effect if the target filesystem supports subvolumes, such as
+"btrfs"\&.
+.sp
+Note that due to limitations of
+"mkfs\&.btrfs", this option is only supported when running with
+\fB\-\-offline=no\fR\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fIEncrypt=\fR
 .RS 4
 Takes one of
@@ -744,6 +762,41 @@ will have to populate the filesystem twice to guess the minimal required size, s
 .sp
 Added in version 253\&.
 .RE
+.PP
+\fIMountPoint=\fR
+.RS 4
+Specifies where and how the partition should be mounted\&. Takes at least one and at most two fields separated with a colon (":")\&. The first field specifies where the partition should be mounted\&. The second field specifies extra mount options to append to the default mount options\&. These fields correspond to the second and fourth column of the
+\fBfstab\fR(5)
+format\&. This setting may be specified multiple times to mount the partition multiple times\&. This can be used to add mounts for different btrfs subvolumes located on the same btrfs partition\&.
+.sp
+Note that this setting is only taken into account when
+\fB\-\-generate\-fstab=\fR
+is specified on the
+\fBsystemd\-repart\fR
+command line\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
+\fIEncryptedVolume=\fR
+.RS 4
+Specify how the encrypted partition should be set up\&. Takes at least one and at most three fields separated with a colon (":")\&. The first field specifies the encrypted volume name under
+/dev/mapper/\&. If not specified,
+"luks\-UUID"
+will be used where
+"UUID"
+is the LUKS UUID\&. The second field specifies the keyfile to use following the same format as specified in crypttab\&. The third field specifies a comma\-delimited list of crypttab options\&. These fields correspond to the first, third and fourth column of the
+\fBcrypttab\fR(5)
+format\&.
+.sp
+Note that this setting is only taken into account when
+\fB\-\-generate\-crypttab=\fR
+is specified on the
+\fBsystemd\-repart\fR
+command line\&.
+.sp
+Added in version 256\&.
+.RE
 .SH "SPECIFIERS"
 .PP
 Specifiers may be used in the
@@ -947,6 +1000,16 @@ The partition number assigned to the partition
 T}
 .TE
 .sp 1
+.SH "ENVIRONMENT"
+.PP
+Extra filesystem formatting options can be provided using filesystem\-specific environment variables:
+\fI$SYSTEMD_REPART_MKFS_OPTIONS_BTRFS\fR,
+\fI$SYSTEMD_REPART_MKFS_OPTIONS_XFS\fR,
+\fI$SYSTEMD_REPART_MKFS_OPTIONS_VFAT\fR,
+\fI$SYSTEMD_REPART_MKFS_OPTIONS_EROFS\fR, and
+\fI$SYSTEMD_REPART_MKFS_OPTIONS_SQUASHFS\fR\&. Each variable accepts valid
+\fBmkfs\&.\fR\fB\fIfilesystem\fR\fR
+command\-line arguments\&. The content of those variables is passed as\-is to the command, without any verification\&.
 .SH "EXAMPLES"
 .PP
 \fBExample\ \&1.\ \&Grow the root partition to the full disk size at first boot\fR
@@ -1101,10 +1164,7 @@ VerityMatchKey=root
 
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-repart\fR(8),
-\fBsfdisk\fR(8),
-\fBsystemd-cryptenroll\fR(1)
+\fBsystemd\fR(1), \fBsystemd-repart\fR(8), \fBsfdisk\fR(8), \fBsystemd-cryptenroll\fR(1)
 .SH "NOTES"
 .IP " 1." 4
 Discoverable Partitions Specification
diff --git a/upstream/fedora-rawhide/man5/repertoiremap.5 b/upstream/fedora-rawhide/man5/repertoiremap.5
index dd7781cb..0a1f19e9 100644
--- a/upstream/fedora-rawhide/man5/repertoiremap.5
+++ b/upstream/fedora-rawhide/man5/repertoiremap.5
@@ -1,6 +1,6 @@
 .\" SPDX-License-Identifier: GPL-2.0-or-later
 .\"
-.TH repertoiremap 5 2023-10-31 "Linux man-pages 6.06"
+.TH repertoiremap 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 repertoiremap \- map symbolic character names to Unicode code points
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/resolv.conf.5 b/upstream/fedora-rawhide/man5/resolv.conf.5
index 149f06dc..12103991 100644
--- a/upstream/fedora-rawhide/man5/resolv.conf.5
+++ b/upstream/fedora-rawhide/man5/resolv.conf.5
@@ -20,7 +20,7 @@
 .\"
 .\" Added ndots remark by Bernhard R. Link - debian bug #182886
 .\"
-.TH resolv.conf 5 2023-10-31 "Linux man-pages 6.06"
+.TH resolv.conf 5 2023-10-31 "Linux man-pages 6.7"
 .UC 4
 .SH NAME
 resolv.conf \- resolver configuration file
diff --git a/upstream/fedora-rawhide/man5/resolved.conf.5 b/upstream/fedora-rawhide/man5/resolved.conf.5
index cd0d5721..4979ca77 100644
--- a/upstream/fedora-rawhide/man5/resolved.conf.5
+++ b/upstream/fedora-rawhide/man5/resolved.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "RESOLVED\&.CONF" "5" "" "systemd 255" "resolved.conf"
+.TH "RESOLVED\&.CONF" "5" "" "systemd 256~rc3" "resolved.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,28 +23,39 @@
 resolved.conf, resolved.conf.d \- Network Name Resolution configuration files
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/systemd/resolved\&.conf
-.PP
+.RE
+.RS 4
+/run/systemd/resolved\&.conf
+.RE
+.RS 4
+/usr/lib/systemd/resolved\&.conf
+.RE
+.RS 4
 /etc/systemd/resolved\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /run/systemd/resolved\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /usr/lib/systemd/resolved\&.conf\&.d/*\&.conf
+.RE
 .SH "DESCRIPTION"
 .PP
 These configuration files control local DNS and LLMNR name resolution\&.
 .SH "CONFIGURATION DIRECTORIES AND PRECEDENCE"
 .PP
-The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is either in
-/usr/lib/systemd/
-or
-/etc/systemd/
-and contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
+The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is loaded from one of the listed directories in order of priority, only the first file found is used:
+/etc/systemd/,
+/run/systemd/,
+/usr/local/lib/systemd/,
+/usr/lib/systemd/\&. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can also be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
 /etc/
-if it\*(Aqs shipped in
-/usr/) however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
+if it\*(Aqs shipped under
+/usr/), however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
 .PP
-In addition to the "main" configuration file, drop\-in configuration snippets are read from
+In addition to the main configuration file, drop\-in configuration snippets are read from
 /usr/lib/systemd/*\&.conf\&.d/,
 /usr/local/lib/systemd/*\&.conf\&.d/, and
 /etc/systemd/*\&.conf\&.d/\&. Those drop\-ins have higher precedence and override the main configuration file\&. Files in the
@@ -54,7 +65,12 @@ configuration subdirectories are sorted by their filename in lexicographic order
 When packages need to customize the configuration, they can install drop\-ins under
 /usr/\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defined a concept of drop\-in priority to allow distributions to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defines a concept of drop\-in priorities to allow OS vendors to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&. It is recommended to use the range 10\-40 for drop\-ins in
+/usr/
+and the range 60\-90 for drop\-ins in
+/etc/
+and
+/run/, to make sure that local and transient drop\-ins take priority over drop\-ins shipped by the OS vendor\&.
 .PP
 To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -173,9 +189,7 @@ If set to true, all DNS lookups are DNSSEC\-validated locally (excluding LLMNR a
 If set to
 "allow\-downgrade", DNSSEC validation is attempted, but if the server does not support DNSSEC properly, DNSSEC mode is automatically disabled\&. Note that this mode makes DNSSEC validation vulnerable to "downgrade" attacks, where an attacker might be able to trigger a downgrade to non\-DNSSEC mode by synthesizing a DNS response that suggests DNSSEC was not supported\&.
 .sp
-If set to false, DNS lookups are not DNSSEC validated\&. In this mode, or when set to
-"allow\-downgrade"
-and the downgrade has happened, the resolver becomes security\-unaware and all forwarded queries have DNSSEC OK (DO) bit unset\&.
+If set to false, DNS lookups are not DNSSEC validated\&.
 .sp
 Note that DNSSEC validation requires retrieval of additional DNS data, and thus results in a small DNS lookup time penalty\&.
 .sp
@@ -366,11 +380,7 @@ Added in version 254\&.
 .RE
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-resolved.service\fR(8),
-\fBsystemd-networkd.service\fR(8),
-\fBdnssec-trust-anchors.d\fR(5),
-\fBresolv.conf\fR(5)
+\fBsystemd\fR(1), \fBsystemd-resolved.service\fR(8), \fBsystemd-networkd.service\fR(8), \fBdnssec-trust-anchors.d\fR(5), \fBresolv.conf\fR(5)
 .SH "NOTES"
 .IP " 1." 4
 RFC 4795
diff --git a/upstream/fedora-rawhide/man5/rpc.5 b/upstream/fedora-rawhide/man5/rpc.5
index 15277eff..bc67a347 100644
--- a/upstream/fedora-rawhide/man5/rpc.5
+++ b/upstream/fedora-rawhide/man5/rpc.5
@@ -5,7 +5,7 @@
 .\" %%%LICENSE_END
 .\"
 .\" @(#)rpc.5	2.2 88/08/03 4.0 RPCSRC; from 1.4 87/11/27 SMI;
-.TH rpc 5 2023-10-31 "Linux man-pages 6.06"
+.TH rpc 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 rpc \- RPC program number data base
 .SH SYNOPSIS
diff --git a/upstream/fedora-rawhide/man5/rsyncd.conf.5 b/upstream/fedora-rawhide/man5/rsyncd.conf.5
index 249edd46..ce91b49a 100644
--- a/upstream/fedora-rawhide/man5/rsyncd.conf.5
+++ b/upstream/fedora-rawhide/man5/rsyncd.conf.5
@@ -1,4 +1,4 @@
-.TH "rsyncd.conf" "5" "20 Oct 2022" "rsyncd.conf from rsync 3.2.7" "User Commands"
+.TH "rsyncd.conf" "5" "6 Apr 2024" "rsyncd.conf from rsync 3.3.0" "User Commands"
 .\" prefix=/usr
 .P
 .SH "NAME"
@@ -10,7 +10,9 @@ rsyncd.conf \- configuration file for rsync in daemon mode
 rsyncd.conf
 .P
 The online version of this manpage (that includes cross-linking of topics)
-is available at https://download.samba.org/pub/rsync/rsyncd.conf.5.
+is available at
+.UR https://download.samba.org/pub/rsync/rsyncd.conf.5
+.UE .
 .P
 .SH "DESCRIPTION"
 .P
@@ -85,25 +87,7 @@ reread the \fBrsyncd.conf\fP file. The file is re-read on each client connection
 .SH "GLOBAL PARAMETERS"
 .P
 The first parameters in the file (before a [module] header) are the global
-parameters.  Rsync also allows for the use of a "[global]" module name to
-indicate the start of one or more global-parameter sections (the name must be
-lower case).
-.P
-You may also include any module parameters in the global part of the config
-file in which case the supplied value will override the default for that
-parameter.
-.P
-You may use references to environment variables in the values of parameters.
-String parameters will have %VAR% references expanded as late as possible (when
-the string is first used in the program), allowing for the use of variables
-that rsync sets at connection time, such as RSYNC_USER_NAME.  Non-string
-parameters (such as true/false settings) are expanded when read from the config
-file.  If a variable does not exist in the environment, or if a sequence of
-characters is not a valid reference (such as an un-paired percent sign), the
-raw characters are passed through unchanged.  This helps with backward
-compatibility and safety (e.g. expanding a non-existent %VAR% to an empty
-string in a path could result in a very unsafe path).  The safest way to insert
-a literal % into a value is to use %%.
+parameters:
 .P
 .IP "\fBmotd\ file\fP"
 This parameter allows you to specify a "message of the day" (MOTD) to display
@@ -136,6 +120,22 @@ can also be specified via the \fB\-\-sockopts\fP command-line option.
 You can override the default backlog value when the daemon listens for
 connections.  It defaults to 5.
 .P
+You may also include any MODULE PARAMETERS in the global part of the
+config file, in which case the supplied value will override the default for
+that parameter.
+.P
+You may use references to environment variables in the values of parameters.
+String parameters will have %VAR% references expanded as late as possible (when
+the string is first used in the program), allowing for the use of variables
+that rsync sets at connection time, such as RSYNC_USER_NAME.  Non-string
+parameters (such as true/false settings) are expanded when read from the config
+file.  If a variable does not exist in the environment, or if a sequence of
+characters is not a valid reference (such as an un-paired percent sign), the
+raw characters are passed through unchanged.  This helps with backward
+compatibility and safety (e.g. expanding a non-existent %VAR% to an empty
+string in a path could result in a very unsafe path).  The safest way to insert
+a literal % into a value is to use %%.
+.P
 .SH "MODULE PARAMETERS"
 .P
 After the global parameters you should define a number of modules, each module
@@ -144,11 +144,17 @@ a module name in square brackets [module] followed by the parameters for that
 module.  The module name cannot contain a slash or a closing square bracket.
 If the name contains whitespace, each internal sequence of whitespace will be
 changed into a single space, while leading or trailing whitespace will be
-discarded.  Also, the name cannot be "global" as that exact name indicates that
-global parameters follow (see above).
+discarded.
+.P
+There is also a special module name of "[global]" that does not define a module
+but instead switches back to the global settings context where default
+parameters can be specified.  Because each defined module gets its full set of
+parameters as a combination of the default values that are set at that position
+in the config file plus its own parameter list, the use of a "[global]" section
+can help to maintain shared config values for multiple modules.
 .P
-As with GLOBAL PARAMETERS, you may use references to environment variables in
-the values of parameters.  See the GLOBAL PARAMETERS section for more details.
+As with GLOBAL PARAMETERS, you may use references to environment variables
+in the values of parameters.  See that section for details.
 .P
 .IP "\fBcomment\fP"
 This parameter specifies a description string that is displayed next to the
@@ -1021,7 +1027,7 @@ before it begins.  Any output from the \fBpre-xfer\ exec\fP command on stdout
 \fInot\fP displayed if the script returns success.  The other programs cannot
 send any text to the user.  All output except for the \fBpre-xfer\ exec\fP
 stdout goes to the corresponding daemon's stdout/stderr, which is typically
-discarded.  See the \fB\-\-no-detatch\fP option for a way to see the daemon's
+discarded.  See the \fB\-\-no-detach\fP option for a way to see the daemon's
 output, which can assist with debugging.
 .IP
 Note that the \fBearly\ exec\fP command runs before any part of the transfer
@@ -1284,19 +1290,25 @@ susan:herpass
 .SH "BUGS"
 .P
 Please report bugs! The rsync bug tracking system is online at
-https://rsync.samba.org/.
+.UR https://rsync.samba.org/
+.UE .
 .P
 .SH "VERSION"
 .P
-This manpage is current for version 3.2.7 of rsync.
+This manpage is current for version 3.3.0 of rsync.
 .P
 .SH "CREDITS"
 .P
 Rsync is distributed under the GNU General Public License.  See the file
 COPYING for details.
 .P
-An rsync web site is available at https://rsync.samba.org/ and its github
-project is https://github.com/WayneD/rsync.
+An rsync web site is available at
+.UR https://rsync.samba.org/
+.UE
+and its github
+project is
+.UR https://github.com/WayneD/rsync
+.UE .
 .P
 .SH "THANKS"
 .P
@@ -1310,4 +1322,5 @@ people have later contributed to it. It is currently maintained by Wayne
 Davison.
 .P
 Mailing lists for support and development are available at
-https://lists.samba.org/.
+.UR https://lists.samba.org/
+.UE .
diff --git a/upstream/fedora-rawhide/man5/securetty.5 b/upstream/fedora-rawhide/man5/securetty.5
index 279a81d6..d1ffbaa8 100644
--- a/upstream/fedora-rawhide/man5/securetty.5
+++ b/upstream/fedora-rawhide/man5/securetty.5
@@ -4,7 +4,7 @@
 .\" SPDX-License-Identifier: GPL-2.0-or-later
 .\"
 .\" Modified Sun Jul 25 11:06:27 1993 by Rik Faith (faith@cs.unc.edu)
-.TH securetty 5 2023-10-31 "Linux man-pages 6.06"
+.TH securetty 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 securetty \- list of terminals on which root is allowed to login
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/services.5 b/upstream/fedora-rawhide/man5/services.5
index 2442c6dc..eb83b3ef 100644
--- a/upstream/fedora-rawhide/man5/services.5
+++ b/upstream/fedora-rawhide/man5/services.5
@@ -11,7 +11,7 @@
 .\" Thu Jan 11 12:14:41 1996 Austin Donnelly  <and1000@cam.ac.uk>
 .\"   * Merged two services(5) manpages
 .\"
-.TH services 5 2023-10-31 "Linux man-pages 6.06"
+.TH services 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 services \- Internet network services list
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/shells.5 b/upstream/fedora-rawhide/man5/shells.5
index 7a6c6297..aaeaed70 100644
--- a/upstream/fedora-rawhide/man5/shells.5
+++ b/upstream/fedora-rawhide/man5/shells.5
@@ -6,7 +6,7 @@
 .\" Modified Sat Jul 24 17:11:07 1993 by Rik Faith (faith@cs.unc.edu)
 .\" Modified Sun Nov 21 10:49:38 1993 by Michael Haardt
 .\" Modified Sun Feb 26 15:09:15 1995 by Rik Faith (faith@cs.unc.edu)
-.TH shells 5 2023-10-31 "Linux man-pages 6.06"
+.TH shells 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 shells \- pathnames of valid login shells
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/slabinfo.5 b/upstream/fedora-rawhide/man5/slabinfo.5
index 51e02a48..73f7f9ed 100644
--- a/upstream/fedora-rawhide/man5/slabinfo.5
+++ b/upstream/fedora-rawhide/man5/slabinfo.5
@@ -3,7 +3,7 @@
 .\"
 .\" SPDX-License-Identifier: Linux-man-pages-copyleft
 .\"
-.TH slabinfo 5 2023-10-31 "Linux man-pages 6.06"
+.TH slabinfo 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 slabinfo \- kernel slab allocator statistics
 .SH SYNOPSIS
diff --git a/upstream/fedora-rawhide/man5/smb.conf.5 b/upstream/fedora-rawhide/man5/smb.conf.5
index 6de830fd..3b5626d6 100644
--- a/upstream/fedora-rawhide/man5/smb.conf.5
+++ b/upstream/fedora-rawhide/man5/smb.conf.5
@@ -2,12 +2,12 @@
 .\"     Title: smb.conf
 .\"    Author: [see the "AUTHOR" section]
 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
-.\"      Date: 02/26/2024
+.\"      Date: 05/08/2024
 .\"    Manual: File Formats and Conventions
-.\"    Source: Samba 4.20.0rc3
+.\"    Source: Samba 4.20.1
 .\"  Language: English
 .\"
-.TH "SMB\&.CONF" "5" "02/26/2024" "Samba 4\&.20\&.0rc3" "File Formats and Conventions"
+.TH "SMB\&.CONF" "5" "05/08/2024" "Samba 4\&.20\&.1" "File Formats and Conventions"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -3860,7 +3860,7 @@ dns update command (G)
 This option sets the command that is called when there are DNS updates\&. It should update the local machines DNS names using TSIG\-GSS\&.
 .sp
 Default:
-\fI\fIdns update command\fR\fR\fI = \fR\fI/builddir/build/BUILD/samba\-4\&.20\&.0rc3/source4/scripting/bin/samba_dnsupdate\fR\fI \fR
+\fI\fIdns update command\fR\fR\fI = \fR\fI/builddir/build/BUILD/samba\-4\&.20\&.1/source4/scripting/bin/samba_dnsupdate\fR\fI \fR
 .sp
 Example:
 \fI\fIdns update command\fR\fR\fI = \fR\fI/usr/local/sbin/dnsupdate\fR\fI \fR
@@ -4886,7 +4886,7 @@ gpo update command (G)
 This option sets the command that is called to apply GPO policies\&. The samba\-gpupdate script applies System Access and Kerberos Policies to the KDC\&. System Access policies set minPwdAge, maxPwdAge, minPwdLength, and pwdProperties in the samdb\&. Kerberos Policies set kdc:service ticket lifetime, kdc:user ticket lifetime, and kdc:renewal lifetime in smb\&.conf\&.
 .sp
 Default:
-\fI\fIgpo update command\fR\fR\fI = \fR\fI/builddir/build/BUILD/samba\-4\&.20\&.0rc3/source4/scripting/bin/samba\-gpupdate\fR\fI \fR
+\fI\fIgpo update command\fR\fR\fI = \fR\fI/builddir/build/BUILD/samba\-4\&.20\&.1/source4/scripting/bin/samba\-gpupdate\fR\fI \fR
 .sp
 Example:
 \fI\fIgpo update command\fR\fR\fI = \fR\fI/usr/local/sbin/gpoupdate\fR\fI \fR
@@ -11017,7 +11017,7 @@ samba_kcc
 was installed in a non\-default location\&.
 .sp
 Default:
-\fI\fIsamba kcc command\fR\fR\fI = \fR\fI/builddir/build/BUILD/samba\-4\&.20\&.0rc3/source4/scripting/bin/samba_kcc\fR\fI \fR
+\fI\fIsamba kcc command\fR\fR\fI = \fR\fI/builddir/build/BUILD/samba\-4\&.20\&.1/source4/scripting/bin/samba_kcc\fR\fI \fR
 .sp
 Example:
 \fI\fIsamba kcc command\fR\fR\fI = \fR\fI/usr/local/bin/kcc\fR\fI \fR
@@ -13021,7 +13021,7 @@ This option sets the command that for updating servicePrincipalName names from
 spn_update_list\&.
 .sp
 Default:
-\fI\fIspn update command\fR\fR\fI = \fR\fI/builddir/build/BUILD/samba\-4\&.20\&.0rc3/source4/scripting/bin/samba_spnupdate\fR\fI \fR
+\fI\fIspn update command\fR\fR\fI = \fR\fI/builddir/build/BUILD/samba\-4\&.20\&.1/source4/scripting/bin/samba_spnupdate\fR\fI \fR
 .sp
 Example:
 \fI\fIspn update command\fR\fR\fI = \fR\fI/usr/local/sbin/spnupdate\fR\fI \fR
@@ -14912,7 +14912,7 @@ and
 special sections make life for an administrator easy, but the various combinations of default attributes can be tricky\&. Take extreme care when designing these sections\&. In particular, ensure that the permissions on spool directories are correct\&.
 .SH "VERSION"
 .PP
-This man page is part of version 4\&.20\&.0rc3 of the Samba suite\&.
+This man page is part of version 4\&.20\&.1 of the Samba suite\&.
 .SH "SEE ALSO"
 .PP
 \fBsamba\fR(7),
diff --git a/upstream/fedora-rawhide/man5/smbpasswd.5 b/upstream/fedora-rawhide/man5/smbpasswd.5
index d18b9a61..b26cb58b 100644
--- a/upstream/fedora-rawhide/man5/smbpasswd.5
+++ b/upstream/fedora-rawhide/man5/smbpasswd.5
@@ -2,12 +2,12 @@
 .\"     Title: smbpasswd
 .\"    Author: [see the "AUTHOR" section]
 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
-.\"      Date: 02/26/2024
+.\"      Date: 05/08/2024
 .\"    Manual: File Formats and Conventions
-.\"    Source: Samba 4.20.0rc3
+.\"    Source: Samba 4.20.1
 .\"  Language: English
 .\"
-.TH "SMBPASSWD" "5" "02/26/2024" "Samba 4\&.20\&.0rc3" "File Formats and Conventions"
+.TH "SMBPASSWD" "5" "05/08/2024" "Samba 4\&.20\&.1" "File Formats and Conventions"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -165,7 +165,7 @@ This field consists of the time the account was last modified\&. It consists of
 All other colon separated fields are ignored at this time\&.
 .SH "VERSION"
 .PP
-This man page is part of version 4\&.20\&.0rc3 of the Samba suite\&.
+This man page is part of version 4\&.20\&.1 of the Samba suite\&.
 .SH "SEE ALSO"
 .PP
 \fBsmbpasswd\fR(8),
diff --git a/upstream/fedora-rawhide/man5/sysctl.d.5 b/upstream/fedora-rawhide/man5/sysctl.d.5
index 9b232b02..43455ab4 100644
--- a/upstream/fedora-rawhide/man5/sysctl.d.5
+++ b/upstream/fedora-rawhide/man5/sysctl.d.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSCTL\&.D" "5" "" "systemd 255" "sysctl.d"
+.TH "SYSCTL\&.D" "5" "" "systemd 256~rc3" "sysctl.d"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,11 +23,15 @@
 sysctl.d \- Configure kernel parameters at boot
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/sysctl\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /run/sysctl\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /usr/lib/sysctl\&.d/*\&.conf
+.RE
 .sp
 .nf
 key\&.name\&.under\&.proc\&.sys = some value
@@ -122,7 +126,12 @@ Packages should install their configuration files in
 /usr/local/lib/
 (local installs)\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. It is recommended to prefix all filenames with a two\-digit number and a dash, to simplify the ordering of the files\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. It is recommended to prefix all filenames with a two\-digit number and a dash, to simplify the ordering of the files\&. It is recommended to use the range 10\-40 for configuration files in
+/usr/
+and the range 60\-90 for configuration files in
+/etc/
+and
+/run/, to make sure that local and transient configuration files will always take priority over configuration files shipped by the OS vendor\&.
 .PP
 If the administrator wants to disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -237,9 +246,4 @@ will get this value (this also covers any interfaces detected while we\*(Aqre ru
 net\&.ipv4\&.conf\&.all\&.rp_filter, which we don\*(Aqt want to set at all, so it is explicitly excluded\&. And "hub0" is excluded from the glob because it has an explicit setting\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-sysctl.service\fR(8),
-\fBsystemd-delta\fR(1),
-\fBsysctl\fR(8),
-\fBsysctl.conf\fR(5),
-\fBmodprobe\fR(8)
+\fBsystemd\fR(1), \fBsystemd-sysctl.service\fR(8), \fBsystemd-delta\fR(1), \fBsysctl\fR(8), \fBsysctl.conf\fR(5), \fBmodprobe\fR(8)
diff --git a/upstream/fedora-rawhide/man5/sysfs.5 b/upstream/fedora-rawhide/man5/sysfs.5
index 7c18e4be..5a5237cc 100644
--- a/upstream/fedora-rawhide/man5/sysfs.5
+++ b/upstream/fedora-rawhide/man5/sysfs.5
@@ -2,7 +2,7 @@
 .\"
 .\" SPDX-License-Identifier: Linux-man-pages-copyleft
 .\"
-.TH sysfs 5 2023-10-31 "Linux man-pages 6.06"
+.TH sysfs 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 sysfs \- a filesystem for exporting kernel objects
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/systemd-sleep.conf.5 b/upstream/fedora-rawhide/man5/systemd-sleep.conf.5
index 20d3e071..0c81de64 100644
--- a/upstream/fedora-rawhide/man5/systemd-sleep.conf.5
+++ b/upstream/fedora-rawhide/man5/systemd-sleep.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\-SLEEP\&.CONF" "5" "" "systemd 255" "systemd-sleep.conf"
+.TH "SYSTEMD\-SLEEP\&.CONF" "5" "" "systemd 256~rc3" "systemd-sleep.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,13 +23,24 @@
 systemd-sleep.conf, sleep.conf.d \- Suspend and hibernation configuration file
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/systemd/sleep\&.conf
-.PP
+.RE
+.RS 4
+/run/systemd/sleep\&.conf
+.RE
+.RS 4
+/usr/lib/systemd/sleep\&.conf
+.RE
+.RS 4
 /etc/systemd/sleep\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /run/systemd/sleep\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /usr/lib/systemd/sleep\&.conf\&.d/*\&.conf
+.RE
 .SH "DESCRIPTION"
 .PP
 \fBsystemd\fR
@@ -89,16 +100,16 @@ attempts to suspend or hibernate the machine\&. See
 for a general description of the syntax\&.
 .SH "CONFIGURATION DIRECTORIES AND PRECEDENCE"
 .PP
-The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is either in
-/usr/lib/systemd/
-or
-/etc/systemd/
-and contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
+The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is loaded from one of the listed directories in order of priority, only the first file found is used:
+/etc/systemd/,
+/run/systemd/,
+/usr/local/lib/systemd/,
+/usr/lib/systemd/\&. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can also be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
 /etc/
-if it\*(Aqs shipped in
-/usr/) however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
+if it\*(Aqs shipped under
+/usr/), however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
 .PP
-In addition to the "main" configuration file, drop\-in configuration snippets are read from
+In addition to the main configuration file, drop\-in configuration snippets are read from
 /usr/lib/systemd/*\&.conf\&.d/,
 /usr/local/lib/systemd/*\&.conf\&.d/, and
 /etc/systemd/*\&.conf\&.d/\&. Those drop\-ins have higher precedence and override the main configuration file\&. Files in the
@@ -108,7 +119,12 @@ configuration subdirectories are sorted by their filename in lexicographic order
 When packages need to customize the configuration, they can install drop\-ins under
 /usr/\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defined a concept of drop\-in priority to allow distributions to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defines a concept of drop\-in priorities to allow OS vendors to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&. It is recommended to use the range 10\-40 for drop\-ins in
+/usr/
+and the range 60\-90 for drop\-ins in
+/etc/
+and
+/run/, to make sure that local and transient drop\-ins take priority over drop\-ins shipped by the OS vendor\&.
 .PP
 To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -142,6 +158,25 @@ can be used to override and enable those specific modes\&.
 Added in version 240\&.
 .RE
 .PP
+\fISuspendState=\fR
+.RS 4
+The string to be written to
+/sys/power/state
+by
+\fBsystemd-suspend.service\fR(8)\&. More than one value can be specified by separating multiple values with whitespace\&. They will be tried in turn, until one is written without error\&. If none of the writes succeed, the operation will be aborted\&.
+.sp
+The allowed set of values is determined by the kernel and is shown in the file itself (use
+\fBcat /sys/power/state\fR
+to display)\&. See
+\m[blue]\fBBasic sysfs Interfaces for System Suspend and Hibernation\fR\m[]\&\s-2\u[1]\d\s+2
+for more details\&.
+.sp
+\fBsystemd-suspend-then-hibernate.service\fR(8)
+uses this value when suspending\&.
+.sp
+Added in version 203\&.
+.RE
+.PP
 \fIHibernateMode=\fR
 .RS 4
 The string to be written to
@@ -163,23 +198,25 @@ when hibernating\&.
 Added in version 203\&.
 .RE
 .PP
-\fISuspendState=\fR
+\fIMemorySleepMode=\fR
 .RS 4
 The string to be written to
-/sys/power/state
-by
-\fBsystemd-suspend.service\fR(8)\&. More than one value can be specified by separating multiple values with whitespace\&. They will be tried in turn, until one is written without error\&. If none of the writes succeed, the operation will be aborted\&.
+/sys/power/mem_sleep
+when
+\fBSuspendState=mem\fR
+or
+\fBhybrid\-sleep\fR
+is used\&. More than one value can be specified by separating multiple values with whitespace\&. They will be tried in turn, until one is written without error\&. If none of the writes succeed, the operation will be aborted\&. Defaults to empty, i\&.e\&. the kernel default or kernel command line option
+\fImem_sleep_default=\fR
+is respected\&.
 .sp
 The allowed set of values is determined by the kernel and is shown in the file itself (use
-\fBcat /sys/power/state\fR
-to display)\&. See
+\fBcat /sys/power/mem_sleep\fR
+to display)\&. See the kernel documentation page
 \m[blue]\fBBasic sysfs Interfaces for System Suspend and Hibernation\fR\m[]\&\s-2\u[1]\d\s+2
 for more details\&.
 .sp
-\fBsystemd-suspend-then-hibernate.service\fR(8)
-uses this value when suspending\&.
-.sp
-Added in version 203\&.
+Added in version 256\&.
 .RE
 .PP
 \fIHibernateDelaySec=\fR
@@ -221,16 +258,10 @@ SuspendState=freeze
 .\}
 .SH "SEE ALSO"
 .PP
-\fBsystemd-sleep\fR(8),
-\fBsystemd-suspend.service\fR(8),
-\fBsystemd-hibernate.service\fR(8),
-\fBsystemd-hybrid-sleep.service\fR(8),
-\fBsystemd-suspend-then-hibernate.service\fR(8),
-\fBsystemd\fR(1),
-\fBsystemd.directives\fR(7)
+\fBsystemd-sleep\fR(8), \fBsystemd-suspend.service\fR(8), \fBsystemd-hibernate.service\fR(8), \fBsystemd-hybrid-sleep.service\fR(8), \fBsystemd-suspend-then-hibernate.service\fR(8), \fBsystemd\fR(1), \fBsystemd.directives\fR(7)
 .SH "NOTES"
 .IP " 1." 4
 Basic sysfs Interfaces for System Suspend and Hibernation
 .RS 4
-\%https://www.kernel.org/doc/html/latest/admin-guide/pm/sleep-states.html#basic-sysfs-interfaces-for-system-suspend-and-hibernation
+\%https://docs.kernel.org/admin-guide/pm/sleep-states.html#basic-sysfs-interfaces-for-system-suspend-and-hibernation
 .RE
diff --git a/upstream/fedora-rawhide/man5/systemd-system.conf.5 b/upstream/fedora-rawhide/man5/systemd-system.conf.5
index 6d2267c2..072da5ee 100644
--- a/upstream/fedora-rawhide/man5/systemd-system.conf.5
+++ b/upstream/fedora-rawhide/man5/systemd-system.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\-SYSTEM\&.CONF" "5" "" "systemd 255" "systemd-system.conf"
+.TH "SYSTEMD\-SYSTEM\&.CONF" "5" "" "systemd 256~rc3" "systemd-system.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -24,12 +24,16 @@ systemd-system.conf, system.conf.d, systemd-user.conf, user.conf.d \- System and
 .SH "SYNOPSIS"
 .PP
 /etc/systemd/system\&.conf,
+/run/systemd/system\&.conf,
+/usr/lib/systemd/system\&.conf,
 /etc/systemd/system\&.conf\&.d/*\&.conf,
 /run/systemd/system\&.conf\&.d/*\&.conf,
 /usr/lib/systemd/system\&.conf\&.d/*\&.conf
 .PP
 ~/\&.config/systemd/user\&.conf,
 /etc/systemd/user\&.conf,
+/run/systemd/user\&.conf,
+/usr/lib/systemd/user\&.conf,
 /etc/systemd/user\&.conf\&.d/*\&.conf,
 /run/systemd/user\&.conf\&.d/*\&.conf,
 /usr/lib/systemd/user\&.conf\&.d/*\&.conf
@@ -43,8 +47,10 @@ and the files in
 system\&.conf\&.d
 directories; when run as a user instance, it interprets the configuration file
 user\&.conf
-(either in the home directory of the user, or if not found, under
-/etc/systemd/) and the files in
+(in order of priority, in the home directory of the user and under
+/etc/systemd/,
+/run/systemd/, and
+/usr/lib/systemd/) and the files in
 user\&.conf\&.d
 directories\&. These configuration files contain a few settings controlling basic manager operations\&.
 .PP
@@ -53,16 +59,16 @@ See
 for a general description of the syntax\&.
 .SH "CONFIGURATION DIRECTORIES AND PRECEDENCE"
 .PP
-The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is either in
-/usr/lib/systemd/
-or
-/etc/systemd/
-and contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
+The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is loaded from one of the listed directories in order of priority, only the first file found is used:
+/etc/systemd/,
+/run/systemd/,
+/usr/local/lib/systemd/,
+/usr/lib/systemd/\&. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can also be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
 /etc/
-if it\*(Aqs shipped in
-/usr/) however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
+if it\*(Aqs shipped under
+/usr/), however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
 .PP
-In addition to the "main" configuration file, drop\-in configuration snippets are read from
+In addition to the main configuration file, drop\-in configuration snippets are read from
 /usr/lib/systemd/*\&.conf\&.d/,
 /usr/local/lib/systemd/*\&.conf\&.d/, and
 /etc/systemd/*\&.conf\&.d/\&. Those drop\-ins have higher precedence and override the main configuration file\&. Files in the
@@ -72,7 +78,12 @@ configuration subdirectories are sorted by their filename in lexicographic order
 When packages need to customize the configuration, they can install drop\-ins under
 /usr/\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defined a concept of drop\-in priority to allow distributions to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defines a concept of drop\-in priorities to allow OS vendors to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&. It is recommended to use the range 10\-40 for drop\-ins in
+/usr/
+and the range 60\-90 for drop\-ins in
+/etc/
+and
+/run/, to make sure that local and transient drop\-ins take priority over drop\-ins shipped by the OS vendor\&.
 .PP
 To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -82,7 +93,7 @@ in the configuration directory in
 .PP
 All options are configured in the [Manager] section:
 .PP
-\fILogColor=\fR, \fILogLevel=\fR, \fILogLocation=\fR, \fILogTarget=\fR, \fILogTime=\fR, \fIDumpCore=yes\fR, \fICrashChangeVT=no\fR, \fICrashShell=no\fR, \fICrashReboot=no\fR, \fIShowStatus=yes\fR, \fIDefaultStandardOutput=journal\fR, \fIDefaultStandardError=inherit\fR
+\fILogColor=\fR, \fILogLevel=\fR, \fILogLocation=\fR, \fILogTarget=\fR, \fILogTime=\fR, \fIDumpCore=yes\fR, \fICrashChangeVT=no\fR, \fICrashShell=no\fR, \fICrashAction=freeze\fR, \fIShowStatus=yes\fR, \fIDefaultStandardOutput=journal\fR, \fIDefaultStandardError=inherit\fR
 .RS 4
 Configures various parameters of basic manager operation\&. These options may be overridden by the respective process and kernel command line arguments\&. See
 \fBsystemd\fR(1)
@@ -263,6 +274,24 @@ Takes a boolean argument\&. If true, ensures that PID 1 and all its children can
 Added in version 239\&.
 .RE
 .PP
+\fIProtectSystem=\fR
+.RS 4
+Takes a boolean argument or the string
+"auto"\&. If set to true this will remount
+/usr/
+read\-only\&. If set to
+"auto"
+(the default) and running in an initrd equivalent to true, otherwise false\&. This implements a restricted subset of the per\-unit setting of the same name, see
+\fBsystemd.exec\fR(5)
+for details: currently, the
+"full"
+or
+"struct"
+values are not supported\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fISystemCallArchitectures=\fR
 .RS 4
 Takes a space\-separated list of architecture identifiers\&. Selects from which architectures system calls may be invoked on this system\&. This may be used as an effective way to disable invocation of non\-native binaries system\-wide, for example to prohibit execution of 32\-bit x86 binaries on 64\-bit x86\-64 systems\&. This option operates system\-wide, and acts similar to the
@@ -588,11 +617,11 @@ Added in version 252\&.
 .PP
 \fIReloadLimitIntervalSec=\fR, \fIReloadLimitBurst=\fR
 .RS 4
-Rate limiting for daemon\-reload requests\&. Default to unset, and any number of daemon\-reload operations can be requested at any time\&.
+Rate limiting for daemon\-reload and (since v256) daemon\-reexec requests\&. The setting applies to both operations, but the rate limits are tracked separately\&. Defaults to unset, and any number of operations can be requested at any time\&.
 \fIReloadLimitIntervalSec=\fR
 takes a value in seconds to configure the rate limit window, and
 \fIReloadLimitBurst=\fR
-takes a positive integer to configure the maximum allowed number of reloads within the configured time window\&.
+takes a positive integer to configure the maximum allowed number of operations within the configured time window\&.
 .sp
 Added in version 253\&.
 .RE
@@ -818,12 +847,7 @@ Added in version 252\&.
 .RE
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd.directives\fR(7),
-\fBsystemd.exec\fR(5),
-\fBsystemd.service\fR(5),
-\fBenviron\fR(7),
-\fBcapabilities\fR(7)
+\fBsystemd\fR(1), \fBsystemd.directives\fR(7), \fBsystemd.exec\fR(5), \fBsystemd.service\fR(5), \fBenviron\fR(7), \fBcapabilities\fR(7)
 .SH "NOTES"
 .IP " 1." 4
 No New Privileges Flag
diff --git a/upstream/fedora-rawhide/man5/systemd.automount.5 b/upstream/fedora-rawhide/man5/systemd.automount.5
index b61efb9a..1ba25d77 100644
--- a/upstream/fedora-rawhide/man5/systemd.automount.5
+++ b/upstream/fedora-rawhide/man5/systemd.automount.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.AUTOMOUNT" "5" "" "systemd 255" "systemd.automount"
+.TH "SYSTEMD\&.AUTOMOUNT" "5" "" "systemd 256~rc3" "systemd.automount"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -183,10 +183,4 @@ Check
 for more settings\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemctl\fR(1),
-\fBsystemd.unit\fR(5),
-\fBsystemd.mount\fR(5),
-\fBmount\fR(8),
-\fBautomount\fR(8),
-\fBsystemd.directives\fR(7)
+\fBsystemd\fR(1), \fBsystemctl\fR(1), \fBsystemd.unit\fR(5), \fBsystemd.mount\fR(5), \fBmount\fR(8), \fBautomount\fR(8), \fBsystemd.directives\fR(7)
diff --git a/upstream/fedora-rawhide/man5/systemd.device.5 b/upstream/fedora-rawhide/man5/systemd.device.5
index 6d6744c4..7c240275 100644
--- a/upstream/fedora-rawhide/man5/systemd.device.5
+++ b/upstream/fedora-rawhide/man5/systemd.device.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.DEVICE" "5" "" "systemd 255" "systemd.device"
+.TH "SYSTEMD\&.DEVICE" "5" "" "systemd 256~rc3" "systemd.device"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -131,8 +131,4 @@ Device unit files may include [Unit] and [Install] sections, which are described
 \fBsystemd.unit\fR(5)\&. No options specific to this file type are supported\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemctl\fR(1),
-\fBsystemd.unit\fR(5),
-\fBudev\fR(7),
-\fBsystemd.directives\fR(7)
+\fBsystemd\fR(1), \fBsystemctl\fR(1), \fBsystemd.unit\fR(5), \fBudev\fR(7), \fBsystemd.directives\fR(7)
diff --git a/upstream/fedora-rawhide/man5/systemd.dnssd.5 b/upstream/fedora-rawhide/man5/systemd.dnssd.5
index 708d02ca..1b719a77 100644
--- a/upstream/fedora-rawhide/man5/systemd.dnssd.5
+++ b/upstream/fedora-rawhide/man5/systemd.dnssd.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.DNSSD" "5" "" "systemd 255" "systemd.dnssd"
+.TH "SYSTEMD\&.DNSSD" "5" "" "systemd 256~rc3" "systemd.dnssd"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -207,6 +207,15 @@ A type of the network service as defined in the section 4\&.1\&.2 of
 Added in version 236\&.
 .RE
 .PP
+\fISubType=\fR
+.RS 4
+A subtype of the network service as defined in the section 7\&.1 of
+\m[blue]\fBRFC 6763\fR\m[]\&\s-2\u[1]\d\s+2, e\&.g\&.
+"_printer"\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fIPort=\fR
 .RS 4
 An IP port number of the network service\&.
@@ -325,9 +334,7 @@ $ avahi\-browse \-a \-r
 .\}
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-resolved.service\fR(8),
-\fBresolvectl\fR(1)
+\fBsystemd\fR(1), \fBsystemd-resolved.service\fR(8), \fBresolvectl\fR(1)
 .SH "NOTES"
 .IP " 1." 4
 RFC 6763
diff --git a/upstream/fedora-rawhide/man5/systemd.exec.5 b/upstream/fedora-rawhide/man5/systemd.exec.5
index 3e30d6d5..c08fb7a7 100644
--- a/upstream/fedora-rawhide/man5/systemd.exec.5
+++ b/upstream/fedora-rawhide/man5/systemd.exec.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.EXEC" "5" "" "systemd 255" "systemd.exec"
+.TH "SYSTEMD\&.EXEC" "5" "" "systemd 256~rc3" "systemd.exec"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -171,10 +171,10 @@ is relative to the root of the system running the service manager\&. Note that s
 \fIRootDirectory=\fR
 .RS 4
 Takes a directory path relative to the host\*(Aqs root directory (i\&.e\&. the root of the system running the service manager)\&. Sets the root directory for executed processes, with the
+\fBpivot_root\fR(2)
+or
 \fBchroot\fR(2)
-system call\&. If this is used, it must be ensured that the process binary and all its auxiliary files are available in the
-\fBchroot()\fR
-jail\&. Note that setting this parameter might result in additional dependencies to be added to the unit (see above)\&.
+system call\&. If this is used, it must be ensured that the process binary and all its auxiliary files are available in the new root\&. Note that setting this parameter might result in additional dependencies to be added to the unit (see above)\&.
 .sp
 The
 \fIMountAPIVFS=\fR
@@ -211,6 +211,12 @@ BindReadOnlyPaths=/dev/log /run/systemd/journal/socket /run/systemd/journal/stdo
 .RE
 .\}
 
+In place of the directory path a
+"\&.v/"
+versioned directory may be specified, see
+\fBsystemd.v\fR(7)
+for details\&.
+.sp
 This option is only available for system services, or for services running in per\-user instances of the service manager in which case
 \fIPrivateUsers=\fR
 is implicitly enabled (requires unprivileged user namespaces support to be enabled in the kernel via the
@@ -268,6 +274,12 @@ file will be made available for the service (read\-only) as
 /run/host/os\-release\&. It will be updated automatically on soft reboot (see:
 \fBsystemd-soft-reboot.service\fR(8)), in case the service is configured to survive it\&.
 .sp
+In place of the image path a
+"\&.v/"
+versioned directory may be specified, see
+\fBsystemd.v\fR(7)
+for details\&.
+.sp
 This option is only available for system services and is not supported for services running in per\-user instances of the service manager\&.
 .sp
 Added in version 233\&.
@@ -549,6 +561,10 @@ creates regular writable bind mounts (unless the source file system mount is alr
 \fIBindReadOnlyPaths=\fR
 creates read\-only bind mounts\&. These settings may be used more than once, each usage appends to the unit\*(Aqs list of bind mounts\&. If the empty string is assigned to either of these two options the entire list of bind mounts defined prior to this is reset\&. Note that in this case both read\-only and regular bind mounts are reset, regardless which of the two settings is used\&.
 .sp
+Using this option implies that a mount namespace is allocated for the unit, i\&.e\&. it implies the effect of
+\fIPrivateMounts=\fR
+(see below)\&.
+.sp
 This option is particularly useful when
 \fIRootDirectory=\fR/\fIRootImage=\fR
 is used\&. In this case the source path refers to a path on the host file system, while the destination path refers to a path below the root directory of the unit\&.
@@ -696,6 +712,12 @@ or
 below, as it may change the setting of
 \fIDevicePolicy=\fR\&.
 .sp
+In place of the image path a
+"\&.v/"
+versioned directory may be specified, see
+\fBsystemd.v\fR(7)
+for details\&.
+.sp
 This option is only available for system services and is not supported for services running in per\-user instances of the service manager\&.
 .sp
 Added in version 248\&.
@@ -733,6 +755,12 @@ or the host\&. See:
 .sp
 Note that usage from user units requires overlayfs support in unprivileged user namespaces, which was first introduced in kernel v5\&.11\&.
 .sp
+In place of the directory path a
+"\&.v/"
+versioned directory may be specified, see
+\fBsystemd.v\fR(7)
+for details\&.
+.sp
 This option is only available for system services, or for services running in per\-user instances of the service manager in which case
 \fIPrivateUsers=\fR
 is implicitly enabled (requires unprivileged user namespaces support to be enabled in the kernel via the
@@ -837,17 +865,22 @@ Sets the supplementary Unix groups the processes are executed as\&. This takes a
 .PP
 \fISetLoginEnvironment=\fR
 .RS 4
-Takes a boolean parameter that controls whether to set
+Takes a boolean parameter that controls whether to set the
 \fI$HOME\fR,
 \fI$LOGNAME\fR, and
 \fI$SHELL\fR
-environment variables\&. If unset, this is controlled by whether
-\fIUser=\fR
-is set\&. If true, they will always be set for system services, i\&.e\&. even when the default user
+environment variables\&. If not set, this defaults to true if
+\fIUser=\fR,
+\fIDynamicUser=\fR
+or
+\fIPAMName=\fR
+are set, false otherwise\&. If set to true, the variables will always be set for system services, i\&.e\&. even when the default user
 "root"
-is used\&. If false, the mentioned variables are not set by systemd, no matter whether
-\fIUser=\fR
-is used or not\&. This option normally has no effect on user services, since these variables are typically inherited from user manager\*(Aqs own environment anyway\&.
+is used\&. If set to false, the mentioned variables are not set by the service manager, no matter whether
+\fIUser=\fR,
+\fIDynamicUser=\fR, or
+\fIPAMName=\fR
+are used or not\&. This option normally has no effect on services of the per\-user service manager, since in that case these variables are typically inherited from user manager\*(Aqs own environment anyway\&.
 .sp
 Added in version 255\&.
 .RE
@@ -1410,11 +1443,11 @@ Added in version 209\&.
 .PP
 \fIIgnoreSIGPIPE=\fR
 .RS 4
-Takes a boolean argument\&. If true, causes
+Takes a boolean argument\&. If true,
 \fBSIGPIPE\fR
-to be ignored in the executed process\&. Defaults to true because
+is ignored in the executed process\&. Defaults to true since
 \fBSIGPIPE\fR
-generally is useful only in shell pipelines\&.
+is generally only useful in shell pipelines\&.
 .RE
 .SH "SCHEDULING"
 .PP
@@ -1532,6 +1565,12 @@ Also note that some sandboxing functionality is generally not available in user
 \fIProtectSystem=\fR) are not available, as the underlying kernel functionality is only accessible to privileged processes\&. However, most namespacing settings, that will not work on their own in user services, will work when used in conjunction with
 \fIPrivateUsers=\fR\fBtrue\fR\&.
 .PP
+Note that the various options that turn directories read\-only (such as
+\fIProtectSystem=\fR,
+\fIReadOnlyPaths=\fR, \&...) do not affect the ability for programs to connect to and communicate with
+\fBAF_UNIX\fR
+sockets in these directories\&. These options cannot be used to lock down access to IPC services hence\&.
+.PP
 \fIProtectSystem=\fR
 .RS 4
 Takes a boolean argument or the special values
@@ -1556,7 +1595,10 @@ and
 \fIProtectKernelTunables=\fR,
 \fIProtectControlGroups=\fR)\&. This setting ensures that any modification of the vendor\-supplied operating system (and optionally its configuration, and local mounts) is prohibited for the service\&. It is recommended to enable this setting for all long\-running services, unless they are involved with system updates or need to modify the operating system in other ways\&. If this option is used,
 \fIReadWritePaths=\fR
-may be used to exclude specific directories from being made read\-only\&. This setting is implied if
+may be used to exclude specific directories from being made read\-only\&. Similar,
+\fIStateDirectory=\fR,
+\fILogsDirectory=\fR, \&... and related directory settings (see below) also exclude the specific directories from the effect of
+\fIProtectSystem=\fR\&. This setting is implied if
 \fIDynamicUser=\fR
 is set\&. This setting cannot ensure protection in all cases\&. In general it has the same limitations as
 \fIReadOnlyPaths=\fR, see below\&. Defaults to off\&.
@@ -2790,14 +2832,15 @@ and
 directories\&.
 .sp
 Other file system namespace unit settings \(em
-\fIPrivateMounts=\fR,
 \fIPrivateTmp=\fR,
 \fIPrivateDevices=\fR,
 \fIProtectSystem=\fR,
 \fIProtectHome=\fR,
 \fIReadOnlyPaths=\fR,
 \fIInaccessiblePaths=\fR,
-\fIReadWritePaths=\fR, \&... \(em also enable file system namespacing in a fashion equivalent to this option\&. Hence it is primarily useful to explicitly request this behaviour if none of the other settings are used\&.
+\fIReadWritePaths=\fR,
+\fIBindPaths=\fR,
+\fIBindReadOnlyPaths=\fR, \&... \(em also enable file system namespacing in a fashion equivalent to this option\&. Hence it is primarily useful to explicitly request this behaviour if none of the other settings are used\&.
 .sp
 This option is only available for system services, or for services running in per\-user instances of the service manager in which case
 \fIPrivateUsers=\fR
@@ -3481,7 +3524,7 @@ The
 option may be used to connect a specific file system object to standard output\&. The semantics are similar to the same option of
 \fIStandardInput=\fR, see above\&. If
 \fIpath\fR
-refers to a regular file on the filesystem, it is opened (created if it doesn\*(Aqt exist yet) for writing at the beginning of the file, but without truncating it\&. If standard input and output are directed to the same file path, it is opened only once \(em for reading as well as writing \(em and duplicated\&. This is particularly useful when the specified path refers to an
+refers to a regular file on the filesystem, it is opened (created if it doesn\*(Aqt exist yet using privileges of the user executing the systemd process) for writing at the beginning of the file, but without truncating it\&. If standard input and output are directed to the same file path, it is opened only once \(em for reading as well as writing \(em and duplicated\&. This is particularly useful when the specified path refers to an
 \fBAF_UNIX\fR
 socket in the file system, as in that case only a single stream connection is created for both input and output\&.
 .sp
@@ -3543,7 +3586,7 @@ on
 systemd\-journald\&.socket
 (also see the "Implicit Dependencies" section above)\&. Also note that in this case stdout (or stderr, see below) will be an
 \fBAF_UNIX\fR
-stream socket, and not a pipe or FIFO that can be re\-opened\&. This means when executing shell scripts the construct
+stream socket, and not a pipe or FIFO that can be reopened\&. This means when executing shell scripts the construct
 \fBecho "hello" > /dev/stderr\fR
 for writing text to stderr will not work\&. To mitigate this use the construct
 \fBecho "hello" >&2\fR
@@ -3678,6 +3721,8 @@ separated by whitespace\&. See
 for details on the journal field concept\&. Even though the underlying journal implementation permits binary field values, this setting accepts only valid UTF\-8 values\&. To include space characters in a journal field value, enclose the assignment in double quotes (")\&.
 The usual specifiers are expanded in all assignments (see below)\&. Note that this setting is not only useful for attaching additional metadata to log records of a unit, but given that all fields and values are indexed may also be used to implement cross\-unit log record matching\&. Assign an empty string to reset the list\&.
 .sp
+Note that this functionality is currently only available in system services, not in per\-user services\&.
+.sp
 Added in version 236\&.
 .RE
 .PP
@@ -3727,7 +3772,7 @@ would add a pattern matching
 "~foobar"
 to the allow list\&.
 .sp
-Log messages are tested against denied patterns (if any), then against allowed patterns (if any)\&. If a log message matches any of the denied patterns, it will be discarded, whatever the allowed patterns\&. Then, remaining log messages are tested against allowed patterns\&. Messages matching against none of the allowed pattern are discarded\&. If no allowed patterns are defined, then all messages are processed directly after going through denied filters\&.
+Log messages are tested against denied patterns (if any), then against allowed patterns (if any)\&. If a log message matches any of the denied patterns, it is discarded immediately without considering allowed patterns\&. Remaining log messages are tested against allowed patterns\&. Messages matching against none of the allowed pattern are discarded\&. If no allowed patterns are defined, then all messages are processed directly after going through denied filters\&.
 .sp
 Filtering is based on the unit for which
 \fILogFilterPatterns=\fR
@@ -3735,6 +3780,8 @@ is defined, meaning log messages coming from
 \fBsystemd\fR(1)
 about the unit are not taken into account\&. Filtered log messages won\*(Aqt be forwarded to traditional syslog daemons, the kernel log buffer (kmsg), the systemd console, or sent as wall messages to all logged\-in users\&.
 .sp
+Note that this functionality is currently only available in system services, not in per\-user services\&.
+.sp
 Added in version 253\&.
 .RE
 .PP
@@ -3934,6 +3981,8 @@ are searched as well\&.
 .sp
 If the file system path is omitted it is chosen identical to the credential name, i\&.e\&. this is a terse way to declare credentials to inherit from the service manager into a service\&. This option may be used multiple times, each time defining an additional credential to pass to the unit\&.
 .sp
+Note that if the path is not specified or a valid credential identifier is given, i\&.e\&. in the above two cases, a missing credential is not considered fatal\&.
+.sp
 If an absolute path referring to a directory is specified, every file in that directory (recursively) will be loaded as a separate credential\&. The ID for each credential will be the provided ID suffixed with
 "_$FILENAME"
 (e\&.g\&.,
@@ -3973,6 +4022,11 @@ for the details about
 or
 \fIDeviceAllow=\fR\&.
 .sp
+Note that encrypted credentials targeted for services of the per\-user service manager must be encrypted with
+\fBsystemd\-creds encrypt \-\-user\fR, and those for the system service manager without the
+\fB\-\-user\fR
+switch\&. Encrypted credentials are always targeted to a specific user or the system as a whole, and it is ensured that per\-user service managers cannot decrypt secrets intended for the system or for other users\&.
+.sp
 The credential files/IPC sockets must be accessible to the service manager, but don\*(Aqt have to be directly accessible to the unit\*(Aqs processes: the credential data is read and copied into separate, read\-only copies for the unit that are accessible to appropriately privileged processes\&. This is particularly useful in combination with
 \fIDynamicUser=\fR
 as this way privileged data can be made available to processes running under a dynamic UID (i\&.e\&. not a previously known one) without having to open up access to all users\&.
@@ -5547,23 +5601,7 @@ MONITOR_UNIT=mysuccess\&.service
 .\}
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemctl\fR(1),
-\fBsystemd-analyze\fR(1),
-\fBjournalctl\fR(1),
-\fBsystemd-system.conf\fR(5),
-\fBsystemd.unit\fR(5),
-\fBsystemd.service\fR(5),
-\fBsystemd.socket\fR(5),
-\fBsystemd.swap\fR(5),
-\fBsystemd.mount\fR(5),
-\fBsystemd.kill\fR(5),
-\fBsystemd.resource-control\fR(5),
-\fBsystemd.time\fR(7),
-\fBsystemd.directives\fR(7),
-\fBtmpfiles.d\fR(5),
-\fBexec\fR(3),
-\fBfork\fR(2)
+\fBsystemd\fR(1), \fBsystemctl\fR(1), \fBsystemd-analyze\fR(1), \fBjournalctl\fR(1), \fBsystemd-system.conf\fR(5), \fBsystemd.unit\fR(5), \fBsystemd.service\fR(5), \fBsystemd.socket\fR(5), \fBsystemd.swap\fR(5), \fBsystemd.mount\fR(5), \fBsystemd.kill\fR(5), \fBsystemd.resource-control\fR(5), \fBsystemd.time\fR(7), \fBsystemd.directives\fR(7), \fBtmpfiles.d\fR(5), \fBexec\fR(3), \fBfork\fR(2)
 .SH "NOTES"
 .IP " 1." 4
 Discoverable Partitions Specification
diff --git a/upstream/fedora-rawhide/man5/systemd.kill.5 b/upstream/fedora-rawhide/man5/systemd.kill.5
index f8379e5f..57b5de8c 100644
--- a/upstream/fedora-rawhide/man5/systemd.kill.5
+++ b/upstream/fedora-rawhide/man5/systemd.kill.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.KILL" "5" "" "systemd 255" "systemd.kill"
+.TH "SYSTEMD\&.KILL" "5" "" "systemd 256~rc3" "systemd.kill"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -211,15 +211,4 @@ Added in version 240\&.
 .RE
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemctl\fR(1),
-\fBjournalctl\fR(1),
-\fBsystemd.unit\fR(5),
-\fBsystemd.service\fR(5),
-\fBsystemd.socket\fR(5),
-\fBsystemd.swap\fR(5),
-\fBsystemd.mount\fR(5),
-\fBsystemd.exec\fR(5),
-\fBsystemd.directives\fR(7),
-\fBkill\fR(2),
-\fBsignal\fR(7)
+\fBsystemd\fR(1), \fBsystemctl\fR(1), \fBjournalctl\fR(1), \fBsystemd.unit\fR(5), \fBsystemd.service\fR(5), \fBsystemd.socket\fR(5), \fBsystemd.swap\fR(5), \fBsystemd.mount\fR(5), \fBsystemd.exec\fR(5), \fBsystemd.directives\fR(7), \fBkill\fR(2), \fBsignal\fR(7)
diff --git a/upstream/fedora-rawhide/man5/systemd.link.5 b/upstream/fedora-rawhide/man5/systemd.link.5
index 359f1911..63d7e08e 100644
--- a/upstream/fedora-rawhide/man5/systemd.link.5
+++ b/upstream/fedora-rawhide/man5/systemd.link.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.LINK" "5" "" "systemd 255" "systemd.link"
+.TH "SYSTEMD\&.LINK" "5" "" "systemd 256~rc3" "systemd.link"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -345,6 +345,97 @@ A description of the device\&.
 Added in version 211\&.
 .RE
 .PP
+\fIProperty=\fR
+.RS 4
+Set specified udev properties\&. This takes space separated list of key\-value pairs concatenated with equal sign ("=")\&. Example:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+Property=HOGE=foo BAR=baz
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+This option supports simple specifier expansion, see the Specifiers section below\&. This option can be specified multiple times\&. If an empty string is assigned, then the all previous assignments are cleared\&.
+.sp
+This setting is useful to configure the
+"ID_NET_MANAGED_BY="
+property which declares which network management service shall manage the interface, which is respected by systemd\-networkd and others\&. Use
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+Property=ID_NET_MANAGED_BY=io\&.systemd\&.Network
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+to declare explicitly that
+\fBsystemd\-networkd\fR
+shall manage the interface, or set the property to something else to declare explicitly it shall not do so\&. See
+\fBsystemd.network\fR(5)
+for details how this property is used to match interface names\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
+\fIImportProperty=\fR
+.RS 4
+Import specified udev properties from the saved database\&. This takes space separated list of property names\&. Example:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+ImportProperty=HOGE BAR
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+This option supports simple specifier expansion, see the Specifiers section below\&. This option can be specified multiple times\&. If an empty string is assigned, then the all previous assignments are cleared\&.
+.sp
+If the same property is also set in
+\fIProperty=\fR
+in the above, then the imported property value will be overridden by the value specified in
+\fIProperty=\fR\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
+\fIUnsetProperty=\fR
+.RS 4
+Unset specified udev properties\&. This takes space separated list of property names\&. Example:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+ImportProperty=HOGE BAR
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+This option supports simple specifier expansion, see the Specifiers section below\&. This option can be specified multiple times\&. If an empty string is assigned, then the all previous assignments are cleared\&.
+.sp
+This setting is applied after
+\fIImportProperty=\fR
+and
+\fIProperty=\fR
+are applied\&. Hence, if the same property is specified in
+\fIImportProperty=\fR
+or
+\fIProperty=\fR, then the imported or specified property value will be ignored, and the property will be unset\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fIAlias=\fR
 .RS 4
 The
@@ -493,7 +584,7 @@ and
 "%"\&. While
 "\&."
 is an allowed character, it\*(Aqs recommended to avoid it when naming interfaces as various tools (such as
-\fBresolvconf\fR(1)) use it as separator character\&. Also, fully numeric interface names are not allowed (in order to avoid ambiguity with interface specification by numeric indexes), as are the special strings
+\fBresolvconf\fR(1)) use it as separator character\&. Also, fully numeric interface names are not allowed (in order to avoid ambiguity with interface specification by numeric indexes), nor are the special strings
 "\&.",
 "\&.\&.",
 "all"
@@ -1584,6 +1675,17 @@ Takes a boolean\&. If set to true, Large Receive Offload (LRO) is enabled\&. Whe
 Added in version 232\&.
 .RE
 .PP
+\fIReceivePacketSteeringCPUMask=\fR
+.RS 4
+Configures Receive Packet Steering (RPS) list of CPUs to which RPS may forward traffic\&. Takes a list of CPU indices or ranges separated by either whitespace or commas\&. Alternatively, takes the special value
+"all"
+in which will include all available CPUs in the mask\&. CPU ranges are specified by the lower and upper CPU indices separated by a dash (e\&.g\&.
+"2\-6")\&. This option may be specified more than once, in which case the specified CPU affinity masks are merged\&. If an empty string is assigned, the mask is reset, all assignments prior to this will have no effect\&. Defaults to unset and RPS CPU list is unchanged\&. To disable RPS when it was previously enabled, use the special value
+"disable"\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fIReceiveVLANCTAGHardwareAcceleration=\fR
 .RS 4
 Takes a boolean\&. If set to true, receive VLAN CTAG hardware acceleration is enabled\&. When unset, the kernel\*(Aqs default will be used\&.
@@ -1828,6 +1930,148 @@ Specifies the MAC address for the virtual function\&.
 .sp
 Added in version 251\&.
 .RE
+.SH "SPECIFIERS"
+.PP
+Some settings resolve specifiers which may be used to write generic unit files referring to runtime or unit parameters that are replaced when the unit files are loaded\&. Specifiers must be known and resolvable for the setting to be valid\&. The following specifiers are understood:
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+.B Table\ \&2.\ \&Specifiers available in unit files
+.TS
+allbox tab(:);
+lB lB lB.
+T{
+Specifier
+T}:T{
+Meaning
+T}:T{
+Details
+T}
+.T&
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l.
+T{
+"%a"
+T}:T{
+Architecture
+T}:T{
+A short string identifying the architecture of the local system\&. A string such as \fBx86\fR, \fBx86\-64\fR or \fBarm64\fR\&. See the architectures defined for \fIConditionArchitecture=\fR in \fBsystemd.unit\fR(5) for a full list\&.
+T}
+T{
+"%A"
+T}:T{
+Operating system image version
+T}:T{
+The operating system image version identifier of the running system, as read from the \fIIMAGE_VERSION=\fR field of /etc/os\-release\&. If not set, resolves to an empty string\&. See \fBos-release\fR(5) for more information\&.
+T}
+T{
+"%b"
+T}:T{
+Boot ID
+T}:T{
+The boot ID of the running system, formatted as string\&. See \fBrandom\fR(4) for more information\&.
+T}
+T{
+"%B"
+T}:T{
+Operating system build ID
+T}:T{
+The operating system build identifier of the running system, as read from the \fIBUILD_ID=\fR field of /etc/os\-release\&. If not set, resolves to an empty string\&. See \fBos-release\fR(5) for more information\&.
+T}
+T{
+"%H"
+T}:T{
+Host name
+T}:T{
+The hostname of the running system\&.
+T}
+T{
+"%l"
+T}:T{
+Short host name
+T}:T{
+The hostname of the running system, truncated at the first dot to remove any domain component\&.
+T}
+T{
+"%m"
+T}:T{
+Machine ID
+T}:T{
+The machine ID of the running system, formatted as string\&. See \fBmachine-id\fR(5) for more information\&.
+T}
+T{
+"%M"
+T}:T{
+Operating system image identifier
+T}:T{
+The operating system image identifier of the running system, as read from the \fIIMAGE_ID=\fR field of /etc/os\-release\&. If not set, resolves to an empty string\&. See \fBos-release\fR(5) for more information\&.
+T}
+T{
+"%o"
+T}:T{
+Operating system ID
+T}:T{
+The operating system identifier of the running system, as read from the \fIID=\fR field of /etc/os\-release\&. See \fBos-release\fR(5) for more information\&.
+T}
+T{
+"%q"
+T}:T{
+Pretty host name
+T}:T{
+The pretty hostname of the running system, as read from the \fIPRETTY_HOSTNAME=\fR field of /etc/machine\-info\&. If not set, resolves to the short hostname\&. See \fBmachine-info\fR(5) for more information\&.
+T}
+T{
+"%T"
+T}:T{
+Directory for temporary files
+T}:T{
+This is either /tmp or the path "$TMPDIR", "$TEMP" or "$TMP" are set to\&. (Note that the directory may be specified without a trailing slash\&.)
+T}
+T{
+"%v"
+T}:T{
+Kernel release
+T}:T{
+Identical to \fBuname \-r\fR output\&.
+T}
+T{
+"%V"
+T}:T{
+Directory for larger and persistent temporary files
+T}:T{
+This is either /var/tmp or the path "$TMPDIR", "$TEMP" or "$TMP" are set to\&. (Note that the directory may be specified without a trailing slash\&.)
+T}
+T{
+"%w"
+T}:T{
+Operating system version ID
+T}:T{
+The operating system version identifier of the running system, as read from the \fIVERSION_ID=\fR field of /etc/os\-release\&. If not set, resolves to an empty string\&. See \fBos-release\fR(5) for more information\&.
+T}
+T{
+"%W"
+T}:T{
+Operating system variant ID
+T}:T{
+The operating system variant identifier of the running system, as read from the \fIVARIANT_ID=\fR field of /etc/os\-release\&. If not set, resolves to an empty string\&. See \fBos-release\fR(5) for more information\&.
+T}
+.TE
+.sp 1
 .SH "EXAMPLES"
 .PP
 \fBExample\ \&1.\ \&/usr/lib/systemd/network/99\-default\&.link\fR
@@ -2032,11 +2276,7 @@ MACAddress=cb:a9:87:65:43:21
 .\}
 .SH "SEE ALSO"
 .PP
-\fBsystemd-udevd.service\fR(8),
-\fBudevadm\fR(8),
-\fBsystemd.netdev\fR(5),
-\fBsystemd.network\fR(5),
-\fBsystemd-network-generator.service\fR(8)
+\fBsystemd-udevd.service\fR(8), \fBudevadm\fR(8), \fBsystemd.netdev\fR(5), \fBsystemd.network\fR(5), \fBsystemd-network-generator.service\fR(8)
 .SH "NOTES"
 .IP " 1." 4
 System and Service Credentials
diff --git a/upstream/fedora-rawhide/man5/systemd.mount.5 b/upstream/fedora-rawhide/man5/systemd.mount.5
index 62d7fb91..894df873 100644
--- a/upstream/fedora-rawhide/man5/systemd.mount.5
+++ b/upstream/fedora-rawhide/man5/systemd.mount.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.MOUNT" "5" "" "systemd 255" "systemd.mount"
+.TH "SYSTEMD\&.MOUNT" "5" "" "systemd 256~rc3" "systemd.mount"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -104,10 +104,12 @@ If a mount unit is beneath another mount unit in the file system hierarchy, both
 .IP \(bu 2.3
 .\}
 Block device backed file systems automatically gain
-\fIBindsTo=\fR
-and
+\fIRequires=\fR,
+\fIStopPropagatedFrom=\fR, and
 \fIAfter=\fR
-type dependencies on the device unit encapsulating the block device (see below)\&.
+type dependencies on the device unit encapsulating the block device (see
+\fIx\-systemd\&.device\-bound=\fR
+for details)\&.
 .RE
 .sp
 .RS 4
@@ -180,9 +182,18 @@ local\-fs\-pre\&.target, and a
 \fIBefore=\fR
 dependency on
 local\-fs\&.target
-unless
-\fBnofail\fR
-mount option is set\&.
+unless one or more mount options among
+\fBnofail\fR,
+\fBx\-systemd\&.wanted\-by=\fR, and
+\fBx\-systemd\&.required\-by=\fR
+is set\&. See below for detailed information\&.
+.sp
+Additionally, an
+\fIAfter=\fR
+dependency on
+swap\&.target
+is added when the file system type is
+"tmpfs"\&.
 .RE
 .sp
 .RS 4
@@ -197,17 +208,19 @@ Network mount units automatically acquire
 \fIAfter=\fR
 dependencies on
 remote\-fs\-pre\&.target,
-network\&.target
+network\&.target, plus
+\fIAfter=\fR
 and
-network\-online\&.target, and gain a
+\fIWants=\fR
+dependencies on
+network\-online\&.target, and a
 \fIBefore=\fR
 dependency on
-remote\-fs\&.target
-unless
-\fBnofail\fR
-mount option is set\&. Towards the latter a
-\fIWants=\fR
-unit is added as well\&.
+remote\-fs\&.target, unless one or more mount options among
+\fBnofail\fR,
+\fBx\-systemd\&.wanted\-by=\fR, and
+\fBx\-systemd\&.required\-by=\fR
+is set\&.
 .RE
 .PP
 Mount units referring to local and network file systems are distinguished by their file system type specification\&. In some cases this is not sufficient (for example network block device based mounts, such as iSCSI), in which case
@@ -312,8 +325,13 @@ In the created mount unit, configures a
 \fIWantedBy=\fR
 or
 \fIRequiredBy=\fR
-dependency on another unit\&. This option may be specified more than once\&. If this is specified, the normal automatic dependencies on the created mount unit, e\&.g\&.,
-local\-fs\&.target, are not automatically created\&. See
+dependency on another unit\&. This option may be specified more than once\&. If this is specified, the default dependencies (see above) other than
+umount\&.target
+on the created mount unit, e\&.g\&.
+local\-fs\&.target, are not automatically created\&. Hence it is likely that some ordering dependencies need to be set up manually through
+\fBx\-systemd\&.before=\fR
+and
+\fBx\-systemd\&.after=\fR\&. See
 \fIWantedBy=\fR
 and
 \fIRequiredBy=\fR
@@ -324,12 +342,16 @@ for details\&.
 Added in version 245\&.
 .RE
 .PP
-\fBx\-systemd\&.requires\-mounts\-for=\fR
+\fBx\-systemd\&.wants\-mounts\-for=\fR, \fBx\-systemd\&.requires\-mounts\-for=\fR
 .RS 4
 Configures a
 \fIRequiresMountsFor=\fR
+or
+\fIWantsMountsFor=\fR
 dependency between the created mount unit and other mount units\&. The argument must be an absolute path\&. This option may be specified more than once\&. See
 \fIRequiresMountsFor=\fR
+or
+\fIWantsMountsFor=\fR
 in
 \fBsystemd.unit\fR(5)
 for details\&.
@@ -550,13 +572,14 @@ Mount unit files may include [Unit] and [Install] sections, which are described
 \fBsystemd.unit\fR(5)\&.
 .PP
 Mount unit files must include a [Mount] section, which carries information about the file system mount points it supervises\&. A number of options that may be used in this section are shared with other unit types\&. These options are documented in
-\fBsystemd.exec\fR(5)
+\fBsystemd.exec\fR(5),
+\fBsystemd.kill\fR(5)
 and
-\fBsystemd.kill\fR(5)\&. The options specific to the [Mount] section of mount units are the following:
+\fBsystemd.resource-control\fR(5)\&. The options specific to the [Mount] section of mount units are the following:
 .PP
 \fIWhat=\fR
 .RS 4
-Takes an absolute path of a device node, file or other resource to mount\&. See
+Takes an absolute path or a fstab\-style identifier of a device node, file or other resource to mount\&. See
 \fBmount\fR(8)
 for details\&. If this refers to a device node, a dependency on the respective device unit is automatically created\&. (See
 \fBsystemd.device\fR(5)
@@ -574,6 +597,13 @@ Takes an absolute path of a file or directory for the mount point; in particular
 Takes a string for the file system type\&. See
 \fBmount\fR(8)
 for details\&. This setting is optional\&.
+.sp
+If the type is
+"overlay", and
+"upperdir="
+or
+"workdir="
+are specified as options and they don\*(Aqt exist, they will be created\&.
 .RE
 .PP
 \fIOptions=\fR
@@ -649,20 +679,7 @@ Check
 for more settings\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemctl\fR(1),
-\fBsystemd-system.conf\fR(5),
-\fBsystemd.unit\fR(5),
-\fBsystemd.exec\fR(5),
-\fBsystemd.kill\fR(5),
-\fBsystemd.resource-control\fR(5),
-\fBsystemd.service\fR(5),
-\fBsystemd.device\fR(5),
-\fBproc\fR(5),
-\fBmount\fR(8),
-\fBsystemd-fstab-generator\fR(8),
-\fBsystemd.directives\fR(7),
-\fBsystemd-mount\fR(1)
+\fBsystemd\fR(1), \fBsystemctl\fR(1), \fBsystemd-system.conf\fR(5), \fBsystemd.unit\fR(5), \fBsystemd.exec\fR(5), \fBsystemd.kill\fR(5), \fBsystemd.resource-control\fR(5), \fBsystemd.service\fR(5), \fBsystemd.device\fR(5), \fBproc\fR(5), \fBmount\fR(8), \fBsystemd-fstab-generator\fR(8), \fBsystemd.directives\fR(7), \fBsystemd-mount\fR(1)
 .SH "NOTES"
 .IP " 1." 4
 API File Systems
diff --git a/upstream/fedora-rawhide/man5/systemd.netdev.5 b/upstream/fedora-rawhide/man5/systemd.netdev.5
index 4cbedb2f..6343ec31 100644
--- a/upstream/fedora-rawhide/man5/systemd.netdev.5
+++ b/upstream/fedora-rawhide/man5/systemd.netdev.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.NETDEV" "5" "" "systemd 255" "systemd.network"
+.TH "SYSTEMD\&.NETDEV" "5" "" "systemd 256~rc3" "systemd.network"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -670,6 +670,16 @@ Specifies the length of the receive queue for broadcast/multicast packets\&. An
 .sp
 Added in version 248\&.
 .RE
+.PP
+\fIBroadcastQueueThreshold=\fR
+.RS 4
+Controls the threshold for broadcast queueing of the macvlan device\&. Takes the special value
+"no", or an integer in the range 0\&...2147483647\&. When
+"no"
+is specified, the broadcast queueing is disabled altogether\&. When an integer is specified, a multicast address will be queued as broadcast if the number of devices using it is greater than the given value\&. Defaults to unset, and the kernel default will be used\&.
+.sp
+Added in version 256\&.
+.RE
 .SH "[MACVTAP] SECTION OPTIONS"
 .PP
 The [MACVTAP] section applies for netdevs of kind
@@ -1734,9 +1744,19 @@ The [WireGuard] section accepts the following keys:
 The Base64 encoded private key for the interface\&. It can be generated using the
 \fBwg genkey\fR
 command (see
-\fBwg\fR(8))\&. This option or
-\fIPrivateKeyFile=\fR
-is mandatory to use WireGuard\&. Note that because this information is secret, you may want to set the permissions of the \&.netdev file to be owned by
+\fBwg\fR(8))\&. Specially, if the specified key is prefixed with
+"@", it is interpreted as the name of the credential from which the actual key shall be read\&.
+\fBsystemd\-networkd\&.service\fR
+automatically imports credentials matching
+"network\&.wireguard\&.*"\&. For more details on credentials, refer to
+\fBsystemd.exec\fR(5)\&. A private key is mandatory to use WireGuard\&. If not set, the credential
+"network\&.wireguard\&.private\&.\fInetdev\fR"
+is used if exists\&. I\&.e\&. for
+50\-foobar\&.netdev,
+"network\&.wireguard\&.private\&.50\-foobar"
+is tried\&.
+.sp
+Note that because this information is secret, it\*(Aqs strongly recommended to use an (encrypted) credential\&. Alternatively, you may want to set the permissions of the \&.netdev file to be owned by
 "root:systemd\-network"
 with a
 "0640"
@@ -1813,7 +1833,13 @@ The [WireGuardPeer] section accepts the following keys:
 Sets a Base64 encoded public key calculated by
 \fBwg pubkey\fR
 (see
-\fBwg\fR(8)) from a private key, and usually transmitted out of band to the author of the configuration file\&. This option is mandatory for this section\&.
+\fBwg\fR(8)) from a private key, and usually transmitted out of band to the author of the configuration file\&. This option honors the
+"@"
+prefix in the same way as the
+\fBPrivateKey=\fR
+setting of the
+\fB[WireGuard]\fR
+section\&. This option is mandatory for this section\&.
 .sp
 Added in version 237\&.
 .RE
@@ -1822,7 +1848,15 @@ Added in version 237\&.
 .RS 4
 Optional preshared key for the interface\&. It can be generated by the
 \fBwg genpsk\fR
-command\&. This option adds an additional layer of symmetric\-key cryptography to be mixed into the already existing public\-key cryptography, for post\-quantum resistance\&. Note that because this information is secret, you may want to set the permissions of the \&.netdev file to be owned by
+command\&. This option adds an additional layer of symmetric\-key cryptography to be mixed into the already existing public\-key cryptography, for post\-quantum resistance\&. This option honors the
+"@"
+prefix in the same way as the
+\fBPrivateKey=\fR
+setting of the
+\fB[WireGuard]\fR
+section\&.
+.sp
+Note that because this information is secret, it\*(Aqs strongly recommended to use an (encrypted) credential\&. Alternatively, you may want to set the permissions of the \&.netdev file to be owned by
 "root:systemd\-network"
 with a
 "0640"
@@ -1872,6 +1906,14 @@ for IPv4 and
 "[1111:2222::3333]:51820"
 for IPv6 address\&. This endpoint will be updated automatically once to the most recent source IP address and port of correctly authenticated packets from the peer at configuration time\&.
 .sp
+This option honors the
+"@"
+prefix in the same way as the
+\fBPrivateKey=\fR
+setting of the
+\fB[WireGuard]\fR
+section\&.
+.sp
 Added in version 237\&.
 .RE
 .PP
@@ -1952,6 +1994,14 @@ Specifies the frequency that Media Independent Interface link monitoring will oc
 Added in version 216\&.
 .RE
 .PP
+\fIPeerNotifyDelaySec=\fR
+.RS 4
+Specifies the number of seconds the delay between each peer notification (gratuitous ARP and unsolicited IPv6 Neighbor Advertisement) when they are issued after a failover event\&. This delay should be a multiple of the MII link monitor interval (miimon)\&. The valid range is 0\&.\&.\&.300s\&. The default value is 0, which means to match the value of the
+\fIMIIMonitorSec=\fR\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fIUpDelaySec=\fR
 .RS 4
 Specifies the delay before a link is enabled after a link up status has been detected\&. This value is rounded down to a multiple of
@@ -2111,6 +2161,13 @@ Specifies the minimum number of links that must be active before asserting carri
 Added in version 220\&.
 .RE
 .PP
+\fIARPMissedMax=\fR
+.RS 4
+Specify the maximum number of arp interval monitor cycle for missed ARP replies\&. If this number is exceeded, link is reported as down\&. Defaults to unset\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 For more detail information see
 \m[blue]\fBLinux Ethernet Bonding Driver HOWTO\fR\m[]\&\s-2\u[1]\d\s+2
 .SH "[XFRM] SECTION OPTIONS"
@@ -2648,11 +2705,7 @@ Independent=yes
 .\}
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-networkd\fR(8),
-\fBsystemd.link\fR(5),
-\fBsystemd.network\fR(5),
-\fBsystemd-network-generator.service\fR(8)
+\fBsystemd\fR(1), \fBsystemd-networkd\fR(8), \fBsystemd.link\fR(5), \fBsystemd.network\fR(5), \fBsystemd-network-generator.service\fR(8)
 .SH "NOTES"
 .IP " 1." 4
 Linux Ethernet Bonding Driver HOWTO
diff --git a/upstream/fedora-rawhide/man5/systemd.network.5 b/upstream/fedora-rawhide/man5/systemd.network.5
index 49b3eb68..5238454e 100644
--- a/upstream/fedora-rawhide/man5/systemd.network.5
+++ b/upstream/fedora-rawhide/man5/systemd.network.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.NETWORK" "5" "" "systemd 255" "systemd.network"
+.TH "SYSTEMD\&.NETWORK" "5" "" "systemd 256~rc3" "systemd.network"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -447,14 +447,16 @@ Added in version 246\&.
 .PP
 \fIRequiredForOnline=\fR
 .RS 4
-Takes a boolean or a minimum operational state and an optional maximum operational state\&. Please see
+Takes a boolean, a minimum operational state (e\&.g\&.,
+"carrier"), or a range of operational state separated with a colon (e\&.g\&.,
+"degraded:routable")\&. Please see
 \fBnetworkctl\fR(1)
 for possible operational states\&. When
 "yes", the network is deemed required when determining whether the system is online (including when running
 \fBsystemd\-networkd\-wait\-online\fR)\&. When
 "no", the network is ignored when determining the online state\&. When a minimum operational state and an optional maximum operational state are set,
-"yes"
-is implied, and this controls the minimum and maximum operational state required for the network interface to be considered online\&.
+\fBsystemd\-networkd\-wait\-online\fR
+deems that the interface is online when the operational state is in the specified range\&.
 .sp
 Defaults to
 "yes"
@@ -483,6 +485,45 @@ The network will be brought up normally (as configured by
 if
 "RequiredForOnline=no"\&.
 .sp
+The boolean value
+"yes"
+is translated as follows;
+.PP
+\fBCAN devices\fR
+.RS 4
+"carrier",
+.sp
+Added in version 256\&.
+.RE
+.PP
+\fBMaster devices, e\&.g\&. bond or bridge\fR
+.RS 4
+"degraded\-carrier"
+with
+\fIRequiredFamilyForOnline=any\fR,
+.sp
+Added in version 256\&.
+.RE
+.PP
+\fBBonding port interfaces\fR
+.RS 4
+"enslaved",
+.sp
+Added in version 256\&.
+.RE
+.PP
+\fBOther interfaces\fR
+.RS 4
+"degraded"\&.
+.sp
+Added in version 236\&.
+.RE
+.sp
+This setting can be overridden by the command line option for
+\fBsystemd\-networkd\-wait\-online\fR\&. See
+\fBsystemd-networkd-wait-online.service\fR(8)
+for more details\&.
+.sp
 Added in version 236\&.
 .RE
 .PP
@@ -494,11 +535,8 @@ Takes an address family\&. When specified, an IP address in the given family is
 "ipv6",
 "both", or
 "any"\&. Defaults to
-"any"\&. Note that this option has no effect if
-"RequiredForOnline=no", or if
-"RequiredForOnline="
-specifies a minimum operational state below
-"degraded"\&.
+"no"\&. Note that this option has no effect if
+"RequiredForOnline=no"\&.
 .sp
 Added in version 249\&.
 .RE
@@ -686,14 +724,23 @@ Takes a boolean\&. If set to
 "yes", DHCPv4 server will be started\&. Defaults to
 "no"\&. Further settings for the DHCP server may be set in the [DHCPServer] section described below\&.
 .sp
+Even if this is enabled, the DHCP server will not be started automatically and wait for the persistent storage being ready to load/save leases in the storage, unless
+\fIRelayTarget=\fR
+or
+\fIPersistLeases=no\fR
+are specified in the [DHCPServer] section\&. It will be started after
+systemd\-networkd\-persistent\-storage\&.service
+is started, which calls
+\fBnetworkctl persistent\-storage yes\fR\&. See
+\fBnetworkctl\fR(1)
+for more details\&.
+.sp
 Added in version 215\&.
 .RE
 .PP
 \fILinkLocalAddressing=\fR
 .RS 4
-Enables link\-local address autoconfiguration\&. Accepts
-\fByes\fR,
-\fBno\fR,
+Enables link\-local address autoconfiguration\&. Accepts a boolean,
 \fBipv4\fR, and
 \fBipv6\fR\&. An IPv6 link\-local address is configured when
 \fByes\fR
@@ -963,6 +1010,8 @@ If the specified address is
 "::"
 (for IPv6), a new address range of the requested size is automatically allocated from a system\-wide pool of unused ranges\&. Note that the prefix length must be equal or larger than 8 for IPv4, and 64 for IPv6\&. The allocated range is checked against all current network interfaces and all known network configuration files to avoid address range conflicts\&. The default system\-wide pool consists of 192\&.168\&.0\&.0/16, 172\&.16\&.0\&.0/12 and 10\&.0\&.0\&.0/8 for IPv4, and fd00::/8 for IPv6\&. This functionality is useful to manage a large number of dynamically created network interfaces with the same network configuration and automatic address range assignment\&.
 .sp
+If an empty string is specified, then the all previous assignments in both [Network] and [Address] sections are cleared\&.
+.sp
 Added in version 211\&.
 .RE
 .PP
@@ -992,6 +1041,14 @@ for IPv6\&. If an empty string is assigned, then the all previous assignments ar
 Added in version 211\&.
 .RE
 .PP
+\fIUseDomains=\fR
+.RS 4
+Specifies the protocol\-independent default value for the same settings in [IPv6AcceptRA], [DHCPv4], and [DHCPv6] sections below\&. Takes a boolean, or the special value
+\fBroute\fR\&. See also the same setting in [DHCPv4] below\&. Defaults to unset\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fIDomains=\fR
 .RS 4
 A whitespace\-separated list of domains which should be resolved using the DNS servers on this link\&. Each item in the list should be a domain name, optionally prefixed with a tilde ("~")\&. The domains with the prefix are called "routing\-only domains"\&. The domains without the prefix are called "search domains" and are first used as search suffixes for extending single\-label hostnames (hostnames containing no dots) to become fully qualified domain names (FQDNs)\&. If a single\-label hostname is resolved on this interface, each of the specified search domains are appended to it in turn, converting it into a fully qualified domain name, until one of them may be successfully resolved\&.
@@ -1030,25 +1087,42 @@ An NTP server address (either an IP address, or a hostname)\&. This option may b
 Added in version 216\&.
 .RE
 .PP
-\fIIPForward=\fR
+\fIIPv4Forwarding=\fR
 .RS 4
-Configures IP packet forwarding for the system\&. If enabled, incoming packets on any network interface will be forwarded to any other interfaces according to the routing table\&. Takes a boolean, or the values
-"ipv4"
-or
-"ipv6", which only enable IP packet forwarding for the specified address family\&. This controls the
-net\&.ipv4\&.ip_forward
-and
-net\&.ipv6\&.conf\&.all\&.forwarding
-sysctl options of the network interface (see
+Configures IPv4 packet forwarding for the interface\&. Takes a boolean value\&. This controls the
+net\&.ipv4\&.conf\&.\fIINTERFACE\fR\&.forwarding
+sysctl option of the network interface\&. See
 \m[blue]\fBIP Sysctl\fR\m[]\&\s-2\u[7]\d\s+2
-for details about sysctl options)\&. Defaults to
-"no"\&.
+for more details about the sysctl option\&. Defaults to true if
+\fIIPMasquerade=\fR
+is enabled for IPv4, otherwise the value specified to the same setting in
+\fBnetworkd.conf\fR(5)
+will be used\&. If none of them are specified, the sysctl option will not be changed\&.
 .sp
-Note: this setting controls a global kernel option, and does so one way only: if a network that has this setting enabled is set up the global setting is turned on\&. However, it is never turned off again, even after all networks with this setting enabled are shut down again\&.
+To control the global setting, use the same setting in
+\fBnetworkd.conf\fR(5)\&.
 .sp
-To allow IP packet forwarding only between specific network interfaces use a firewall\&.
+Added in version 256\&.
+.RE
+.PP
+\fIIPv6Forwarding=\fR
+.RS 4
+Configures IPv6 packet forwarding for the interface\&. Takes a boolean value\&. This controls the
+net\&.ipv6\&.conf\&.\fIINTERFACE\fR\&.forwarding
+sysctl option of the network interface\&. See
+\m[blue]\fBIP Sysctl\fR\m[]\&\s-2\u[7]\d\s+2
+for more details about the sysctl option\&. Defaults to true if
+\fIIPMasquerade=\fR
+is enabled for IPv6 or
+\fIIPv6SendRA=\fR
+is enabled, otherwise the value specified to the same setting in
+\fBnetworkd.conf\fR(5)
+will be used\&. If none of them are specified, the sysctl option will not be changed\&.
 .sp
-Added in version 219\&.
+To control the global setting, use the same setting in
+\fBnetworkd.conf\fR(5)\&.
+.sp
+Added in version 256\&.
 .RE
 .PP
 \fIIPMasquerade=\fR
@@ -1058,19 +1132,13 @@ Configures IP masquerading for the network interface\&. If enabled, packets forw
 "ipv6",
 "both", or
 "no"\&. Defaults to
-"no"\&. If enabled, this automatically sets
-\fIIPForward=\fR
-to one of
-"ipv4",
-"ipv6"
-or
-"yes"\&.
+"no"\&.
 .sp
 Note\&. Any positive boolean values such as
 "yes"
 or
 "true"
-are now deprecated\&. Please use one of the values in the above\&.
+are now deprecated\&. Please use one of the values above\&.
 .sp
 Added in version 219\&.
 .RE
@@ -1092,7 +1160,11 @@ Added in version 222\&.
 .PP
 \fIIPv6AcceptRA=\fR
 .RS 4
-Takes a boolean\&. Controls IPv6 Router Advertisement (RA) reception support for the interface\&. If true, RAs are accepted; if false, RAs are ignored\&. When RAs are accepted, they may trigger the start of the DHCPv6 client if the relevant flags are set in the RA data, or if no routers are found on the link\&. The default is to disable RA reception for bridge devices or when IP forwarding is enabled, and to enable it otherwise\&. Cannot be enabled on devices aggregated in a bond device or when link\-local addressing is disabled\&.
+Takes a boolean\&. Controls IPv6 Router Advertisement (RA) reception support for the interface\&. If true, RAs are accepted; if false, RAs are ignored\&. When RAs are accepted, they may trigger the start of the DHCPv6 client if the relevant flags are set in the RA data, or if no routers are found on the link\&. Defaults to false for bridge devices, when IP forwarding is enabled,
+\fIIPv6SendRA=\fR
+or
+\fIKeepMaster=\fR
+is enabled\&. Otherwise, enabled by default\&. Cannot be enabled on devices aggregated in a bond device or when link\-local addressing is disabled\&.
 .sp
 Further settings for the IPv6 RA support may be configured in the [IPv6AcceptRA] section, see below\&.
 .sp
@@ -1125,6 +1197,13 @@ Configures IPv6 Hop Limit\&. Takes an integer in the range 1\&...255\&. For each
 Added in version 228\&.
 .RE
 .PP
+\fIIPv6RetransmissionTimeSec=\fR
+.RS 4
+Configures IPv6 Retransmission Time\&. The time between retransmitted Neighbor Solicitation messages\&. Used by address resolution and the Neighbor Unreachability Detection algorithm\&. A value of zero is ignored and the kernel\*(Aqs current value will be used\&. Defaults to unset, and the kernel\*(Aqs current value will be used\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fIIPv4ReversePathFilter=\fR
 .RS 4
 Configure IPv4 Reverse Path Filtering\&. If enabled, when an IPv4 packet is received, the machine will first check whether the
@@ -1163,6 +1242,18 @@ Takes a boolean\&. Configures proxy ARP for IPv4\&. Proxy ARP is the technique i
 Added in version 233\&.
 .RE
 .PP
+\fIIPv4ProxyARPPrivateVLAN=\fR
+.RS 4
+Takes a boolean\&. Configures proxy ARP private VLAN for IPv4, also known as VLAN aggregation, private VLAN, source\-port filtering, port\-isolation, or MAC\-forced forwarding\&.
+.sp
+This variant of the ARP proxy technique will allow the ARP proxy to reply back to the same interface\&.
+.sp
+See
+\m[blue]\fBRFC 3069\fR\m[]\&\s-2\u[10]\d\s+2\&. When unset, the kernel\*(Aqs default will be used\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fIIPv6ProxyNDP=\fR
 .RS 4
 Takes a boolean\&. Configures proxy NDP for IPv6\&. Proxy NDP (Neighbor Discovery Protocol) is a technique for IPv6 to allow routing of addresses to a different destination when peers expect them to be present on a certain physical link\&. In this case a router answers Neighbour Advertisement messages intended for another machine by offering its own MAC address as destination\&. Unlike proxy ARP for IPv4, it is not enabled globally, but will only send Neighbour Advertisement messages for addresses in the IPv6 neighbor proxy table, which can also be shown by
@@ -1445,7 +1536,7 @@ Added in version 246\&.
 \fIHomeAddress=\fR
 .RS 4
 Takes a boolean\&. Designates this address the "home address" as defined in
-\m[blue]\fBRFC 6275\fR\m[]\&\s-2\u[10]\d\s+2\&. Supported only on IPv6\&. Defaults to false\&.
+\m[blue]\fBRFC 6275\fR\m[]\&\s-2\u[11]\d\s+2\&. Supported only on IPv6\&. Defaults to false\&.
 .sp
 Added in version 232\&.
 .RE
@@ -1458,9 +1549,9 @@ Takes one of
 "both", or
 "none"\&. When
 "ipv4", performs IPv4 Address Conflict Detection\&. See
-\m[blue]\fBRFC 5227\fR\m[]\&\s-2\u[11]\d\s+2\&. When
+\m[blue]\fBRFC 5227\fR\m[]\&\s-2\u[12]\d\s+2\&. When
 "ipv6", performs IPv6 Duplicate Address Detection\&. See
-\m[blue]\fBRFC 4862\fR\m[]\&\s-2\u[12]\d\s+2\&. Defaults to
+\m[blue]\fBRFC 4862\fR\m[]\&\s-2\u[13]\d\s+2\&. Defaults to
 "ipv4"
 for IPv4 link\-local addresses,
 "ipv6"
@@ -1474,7 +1565,7 @@ Added in version 232\&.
 \fIManageTemporaryAddress=\fR
 .RS 4
 Takes a boolean\&. If true the kernel manage temporary addresses created from this one as template on behalf of Privacy Extensions
-\m[blue]\fBRFC 3041\fR\m[]\&\s-2\u[13]\d\s+2\&. For this to become active, the use_tempaddr sysctl setting has to be set to a value greater than zero\&. The given address needs to have a prefix length of 64\&. This flag allows using privacy extensions in a manually configured network, just like if stateless auto\-configuration was active\&. Defaults to false\&.
+\m[blue]\fBRFC 3041\fR\m[]\&\s-2\u[14]\d\s+2\&. For this to become active, the use_tempaddr sysctl setting has to be set to a value greater than zero\&. The given address needs to have a prefix length of 64\&. This flag allows using privacy extensions in a manually configured network, just like if stateless auto\-configuration was active\&. Defaults to false\&.
 .sp
 Added in version 232\&.
 .RE
@@ -1505,22 +1596,34 @@ Added in version 232\&.
 \fINetLabel=\fR\fIlabel\fR
 .RS 4
 This setting provides a method for integrating static and dynamic network configuration into Linux
-\m[blue]\fBNetLabel\fR\m[]\&\s-2\u[14]\d\s+2
+\m[blue]\fBNetLabel\fR\m[]\&\s-2\u[15]\d\s+2
 subsystem rules, used by
-\m[blue]\fBLinux Security Modules (LSMs)\fR\m[]\&\s-2\u[15]\d\s+2
+\m[blue]\fBLinux Security Modules (LSMs)\fR\m[]\&\s-2\u[16]\d\s+2
 for network access control\&. The label, with suitable LSM rules, can be used to control connectivity of (for example) a service with peers in the local network\&. At least with SELinux, only the ingress can be controlled but not egress\&. The benefit of using this setting is that it may be possible to apply interface independent part of NetLabel configuration at very early stage of system boot sequence, at the time when the network interfaces are not available yet, with
 \fBnetlabelctl\fR(8), and the per\-interface configuration with
 \fBsystemd\-networkd\fR
 once the interfaces appear later\&. Currently this feature is only implemented for SELinux\&.
 .sp
 The option expects a single NetLabel label\&. The label must conform to lexical restrictions of LSM labels\&. When an interface is configured with IP addresses, the addresses and subnetwork masks will be appended to the
-\m[blue]\fBNetLabel Fallback Peer Labeling\fR\m[]\&\s-2\u[16]\d\s+2
+\m[blue]\fBNetLabel Fallback Peer Labeling\fR\m[]\&\s-2\u[17]\d\s+2
 rules\&. They will be removed when the interface is deconfigured\&. Failures to manage the labels will be ignored\&.
+.if n \{\
 .sp
-Warning: Once labeling is enabled for network traffic, a lot of LSM access control points in Linux networking stack go from dormant to active\&. Care should be taken to avoid getting into a situation where for example remote connectivity is broken, when the security policy hasn\*(Aqt been updated to consider LSM per\-packet access controls and no rules would allow any network traffic\&. Also note that additional configuration with
+.\}
+.RS 4
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+.ps +1
+\fBWarning\fR
+.ps -1
+.br
+Once labeling is enabled for network traffic, a lot of LSM access control points in Linux networking stack go from dormant to active\&. Care should be taken to avoid getting into a situation where for example remote connectivity is broken, when the security policy hasn\*(Aqt been updated to consider LSM per\-packet access controls and no rules would allow any network traffic\&. Also note that additional configuration with
 \fBnetlabelctl\fR(8)
 is needed\&.
-.sp
+.sp .5v
+.RE
 Example:
 .sp
 .if n \{\
@@ -1577,7 +1680,7 @@ Added in version 252\&.
 \fINFTSet=\fR\fIsource\fR:\fIfamily\fR:\fItable\fR:\fIset\fR
 .RS 4
 This setting provides a method for integrating network configuration into firewall rules with
-\m[blue]\fBNFT\fR\m[]\&\s-2\u[17]\d\s+2
+\m[blue]\fBNFT\fR\m[]\&\s-2\u[18]\d\s+2
 sets\&. The benefit of using the setting is that static network configuration (or dynamically obtained network addresses, see similar directives in other sections) can be used in firewall rules with the indirection of NFT set types\&. For example, access could be granted for hosts in the local subnetwork only\&. Firewall rules using IP address of an interface are also instantly updated when the network configuration changes, for example via DHCP\&.
 .sp
 This option expects a whitespace separated list of NFT set definitions\&. Each definition consists of a colon\-separated tuple of source type (one of
@@ -1698,7 +1801,7 @@ Added in version 243\&.
 .SH "[IPV6ADDRESSLABEL] SECTION OPTIONS"
 .PP
 An [IPv6AddressLabel] section accepts the following keys\&. Specify several [IPv6AddressLabel] sections to configure several address labels\&. IPv6 address labels are used for address selection\&. See
-\m[blue]\fBRFC 3484\fR\m[]\&\s-2\u[18]\d\s+2\&. Precedence is managed by userspace, and only the label itself is stored in the kernel\&.
+\m[blue]\fBRFC 3484\fR\m[]\&\s-2\u[19]\d\s+2\&. Precedence is managed by userspace, and only the label itself is stored in the kernel\&.
 .PP
 \fILabel=\fR
 .RS 4
@@ -1722,9 +1825,9 @@ An [RoutingPolicyRule] section accepts the following settings\&. Specify several
 \fITypeOfService=\fR
 .RS 4
 This specifies the Type of Service (ToS) field of packets to match; it takes an unsigned integer in the range 0\&...255\&. The field can be used to specify precedence (the first 3 bits) and ToS (the next 3 bits)\&. The field can be also used to specify Differentiated Services Code Point (DSCP) (the first 6 bits) and Explicit Congestion Notification (ECN) (the last 2 bits)\&. See
-\m[blue]\fBType of Service\fR\m[]\&\s-2\u[19]\d\s+2
+\m[blue]\fBType of Service\fR\m[]\&\s-2\u[20]\d\s+2
 and
-\m[blue]\fBDifferentiated services\fR\m[]\&\s-2\u[20]\d\s+2
+\m[blue]\fBDifferentiated services\fR\m[]\&\s-2\u[21]\d\s+2
 for more details\&.
 .sp
 Added in version 235\&.
@@ -1789,6 +1892,14 @@ Specifies the outgoing device to match\&. The outgoing interface is only availab
 Added in version 236\&.
 .RE
 .PP
+\fIL3MasterDevice=\fR
+.RS 4
+A boolean\&. Specifies whether the rule is to direct lookups to the tables associated with level 3 master devices (also known as Virtual Routing and Forwarding or VRF devices)\&. For further details see
+\m[blue]\fBVirtual Routing and Forwarding (VRF)\fR\m[]\&\s-2\u[22]\d\s+2\&. Defaults to false\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fISourcePort=\fR
 .RS 4
 Specifies the source IP port or IP port range match in forwarding information base (FIB) rules\&. A port range is specified by the lower and upper port separated by a dash\&. Defaults to unset\&.
@@ -1890,7 +2001,10 @@ The [NextHop] section is used to manipulate entries in the kernel\*(Aqs "nexthop
 .PP
 \fIId=\fR
 .RS 4
-The id of the next hop\&. Takes an integer in the range 1\&...4294967295\&. If unspecified, then automatically chosen by kernel\&.
+The id of the next hop\&. Takes an integer in the range 1\&...4294967295\&. This is mandatory if
+\fIManageForeignNextHops=no\fR
+is specified in
+\fBnetworkd.conf\fR(5)\&. Otherwise, if unspecified, an unused ID will be automatically picked\&.
 .sp
 Added in version 244\&.
 .RE
@@ -1993,7 +2107,7 @@ Added in version 216\&.
 \fIIPv6Preference=\fR
 .RS 4
 Specifies the route preference as defined in
-\m[blue]\fBRFC 4191\fR\m[]\&\s-2\u[21]\d\s+2
+\m[blue]\fBRFC 4191\fR\m[]\&\s-2\u[23]\d\s+2
 for Router Discovery messages\&. Which can be one of
 "low"
 the route has a lowest priority,
@@ -2121,7 +2235,9 @@ is
 "nat", then
 "local"
 is used\&. In other cases, defaults to
-"main"\&.
+"main"\&. Ignored if
+\fIL3MasterDevice=\fR
+is true\&.
 .sp
 Added in version 230\&.
 .RE
@@ -2200,13 +2316,6 @@ Takes a boolean\&. When true enables TCP fastopen without a cookie on a per\-rou
 Added in version 243\&.
 .RE
 .PP
-\fITTLPropagate=\fR
-.RS 4
-Takes a boolean\&. When true enables TTL propagation at Label Switched Path (LSP) egress\&. When unset, the kernel\*(Aqs default will be used\&.
-.sp
-Added in version 243\&.
-.RE
-.PP
 \fIMTUBytes=\fR
 .RS 4
 The maximum transmission unit in bytes to set for the route\&. The usual suffixes K, M, G, are supported and are understood to the base of 1024\&.
@@ -2283,7 +2392,7 @@ Added in version 223\&.
 \fIMUDURL=\fR
 .RS 4
 When configured, the specified Manufacturer Usage Description (MUD) URL will be sent to the DHCPv4 server\&. Takes a URL of length up to 255 characters\&. A superficial verification that the string is a valid URL will be performed\&. DHCPv4 clients are intended to have at most one MUD URL associated with them\&. See
-\m[blue]\fBRFC 8520\fR\m[]\&\s-2\u[22]\d\s+2\&.
+\m[blue]\fBRFC 8520\fR\m[]\&\s-2\u[24]\d\s+2\&.
 .sp
 MUD is an embedded software standard defined by the IETF that allows IoT device makers to advertise device specifications, including the intended communication patterns for their device when it connects to the network\&. The network can then use this to author a context\-specific access policy, so the device functions only within those parameters\&.
 .sp
@@ -2353,7 +2462,7 @@ Added in version 230\&.
 \fIRapidCommit=\fR
 .RS 4
 Takes a boolean\&. The DHCPv4 client can obtain configuration parameters from a DHCPv4 server through a rapid two\-message exchange (discover and ack)\&. When the rapid commit option is set by both the DHCPv4 client and the DHCPv4 server, the two\-message exchange is used\&. Otherwise, the four\-message exchange (discover, offer, request, and ack) is used\&. The two\-message exchange provides faster client configuration\&. See
-\m[blue]\fBRFC 4039\fR\m[]\&\s-2\u[23]\d\s+2
+\m[blue]\fBRFC 4039\fR\m[]\&\s-2\u[25]\d\s+2
 for details\&. Defaults to true when
 \fIAnonymize=no\fR
 and neither
@@ -2368,7 +2477,7 @@ Added in version 255\&.
 \fIAnonymize=\fR
 .RS 4
 Takes a boolean\&. When true, the options sent to the DHCP server will follow the
-\m[blue]\fBRFC 7844\fR\m[]\&\s-2\u[24]\d\s+2
+\m[blue]\fBRFC 7844\fR\m[]\&\s-2\u[26]\d\s+2
 (Anonymity Profiles for DHCP Clients) to minimize disclosure of identifying information\&. Defaults to false\&.
 .sp
 This option should only be set to true when
@@ -2391,7 +2500,7 @@ When true,
 are implied and these settings in the \&.network file are silently ignored\&. Also,
 \fIHostname=\fR,
 \fIMUDURL=\fR,
-\fIRequestAddress\fR,
+\fIRequestAddress=\fR,
 \fIRequestOptions=\fR,
 \fISendOption=\fR,
 \fISendVendorOption=\fR,
@@ -2419,7 +2528,7 @@ Send an arbitrary raw option in the DHCPv4 request\&. Takes a DHCP option number
 "uint32",
 "ipv4address", or
 "string"\&. Special characters in the data string may be escaped using
-\m[blue]\fBC\-style escapes\fR\m[]\&\s-2\u[25]\d\s+2\&. This setting can be specified multiple times\&. If an empty string is specified, then all options specified earlier are cleared\&. Defaults to unset\&.
+\m[blue]\fBC\-style escapes\fR\m[]\&\s-2\u[27]\d\s+2\&. This setting can be specified multiple times\&. If an empty string is specified, then all options specified earlier are cleared\&. Defaults to unset\&.
 .sp
 Added in version 244\&.
 .RE
@@ -2432,7 +2541,7 @@ Send an arbitrary vendor option in the DHCPv4 request\&. Takes a DHCP option num
 "uint32",
 "ipv4address", or
 "string"\&. Special characters in the data string may be escaped using
-\m[blue]\fBC\-style escapes\fR\m[]\&\s-2\u[25]\d\s+2\&. This setting can be specified multiple times\&. If an empty string is specified, then all options specified earlier are cleared\&. Defaults to unset\&.
+\m[blue]\fBC\-style escapes\fR\m[]\&\s-2\u[27]\d\s+2\&. This setting can be specified multiple times\&. If an empty string is specified, then all options specified earlier are cleared\&. Defaults to unset\&.
 .sp
 Added in version 246\&.
 .RE
@@ -2560,7 +2669,14 @@ setting\&. If set to
 \fBroute\fR, the domain name received from the DHCP server will be used for routing DNS queries only, but not for searching, similarly to the effect of the
 \fBDomains=\fR
 setting when the argument is prefixed with
-"~"\&. Defaults to false\&.
+"~"\&.
+.sp
+When unspecified, the value specified in the same setting in the [Network] section will be used\&. When it is unspecified, the value specified in the same setting in the [DHCPv4] section in
+\fBnetworkd.conf\fR(5)
+will be used\&. When it is unspecified, the value specified in the same setting in the [Network] section in
+\fBnetworkd.conf\fR(5)
+will be used\&. When none of them are specified, defaults to
+"no"\&.
 .sp
 It is recommended to enable this option only on trusted networks, as setting this affects resolution of all hostnames, in particular of single\-label names\&. It is generally safer to use the supplied domain only as routing domain, rather than as search domain, in order to not have it affect local resolution of single\-label names\&.
 .sp
@@ -2647,7 +2763,7 @@ will be used\&.
 Note, when the server provides both the Router and Classless Static Routes option, and
 \fIUseRoutes=\fR
 is enabled, the Router option is always ignored regardless of this setting\&. See
-\m[blue]\fBRFC 3442\fR\m[]\&\s-2\u[26]\d\s+2\&.
+\m[blue]\fBRFC 3442\fR\m[]\&\s-2\u[28]\d\s+2\&.
 .sp
 Added in version 246\&.
 .RE
@@ -2665,7 +2781,7 @@ When true, subnets of the received IPv6 prefix are assigned to downstream interf
 \fIDHCPPrefixDelegation=\fR\&. See also
 \fIDHCPPrefixDelegation=\fR
 in the [Network] section, the [DHCPPrefixDelegation] section, and
-\m[blue]\fBRFC 5969\fR\m[]\&\s-2\u[27]\d\s+2\&. Defaults to false\&.
+\m[blue]\fBRFC 5969\fR\m[]\&\s-2\u[29]\d\s+2\&. Defaults to false\&.
 .sp
 Added in version 250\&.
 .RE
@@ -2673,10 +2789,7 @@ Added in version 250\&.
 \fIIPv6OnlyMode=\fR
 .RS 4
 When true, the DHCPv4 configuration will be delayed by the timespan provided by the DHCP server and skip to configure dynamic IPv4 network connectivity if IPv6 connectivity is provided within the timespan\&. See
-\m[blue]\fBRFC 8925\fR\m[]\&\s-2\u[28]\d\s+2\&. Defaults to true when
-\fIIPv6AcceptRA=\fR
-is enabled or DHCPv6 client is enabled (i\&.e\&.,
-\fIDHCP=yes\fR), and false otherwise\&.
+\m[blue]\fBRFC 8925\fR\m[]\&\s-2\u[30]\d\s+2\&. Defaults to false\&.
 .sp
 Added in version 255\&.
 .RE
@@ -2714,6 +2827,13 @@ Set the port from which the DHCP client packets originate\&.
 Added in version 233\&.
 .RE
 .PP
+\fIServerPort=\fR
+.RS 4
+Set the port on which the DHCP server is listening\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fIDenyList=\fR
 .RS 4
 A whitespace\-separated list of IPv4 addresses\&. Each address can optionally take a prefix length after
@@ -2723,7 +2843,7 @@ is configured then
 \fIDenyList=\fR
 is ignored\&.
 .sp
-Note that this filters only DHCP offers, so the filtering may not work when
+Note that this filters only DHCP offers, so the filtering might not work when
 \fIRapidCommit=\fR
 is enabled\&. See also
 \fIRapidCommit=\fR
@@ -2737,7 +2857,7 @@ Added in version 246\&.
 A whitespace\-separated list of IPv4 addresses\&. Each address can optionally take a prefix length after
 "/"\&. DHCP offers from servers in the list are accepted\&.
 .sp
-Note that this filters only DHCP offers, so the filtering may not work when
+Note that this filters only DHCP offers, so the filtering might not work when
 \fIRapidCommit=\fR
 is enabled\&. See also
 \fIRapidCommit=\fR
@@ -2760,7 +2880,7 @@ A boolean\&. When true,
 performs IPv4 Duplicate Address Detection to the acquired address by the DHCPv4 client\&. If duplicate is detected, the DHCPv4 client rejects the address by sending a
 \fBDHCPDECLINE\fR
 packet to the DHCP server, and tries to obtain an IP address again\&. See
-\m[blue]\fBRFC 5227\fR\m[]\&\s-2\u[11]\d\s+2\&. Defaults to false\&.
+\m[blue]\fBRFC 5227\fR\m[]\&\s-2\u[12]\d\s+2\&. Defaults to false\&.
 .sp
 Added in version 245\&.
 .RE
@@ -2820,7 +2940,7 @@ Send an arbitrary vendor option in the DHCPv6 request\&. Takes an enterprise ide
 "ipv4address",
 "ipv6address", or
 "string"\&. Special characters in the data string may be escaped using
-\m[blue]\fBC\-style escapes\fR\m[]\&\s-2\u[25]\d\s+2\&. This setting can be specified multiple times\&. If an empty string is specified, then all options specified earlier are cleared\&. Defaults to unset\&.
+\m[blue]\fBC\-style escapes\fR\m[]\&\s-2\u[27]\d\s+2\&. This setting can be specified multiple times\&. If an empty string is specified, then all options specified earlier are cleared\&. Defaults to unset\&.
 .sp
 Added in version 246\&.
 .RE
@@ -2828,7 +2948,7 @@ Added in version 246\&.
 \fIUserClass=\fR
 .RS 4
 A DHCPv6 client can use User Class option to identify the type or category of user or applications it represents\&. The information contained in this option is a string that represents the user class of which the client is a member\&. Each class sets an identifying string of information to be used by the DHCP service to classify clients\&. Special characters in the data string may be escaped using
-\m[blue]\fBC\-style escapes\fR\m[]\&\s-2\u[25]\d\s+2\&. This setting can be specified multiple times\&. If an empty string is specified, then all options specified earlier are cleared\&. Takes a whitespace\-separated list of strings\&. Note that currently
+\m[blue]\fBC\-style escapes\fR\m[]\&\s-2\u[27]\d\s+2\&. This setting can be specified multiple times\&. If an empty string is specified, then all options specified earlier are cleared\&. Takes a whitespace\-separated list of strings\&. Note that currently
 \fBNUL\fR
 bytes are not allowed\&.
 .sp
@@ -2854,7 +2974,7 @@ Added in version 244\&.
 \fIRapidCommit=\fR
 .RS 4
 Takes a boolean\&. The DHCPv6 client can obtain configuration parameters from a DHCPv6 server through a rapid two\-message exchange (solicit and reply)\&. When the rapid commit option is set by both the DHCPv6 client and the DHCPv6 server, the two\-message exchange is used\&. Otherwise, the four\-message exchange (solicit, advertise, request, and reply) is used\&. The two\-message exchange provides faster client configuration\&. See
-\m[blue]\fBRFC 3315\fR\m[]\&\s-2\u[29]\d\s+2
+\m[blue]\fBRFC 3315\fR\m[]\&\s-2\u[31]\d\s+2
 for details\&. Defaults to true, and the two\-message exchange will be used if the server support it\&.
 .sp
 Added in version 252\&.
@@ -2897,7 +3017,7 @@ When true (the default), the client will request the DHCPv6 server to delegate p
 \fIDHCPPrefixDelegation=yes\fR\&. See also the
 \fIDHCPPrefixDelegation=\fR
 setting in the [Network] section, settings in the [DHCPPrefixDelegation] section, and
-\m[blue]\fBRFC 8415\fR\m[]\&\s-2\u[30]\d\s+2\&.
+\m[blue]\fBRFC 8415\fR\m[]\&\s-2\u[32]\d\s+2\&.
 .sp
 Added in version 250\&.
 .RE
@@ -2971,7 +3091,7 @@ Added in version 250\&.
 \fISubnetId=\fR
 .RS 4
 Configure a specific subnet ID on the interface from a (previously) received prefix delegation\&. You can either set "auto" (the default) or a specific subnet ID (as defined in
-\m[blue]\fBRFC 4291\fR\m[]\&\s-2\u[31]\d\s+2, section 2\&.5\&.4), in which case the allowed value is hexadecimal, from 0 to 0x7fffffffffffffff inclusive\&.
+\m[blue]\fBRFC 4291\fR\m[]\&\s-2\u[33]\d\s+2, section 2\&.5\&.4), in which case the allowed value is hexadecimal, from 0 to 0x7fffffffffffffff inclusive\&.
 .sp
 Added in version 246\&.
 .RE
@@ -3053,6 +3173,13 @@ The [IPv6AcceptRA] section configures the IPv6 Router Advertisement (RA) client,
 \fIIPv6AcceptRA=\fR
 setting described above:
 .PP
+\fIUseRedirect=\fR
+.RS 4
+When true (the default), Redirect message sent by the current first\-hop router will be accepted, and configures routes to redirected nodes will be configured\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fIToken=\fR
 .RS 4
 Specifies an optional address generation mode for the Stateless Address Autoconfiguration (SLAAC)\&. The following values are supported:
@@ -3076,7 +3203,7 @@ Added in version 250\&.
 \fBprefixstable[:\fR\fB\fIADDRESS\fR\fR\fB][,\fR\fB\fIUUID\fR\fR\fB]\fR
 .RS 4
 The algorithm specified in
-\m[blue]\fBRFC 7217\fR\m[]\&\s-2\u[32]\d\s+2
+\m[blue]\fBRFC 7217\fR\m[]\&\s-2\u[34]\d\s+2
 will be used to generate interface identifiers\&. This mode can optionally take an IPv6 address separated with a colon (":")\&. If an IPv6 address is specified, then an interface identifier is generated only when a prefix received in an RA message matches the supplied address\&.
 .sp
 This mode can also optionally take a non\-null UUID in the format which
@@ -3203,11 +3330,18 @@ Takes a boolean\&. When true, the hop limit received in the Router Advertisement
 Added in version 255\&.
 .RE
 .PP
-\fIUseICMP6RateLimit=\fR
+\fIUseReachableTime=\fR
 .RS 4
-Takes a boolean\&. When true, the ICMP6 rate limit received in the Router Advertisement will be set to ICMP6 rate limit based on the advertisement\&. Defaults to true\&.
+Takes a boolean\&. When true, the reachable time received in the Router Advertisement will be set on the interface receiving the advertisement\&. It is used as the base timespan of the validity of a neighbor entry\&. Defaults to true\&.
 .sp
-Added in version 255\&.
+Added in version 256\&.
+.RE
+.PP
+\fIUseRetransmissionTime=\fR
+.RS 4
+Takes a boolean\&. When true, the retransmission time received in the Router Advertisement will be set on the interface receiving the advertisement\&. It is used as the time between retransmissions of Neighbor Solicitation messages to a neighbor when resolving the address or when probing the reachability of a neighbor\&. Defaults to true\&.
+.sp
+Added in version 256\&.
 .RE
 .PP
 \fIUseGateway=\fR
@@ -3238,7 +3372,7 @@ Added in version 254\&.
 When true, the IPv6 PREF64 (or NAT64) prefixes received in the Router Advertisement will be recorded and made available to client programs and displayed in the
 \fBnetworkctl\fR(1)
 status output per\-link\&. See
-\m[blue]\fBRFC 8781\fR\m[]\&\s-2\u[33]\d\s+2\&. Defaults to false\&.
+\m[blue]\fBRFC 8781\fR\m[]\&\s-2\u[35]\d\s+2\&. Defaults to false\&.
 .sp
 Added in version 255\&.
 .RE
@@ -3421,7 +3555,7 @@ ServerAddress=192\&.168\&.0\&.1/24
 .RE
 .\}
 .sp
-are equivalent to the following\&.
+are equivalent to the following:
 .sp
 .if n \{\
 .RS 4
@@ -3556,7 +3690,7 @@ Added in version 226\&.
 Takes an IPv4 address of the boot server used by e\&.g\&. PXE boot systems\&. When specified, this address is sent in the
 \fBsiaddr\fR
 field of the DHCP message header\&. See
-\m[blue]\fBRFC 2131\fR\m[]\&\s-2\u[34]\d\s+2
+\m[blue]\fBRFC 2131\fR\m[]\&\s-2\u[36]\d\s+2
 for more details\&. Defaults to unset\&.
 .sp
 Added in version 251\&.
@@ -3565,7 +3699,7 @@ Added in version 251\&.
 \fIBootServerName=\fR
 .RS 4
 Takes a name of the boot server used by e\&.g\&. PXE boot systems\&. When specified, this name is sent in the DHCP option 66 ("TFTP server name")\&. See
-\m[blue]\fBRFC 2132\fR\m[]\&\s-2\u[35]\d\s+2
+\m[blue]\fBRFC 2132\fR\m[]\&\s-2\u[37]\d\s+2
 for more details\&. Defaults to unset\&.
 .sp
 Note that typically setting one of
@@ -3580,7 +3714,7 @@ Added in version 251\&.
 \fIBootFilename=\fR
 .RS 4
 Takes a path or URL to a file loaded by e\&.g\&. a PXE boot loader\&. When specified, this path is sent in the DHCP option 67 ("Bootfile name")\&. See
-\m[blue]\fBRFC 2132\fR\m[]\&\s-2\u[35]\d\s+2
+\m[blue]\fBRFC 2132\fR\m[]\&\s-2\u[37]\d\s+2
 for more details\&. Defaults to unset\&.
 .sp
 Added in version 251\&.
@@ -3589,7 +3723,7 @@ Added in version 251\&.
 \fIIPv6OnlyPreferredSec=\fR
 .RS 4
 Takes a timespan\&. Controls the
-\m[blue]\fBRFC 8925\fR\m[]\&\s-2\u[28]\d\s+2
+\m[blue]\fBRFC 8925\fR\m[]\&\s-2\u[30]\d\s+2
 IPv6\-Only Preferred option\&. Specifies the DHCPv4 option to indicate that a host supports an IPv6\-only mode and is willing to forgo obtaining an IPv4 address if the network provides IPv6 connectivity\&. Defaults to unset, and not send the option\&. The minimum allowed value is 300 seconds\&.
 .sp
 Added in version 255\&.
@@ -3604,7 +3738,7 @@ Send a raw option with value via DHCPv4 server\&. Takes a DHCP option number, da
 "ipv4address",
 "ipv6address", or
 "string"\&. Special characters in the data string may be escaped using
-\m[blue]\fBC\-style escapes\fR\m[]\&\s-2\u[25]\d\s+2\&. This setting can be specified multiple times\&. If an empty string is specified, then all options specified earlier are cleared\&. Defaults to unset\&.
+\m[blue]\fBC\-style escapes\fR\m[]\&\s-2\u[27]\d\s+2\&. This setting can be specified multiple times\&. If an empty string is specified, then all options specified earlier are cleared\&. Defaults to unset\&.
 .sp
 Added in version 244\&.
 .RE
@@ -3617,7 +3751,7 @@ Send a vendor option with value via DHCPv4 server\&. Takes a DHCP option number,
 "uint32",
 "ipv4address", or
 "string"\&. Special characters in the data string may be escaped using
-\m[blue]\fBC\-style escapes\fR\m[]\&\s-2\u[25]\d\s+2\&. This setting can be specified multiple times\&. If an empty string is specified, then all options specified earlier are cleared\&. Defaults to unset\&.
+\m[blue]\fBC\-style escapes\fR\m[]\&\s-2\u[27]\d\s+2\&. This setting can be specified multiple times\&. If an empty string is specified, then all options specified earlier are cleared\&. Defaults to unset\&.
 .sp
 Added in version 246\&.
 .RE
@@ -3638,7 +3772,7 @@ Added in version 249\&.
 .RS 4
 Takes an IPv4 address, which must be in the format described in
 \fBinet_pton\fR(3)\&. Turns this DHCP server into a DHCP relay agent\&. See
-\m[blue]\fBRFC 1542\fR\m[]\&\s-2\u[36]\d\s+2\&. The address is the address of DHCP server or another relay agent to forward DHCP messages to and from\&.
+\m[blue]\fBRFC 1542\fR\m[]\&\s-2\u[38]\d\s+2\&. The address is the address of DHCP server or another relay agent to forward DHCP messages to and from\&.
 .sp
 Added in version 249\&.
 .RE
@@ -3670,10 +3804,22 @@ Added in version 249\&.
 \fIRapidCommit=\fR
 .RS 4
 Takes a boolean\&. When true, the server supports
-\m[blue]\fBRFC 4039\fR\m[]\&\s-2\u[37]\d\s+2\&. When a client sends a DHCPDISCOVER message with the Rapid Commit option to the server, then the server will reply with a DHCPACK message to the client, instead of DHCPOFFER\&. Defaults to true\&.
+\m[blue]\fBRFC 4039\fR\m[]\&\s-2\u[39]\d\s+2\&. When a client sends a DHCPDISCOVER message with the Rapid Commit option to the server, then the server will reply with a DHCPACK message to the client, instead of DHCPOFFER\&. Defaults to true\&.
 .sp
 Added in version 255\&.
 .RE
+.PP
+\fIPersistLeases=\fR
+.RS 4
+Takes a boolean\&. When true, the DHCP server will load and save leases in the persistent storage\&. When false, the DHCP server will neither load nor save leases in the persistent storage\&. Hence, bound leases will be lost when the interface is reconfigured e\&.g\&. by
+\fBnetworkctl reconfigure\fR, or
+systemd\-networkd\&.service
+is restarted\&. That may cause address conflict on the network\&. So, please take an extra care when disable this setting\&. When unspecified, the value specified in the same setting in
+\fBnetworkd.conf\fR(5), which defaults to
+"yes", will be used\&.
+.sp
+Added in version 256\&.
+.RE
 .SH "[DHCPSERVERSTATICLEASE] SECTION OPTIONS"
 .PP
 The
@@ -3722,9 +3868,16 @@ Takes a timespan\&. Configures the IPv6 router lifetime in seconds\&. The value
 Added in version 235\&.
 .RE
 .PP
+\fIReachableTimeSec=\fR
+.RS 4
+Configures the time, used in the Neighbor Unreachability Detection algorithm, for which clients can assume a neighbor is reachable after having received a reachability confirmation\&. Takes a time span in the range 0\&...4294967295 ms\&. When 0, clients will handle it as if the value wasn\*(Aqt specified\&. Defaults to 0\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fIRetransmitSec=\fR
 .RS 4
-Takes a timespan\&. Configures the retransmit time, used by clients to retransmit Neighbor Solicitation messages on address resolution and the Neighbor Unreachability Detection algorithm\&. An integer the default unit of seconds, in the range 0\&...4294967295 msec\&. Defaults to 0\&.
+Configures the time, used in the Neighbor Unreachability Detection algorithm, for which clients can use as retransmit time on address resolution and the Neighbor Unreachability Detection algorithm\&. Takes a time span in the range 0\&...4294967295 ms\&. When 0, clients will handle it as if the value wasn\*(Aqt specified\&. Defaults to 0\&.
 .sp
 Added in version 255\&.
 .RE
@@ -3744,7 +3897,7 @@ and
 added as synonyms for
 "medium"
 just to make configuration easier\&. See
-\m[blue]\fBRFC 4191\fR\m[]\&\s-2\u[21]\d\s+2
+\m[blue]\fBRFC 4191\fR\m[]\&\s-2\u[23]\d\s+2
 for details\&. Defaults to
 "medium"\&.
 .sp
@@ -3824,8 +3977,8 @@ Added in version 235\&.
 .PP
 \fIHomeAgent=\fR
 .RS 4
-Takes a boolean\&. Specifies that IPv6 router advertisements which indicates to hosts that the router acts as a Home Agent and includes a Home Agent Option\&. Defaults to false\&. See
-\m[blue]\fBRFC 6275\fR\m[]\&\s-2\u[10]\d\s+2
+Takes a boolean\&. Specifies that IPv6 router advertisements which indicate to hosts that the router acts as a Home Agent and includes a Home Agent option\&. Defaults to false\&. See
+\m[blue]\fBRFC 6275\fR\m[]\&\s-2\u[11]\d\s+2
 for further details\&.
 .sp
 Added in version 255\&.
@@ -3833,7 +3986,7 @@ Added in version 255\&.
 .PP
 \fIHomeAgentLifetimeSec=\fR
 .RS 4
-Takes a timespan\&. Specifies the lifetime of the Home Agent\&. An integer the default unit of seconds, in the range 1\&...65535\&. Defaults to the value set to
+Takes a timespan\&. Specifies the lifetime of the Home Agent\&. An integer, the default unit is seconds, in the range 1\&...65535\&. Defaults to the value set to
 \fIRouterLifetimeSec=\fR\&.
 .sp
 Added in version 255\&.
@@ -3848,7 +4001,7 @@ Added in version 255\&.
 .SH "[IPV6PREFIX] SECTION OPTIONS"
 .PP
 One or more [IPv6Prefix] sections contain the IPv6 prefixes that are announced via Router Advertisements\&. See
-\m[blue]\fBRFC 4861\fR\m[]\&\s-2\u[38]\d\s+2
+\m[blue]\fBRFC 4861\fR\m[]\&\s-2\u[40]\d\s+2
 for further details\&.
 .PP
 \fIAddressAutoconfiguration=\fR, \fIOnLink=\fR
@@ -3909,7 +4062,7 @@ Added in version 249\&.
 .SH "[IPV6ROUTEPREFIX] SECTION OPTIONS"
 .PP
 One or more [IPv6RoutePrefix] sections contain the IPv6 prefix routes that are announced via Router Advertisements\&. See
-\m[blue]\fBRFC 4191\fR\m[]\&\s-2\u[21]\d\s+2
+\m[blue]\fBRFC 4191\fR\m[]\&\s-2\u[23]\d\s+2
 for further details\&.
 .PP
 \fIRoute=\fR
@@ -3932,7 +4085,7 @@ Added in version 244\&.
 .SH "[IPV6PREF64PREFIX] SECTION OPTIONS"
 .PP
 One or more [IPv6PREF64Prefix] sections contain the IPv6 PREF64 (or NAT64) prefixes that are announced via Router Advertisements\&. See
-\m[blue]\fBRFC 8781\fR\m[]\&\s-2\u[33]\d\s+2
+\m[blue]\fBRFC 8781\fR\m[]\&\s-2\u[35]\d\s+2
 for further details\&.
 .PP
 \fIPrefix=\fR
@@ -5507,14 +5660,14 @@ Added in version 246\&.
 .RE
 .SH "[BRIDGEVLAN] SECTION OPTIONS"
 .PP
-The [BridgeVLAN] section manages the VLAN ID configuration of a bridge port and accepts the following keys\&. Specify several [BridgeVLAN] sections to configure several VLAN entries\&. The
+The [BridgeVLAN] section manages the VLAN ID configurations of a bridge master or port, and accepts the following keys\&. To make the settings in this section take an effect,
 \fIVLANFiltering=\fR
-option has to be enabled, see the [Bridge] section in
-\fBsystemd.netdev\fR(5)\&.
+option has to be enabled on the bridge master, see the [Bridge] section in
+\fBsystemd.netdev\fR(5)\&. If at least one valid settings specified in this section in a \&.network file for an interface, all assigned VLAN IDs on the interface that are not configured in the \&.network file will be removed\&. If VLAN IDs on an interface need to be managed by other tools, then the settings in this section cannot be used in the matching \&.network file\&.
 .PP
 \fIVLAN=\fR
 .RS 4
-The VLAN ID allowed on the port\&. This can be either a single ID or a range M\-N\&. Takes an integer in the range 1\&...4094\&.
+The VLAN ID allowed on the port\&. This can be either a single ID or a range M\-N\&. Takes an integer in the range 1\&...4094\&. This setting can be specified multiple times\&. If an empty string is assigned, then the all previous assignments are cleared\&.
 .sp
 Added in version 231\&.
 .RE
@@ -5525,20 +5678,19 @@ The VLAN ID specified here will be used to untag frames on egress\&. Configuring
 \fIEgressUntagged=\fR
 implicates the use of
 \fIVLAN=\fR
-above and will enable the VLAN ID for ingress as well\&. This can be either a single ID or a range M\-N\&.
+above and will enable the VLAN ID for ingress as well\&. This can be either a single ID or a range M\-N\&. This setting can be specified multiple times\&. If an empty string is assigned, then the all previous assignments are cleared\&.
 .sp
 Added in version 231\&.
 .RE
 .PP
 \fIPVID=\fR
 .RS 4
-The Port VLAN ID specified here is assigned to all untagged frames at ingress\&.
-\fIPVID=\fR
-can be used only once\&. Configuring
+The port VLAN ID specified here is assigned to all untagged frames at ingress\&. Takes an VLAN ID or negative boolean value (e\&.g\&.
+"no")\&. When false, the currently assigned port VLAN ID will be dropped\&. Configuring
 \fIPVID=\fR
 implicates the use of
 \fIVLAN=\fR
-above and will enable the VLAN ID for ingress as well\&.
+setting in the above and will enable the VLAN ID for ingress as well\&. Defaults to unset, and will keep the assigned port VLAN ID if exists\&.
 .sp
 Added in version 231\&.
 .RE
@@ -6031,12 +6183,7 @@ nic\&. If offloading is not needed, xfrm interfaces can be assigned to the
 device\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-networkd.service\fR(8),
-\fBsystemd.link\fR(5),
-\fBsystemd.netdev\fR(5),
-\fBsystemd-network-generator.service\fR(8),
-\fBsystemd-resolved.service\fR(8)
+\fBsystemd\fR(1), \fBsystemd-networkd.service\fR(8), \fBsystemd.link\fR(5), \fBsystemd.netdev\fR(5), \fBsystemd-network-generator.service\fR(8), \fBsystemd-resolved.service\fR(8)
 .SH "NOTES"
 .IP " 1." 4
 System and Service Credentials
@@ -6084,146 +6231,156 @@ RFC 3704
 \%https://tools.ietf.org/html/rfc1027
 .RE
 .IP "10." 4
+RFC 3069
+.RS 4
+\%https://tools.ietf.org/html/rfc3069
+.RE
+.IP "11." 4
 RFC 6275
 .RS 4
 \%https://tools.ietf.org/html/rfc6275
 .RE
-.IP "11." 4
+.IP "12." 4
 RFC 5227
 .RS 4
 \%https://tools.ietf.org/html/rfc5227
 .RE
-.IP "12." 4
+.IP "13." 4
 RFC 4862
 .RS 4
 \%https://tools.ietf.org/html/rfc4862
 .RE
-.IP "13." 4
+.IP "14." 4
 RFC 3041
 .RS 4
 \%https://tools.ietf.org/html/rfc3041
 .RE
-.IP "14." 4
+.IP "15." 4
 NetLabel
 .RS 4
 \%https://docs.kernel.org/netlabel/index.html
 .RE
-.IP "15." 4
+.IP "16." 4
 Linux Security Modules (LSMs)
 .RS 4
 \%https://en.wikipedia.org/wiki/Linux_Security_Modules
 .RE
-.IP "16." 4
+.IP "17." 4
 NetLabel Fallback Peer Labeling
 .RS 4
 \%https://github.com/SELinuxProject/selinux-notebook/blob/main/src/network_support.md
 .RE
-.IP "17." 4
+.IP "18." 4
 NFT
 .RS 4
 \%https://netfilter.org/projects/nftables/index.html
 .RE
-.IP "18." 4
+.IP "19." 4
 RFC 3484
 .RS 4
 \%https://tools.ietf.org/html/rfc3484
 .RE
-.IP "19." 4
+.IP "20." 4
 Type of Service
 .RS 4
 \%https://en.wikipedia.org/wiki/Type_of_service
 .RE
-.IP "20." 4
+.IP "21." 4
 Differentiated services
 .RS 4
 \%https://en.wikipedia.org/wiki/Differentiated_services
 .RE
-.IP "21." 4
+.IP "22." 4
+Virtual Routing and Forwarding (VRF)
+.RS 4
+\%https://docs.kernel.org/networking/vrf.html
+.RE
+.IP "23." 4
 RFC 4191
 .RS 4
 \%https://tools.ietf.org/html/rfc4191
 .RE
-.IP "22." 4
+.IP "24." 4
 RFC 8520
 .RS 4
 \%https://tools.ietf.org/html/rfc8520
 .RE
-.IP "23." 4
+.IP "25." 4
 RFC 4039
 .RS 4
 \%https://tools.ietf.org/html/rfc4039
 .RE
-.IP "24." 4
+.IP "26." 4
 RFC 7844
 .RS 4
 \%https://tools.ietf.org/html/rfc7844
 .RE
-.IP "25." 4
+.IP "27." 4
 C-style escapes
 .RS 4
 \%https://en.wikipedia.org/wiki/Escape_sequences_in_C#Table_of_escape_sequences
 .RE
-.IP "26." 4
+.IP "28." 4
 RFC 3442
 .RS 4
 \%https://datatracker.ietf.org/doc/html/rfc3442
 .RE
-.IP "27." 4
+.IP "29." 4
 RFC 5969
 .RS 4
 \%https://tools.ietf.org/html/rfc5969
 .RE
-.IP "28." 4
+.IP "30." 4
 RFC 8925
 .RS 4
 \%https://tools.ietf.org/html/rfc8925
 .RE
-.IP "29." 4
+.IP "31." 4
 RFC 3315
 .RS 4
 \%https://tools.ietf.org/html/rfc3315#section-17.2.1
 .RE
-.IP "30." 4
+.IP "32." 4
 RFC 8415
 .RS 4
 \%https://www.rfc-editor.org/rfc/rfc8415.html#section-6.3
 .RE
-.IP "31." 4
+.IP "33." 4
 RFC 4291
 .RS 4
 \%https://tools.ietf.org/html/rfc4291#section-2.5.4
 .RE
-.IP "32." 4
+.IP "34." 4
 RFC 7217
 .RS 4
 \%https://tools.ietf.org/html/rfc7217
 .RE
-.IP "33." 4
+.IP "35." 4
 RFC 8781
 .RS 4
 \%https://tools.ietf.org/html/rfc8781
 .RE
-.IP "34." 4
+.IP "36." 4
 RFC 2131
 .RS 4
 \%https://www.rfc-editor.org/rfc/rfc2131.html
 .RE
-.IP "35." 4
+.IP "37." 4
 RFC 2132
 .RS 4
 \%https://www.rfc-editor.org/rfc/rfc2132.html
 .RE
-.IP "36." 4
+.IP "38." 4
 RFC 1542
 .RS 4
 \%https://tools.ietf.org/html/rfc1542
 .RE
-.IP "37." 4
+.IP "39." 4
 RFC 4039
 .RS 4
 \%https://datatracker.ietf.org/doc/html/rfc4039
 .RE
-.IP "38." 4
+.IP "40." 4
 RFC 4861
 .RS 4
 \%https://tools.ietf.org/html/rfc4861
diff --git a/upstream/fedora-rawhide/man5/systemd.nspawn.5 b/upstream/fedora-rawhide/man5/systemd.nspawn.5
index 0c441ba1..5bb98a83 100644
--- a/upstream/fedora-rawhide/man5/systemd.nspawn.5
+++ b/upstream/fedora-rawhide/man5/systemd.nspawn.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.NSPAWN" "5" "" "systemd 255" "systemd.nspawn"
+.TH "SYSTEMD\&.NSPAWN" "5" "" "systemd 256~rc3" "systemd.nspawn"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,11 +23,15 @@
 systemd.nspawn \- Container settings
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/systemd/nspawn/\fImachine\fR\&.nspawn
-.PP
+.RE
+.RS 4
 /run/systemd/nspawn/\fImachine\fR\&.nspawn
-.PP
+.RE
+.RS 4
 /var/lib/machines/\fImachine\fR\&.nspawn
+.RE
 .SH "DESCRIPTION"
 .PP
 An nspawn container settings file (suffix
@@ -587,6 +591,4 @@ Added in version 226\&.
 .RE
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-nspawn\fR(1),
-\fBsystemd.directives\fR(7)
+\fBsystemd\fR(1), \fBsystemd-nspawn\fR(1), \fBsystemd.directives\fR(7)
diff --git a/upstream/fedora-rawhide/man5/systemd.path.5 b/upstream/fedora-rawhide/man5/systemd.path.5
index 9fbc4d47..11d47179 100644
--- a/upstream/fedora-rawhide/man5/systemd.path.5
+++ b/upstream/fedora-rawhide/man5/systemd.path.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.PATH" "5" "" "systemd 255" "systemd.path"
+.TH "SYSTEMD\&.PATH" "5" "" "systemd 256~rc3" "systemd.path"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -203,9 +203,4 @@ in
 \fBsystemd.exec\fR(5)
 for more details\&.
 .PP
-\fBsystemd\fR(1),
-\fBsystemctl\fR(1),
-\fBsystemd.unit\fR(5),
-\fBsystemd.service\fR(5),
-\fBinotify\fR(7),
-\fBsystemd.directives\fR(7)
+\fBsystemd\fR(1), \fBsystemctl\fR(1), \fBsystemd.unit\fR(5), \fBsystemd.service\fR(5), \fBinotify\fR(7), \fBsystemd.directives\fR(7)
diff --git a/upstream/fedora-rawhide/man5/systemd.pcrlock.5 b/upstream/fedora-rawhide/man5/systemd.pcrlock.5
index cadc0742..a3eecafe 100644
--- a/upstream/fedora-rawhide/man5/systemd.pcrlock.5
+++ b/upstream/fedora-rawhide/man5/systemd.pcrlock.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.PCRLOCK" "5" "" "systemd 255" "systemd.pcrlock"
+.TH "SYSTEMD\&.PCRLOCK" "5" "" "systemd 256~rc3" "systemd.pcrlock"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,25 +23,43 @@
 systemd.pcrlock, systemd.pcrlock.d \- PCR measurement prediction files
 .SH "SYNOPSIS"
 .PP
-.nf
+.RS 4
 /etc/pcrlock\&.d/*\&.pcrlock
+.RE
+.RS 4
 /etc/pcrlock\&.d/*\&.pcrlock\&.d/*\&.pcrlock
+.RE
+.RS 4
 /run/pcrlock\&.d/*\&.pcrlock
+.RE
+.RS 4
 /run/pcrlock\&.d/*\&.pcrlock\&.d/*\&.pcrlock
+.RE
+.RS 4
 /var/lib/pcrlock\&.d/*\&.pcrlock
+.RE
+.RS 4
 /var/lib/pcrlock\&.d/*\&.pcrlock\&.d/*\&.pcrlock
+.RE
+.RS 4
 /usr/local/pcrlock\&.d/*\&.pcrlock
+.RE
+.RS 4
 /usr/local/pcrlock\&.d/*\&.pcrlock\&.d/*\&.pcrlock
+.RE
+.RS 4
 /usr/lib/pcrlock\&.d/*\&.pcrlock
+.RE
+.RS 4
 /usr/lib/pcrlock\&.d/*\&.pcrlock\&.d/*\&.pcrlock
-.fi
+.RE
 .SH "DESCRIPTION"
 .PP
 *\&.pcrlock
 files define expected TPM2 PCR measurements of components involved in the boot process\&.
 \fBsystemd-pcrlock\fR(1)
 uses such pcrlock files to analyze and predict TPM2 PCR measurements\&. The pcrlock files are JSON arrays that follow a subset of the
-\m[blue]\fBTCG Common Event Log Format (CEL\-JSON)\fR\m[]\&\s-2\u[1]\d\s+2
+\m[blue]\fBTCG Canonical Event Log Format (CEL\-JSON)\fR\m[]\&\s-2\u[1]\d\s+2
 specification\&. Specifically the
 "recnum",
 "content", and
@@ -90,7 +108,7 @@ Added in version 255\&.
 250\-firmware\-code\-early\&.pcrlock
 .RS 4
 Firmware code measurements, as recorded to PCR 0 and 2, up to the separator measurement (see
-400\-secureboot\-separator\&.pcrlock\&.
+400\-secureboot\-separator\&.pcrlock
 below)\&. May be generated via
 \fBsystemd\-pcrlock lock\-firmware\-code\fR\&.
 .sp
@@ -100,7 +118,7 @@ Added in version 255\&.
 250\-firmware\-config\-early\&.pcrlock
 .RS 4
 Firmware configuration measurements, as recorded to PCR 1 and 3, up to the separator measurement (see
-400\-secureboot\-separator\&.pcrlock\&.
+400\-secureboot\-separator\&.pcrlock
 below)\&. May be generated via
 \fBsystemd\-pcrlock lock\-firmware\-config\fR\&.
 .sp
@@ -131,7 +149,7 @@ Added in version 255\&.
 550\-firmware\-code\-late\&.pcrlock
 .RS 4
 Firmware code measurements, as recorded to PCR 0 and 2, after the separator measurement (see
-400\-secureboot\-separator\&.pcrlock\&.
+400\-secureboot\-separator\&.pcrlock
 above)\&. May be generated via
 \fBsystemd\-pcrlock lock\-firmware\-code\fR\&.
 .sp
@@ -141,7 +159,7 @@ Added in version 255\&.
 550\-firmware\-config\-late\&.pcrlock
 .RS 4
 Firmware configuration measurements, as recorded to PCR 1 and 3, after the separator measurement (see
-400\-secureboot\-separator\&.pcrlock\&.
+400\-secureboot\-separator\&.pcrlock
 above)\&. May be generated via
 \fBsystemd\-pcrlock lock\-firmware\-config\fR\&.
 .sp
@@ -168,7 +186,7 @@ Added in version 255\&.
 .RS 4
 The EFI action generated when
 \fBExitBootServices()\fR
-is generated, i\&.e\&. the UEFI environment is left and the OS takes over\&. Covers the PCR 5 measurement\&. Statically defined\&.
+is generated, i\&.e\&. when the UEFI environment is left and the OS takes over\&. Covers the PCR 5 measurement\&. Statically defined\&.
 .sp
 Added in version 255\&.
 .RE
@@ -266,11 +284,10 @@ Added in version 255\&.
 .RE
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-pcrlock\fR(1)
+\fBsystemd\fR(1), \fBsystemd-pcrlock\fR(1)
 .SH "NOTES"
 .IP " 1." 4
-TCG Common Event Log Format (CEL-JSON)
+TCG Canonical Event Log Format (CEL-JSON)
 .RS 4
 \%https://trustedcomputinggroup.org/resource/canonical-event-log-format/
 .RE
diff --git a/upstream/fedora-rawhide/man5/systemd.preset.5 b/upstream/fedora-rawhide/man5/systemd.preset.5
index 945e0d62..c75ee687 100644
--- a/upstream/fedora-rawhide/man5/systemd.preset.5
+++ b/upstream/fedora-rawhide/man5/systemd.preset.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.PRESET" "5" "" "systemd 255" "systemd.preset"
+.TH "SYSTEMD\&.PRESET" "5" "" "systemd 256~rc3" "systemd.preset"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,17 +23,24 @@
 systemd.preset \- Service enablement presets
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/systemd/system\-preset/*\&.preset
-.PP
+.RE
+.RS 4
 /run/systemd/system\-preset/*\&.preset
-.PP
+.RE
+.RS 4
 /usr/lib/systemd/system\-preset/*\&.preset
-.PP
+.RE
+.RS 4
 /etc/systemd/user\-preset/*\&.preset
-.PP
+.RE
+.RS 4
 /run/systemd/user\-preset/*\&.preset
-.PP
+.RE
+.RS 4
 /usr/lib/systemd/user\-preset/*\&.preset
+.RE
 .SH "DESCRIPTION"
 .PP
 Preset files may be used to encode policy which units shall be enabled by default and which ones shall be disabled\&. They are read by
@@ -45,7 +52,7 @@ is identical to
 or
 \fBsystemctl disable\fR\&.
 \fBsystemctl preset\fR
-is used by the post install scriptlets of rpm packages (or other OS package formats), to enable/disable specific units by default on package installation, enforcing distribution, spin or administrator preset policy\&. This allows choosing a certain set of units to be enabled/disabled even before installing the actual package\&. For more information, see
+is used by the post install scriptlets of rpm packages (or other OS package formats), to enable/disable specific units by default on package installation, enforcing distribution, spin, or administrator preset policy\&. This allows choosing a certain set of units to be enabled/disabled even before installing the actual package\&. For more information, see
 \fBsystemctl\fR(1)\&.
 .PP
 It is not recommended to ship preset files within the respective software packages implementing the units, but rather centralize them in a distribution or spin default policy, which can be amended by administrator policy, see below\&.
@@ -55,7 +62,11 @@ If no preset files exist, preset operations will enable all units that are insta
 When the machine is booted for the first time,
 \fBsystemd\fR(1)
 will enable/disable all units according to preset policy, similarly to
-\fBsystemctl preset\-all\fR\&. Also see "First Boot Semantics" in
+\fBsystemctl preset\-all\fR\&. Also see
+\fIConditionFirstBoot=\fR
+in
+\fBsystemd.unit\fR(5)
+and "First Boot Semantics" in
 \fBmachine-id\fR(5)\&.
 .SH "PRESET FILE FORMAT"
 .PP
@@ -203,9 +214,7 @@ The preset mechanism allows clean separation of the enablement mechanism (inside
 \fBsystemctl preset\fR) and enablement policy (centralized in the preset files), and lifts the configuration out of individual packages\&. Preset files may be written for specific distributions, for specific spins or for specific sites, in order to enforce different policies as needed\&. It is recommended to apply the policy encoded in preset files in package installation scriptlets\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemctl\fR(1),
-\fBsystemd-delta\fR(1)
+\fBsystemd\fR(1), \fBsystemctl\fR(1), \fBsystemd-delta\fR(1)
 .PP
 \fBdaemon\fR(7)
 has a discussion of packaging scriptlets\&.
diff --git a/upstream/fedora-rawhide/man5/systemd.resource-control.5 b/upstream/fedora-rawhide/man5/systemd.resource-control.5
index 3e1a9ae0..a2829b60 100644
--- a/upstream/fedora-rawhide/man5/systemd.resource-control.5
+++ b/upstream/fedora-rawhide/man5/systemd.resource-control.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.RESOURCE\-CONTROL" "5" "" "systemd 255" "systemd.resource-control"
+.TH "SYSTEMD\&.RESOURCE\-CONTROL" "5" "" "systemd 256~rc3" "systemd.resource-control"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -161,6 +161,7 @@ user\-\fInnn\fR\&.slice\&. Drop\-ins with local configuration that affect user 1
 /etc/systemd/system/user\-1000\&.slice,
 /etc/systemd/system/user\-1000\&.slice\&.d/*\&.conf, but also
 /etc/systemd/system/user\-\&.slice\&.d/*\&.conf\&. This last directory applies to all user slices\&.
+.SS ""
 .PP
 See the
 \m[blue]\fBNew Control Group Interfaces\fR\m[]\&\s-2\u[1]\d\s+2
@@ -422,7 +423,10 @@ Takes a memory size in bytes\&. If the value is suffixed with K, M, G or T, the
 "infinity", no memory throttling is applied\&. This controls the
 "memory\&.high"
 control group attribute\&. For details about this control group attribute, see
-\m[blue]\fBMemory Interface Files\fR\m[]\&\s-2\u[5]\d\s+2\&.
+\m[blue]\fBMemory Interface Files\fR\m[]\&\s-2\u[5]\d\s+2\&. The effective configuration is reported as
+\fIEffectiveMemoryHigh=\fR
+(see also
+\fIEffectiveMemoryMax=\fR)\&.
 .sp
 While
 \fIStartupMemoryHigh=\fR
@@ -451,7 +455,9 @@ Takes a memory size in bytes\&. If the value is suffixed with K, M, G or T, the
 "infinity", no memory limit is applied\&. This controls the
 "memory\&.max"
 control group attribute\&. For details about this control group attribute, see
-\m[blue]\fBMemory Interface Files\fR\m[]\&\s-2\u[5]\d\s+2\&.
+\m[blue]\fBMemory Interface Files\fR\m[]\&\s-2\u[5]\d\s+2\&. The effective configuration is reported as
+\fIEffectiveMemoryMax=\fR
+(the value is the most stringent limit of the unit and parent slices and it is capped by physical memory)\&.
 .sp
 While
 \fIStartupMemoryMax=\fR
@@ -516,6 +522,19 @@ allows prioritizing specific services at boot\-up and shutdown differently than
 Added in version 253\&.
 .RE
 .PP
+\fIMemoryZSwapWriteback=\fR
+.RS 4
+This setting controls the
+\fBmemory\fR
+controller in the unified hierarchy\&.
+.sp
+Takes a boolean argument\&. When true, pages stored in the Zswap cache are permitted to be written to the backing storage, false otherwise\&. Defaults to true\&. This allows disabling writeback of swap pages for IO\-intensive applications, while retaining the ability to store compressed pages in Zswap\&. See the kernel\*(Aqs
+\m[blue]\fBZswap\fR\m[]\&\s-2\u[6]\d\s+2
+documentation for more details\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fIAllowedMemoryNodes=\fR, \fIStartupAllowedMemoryNodes=\fR
 .RS 4
 These settings control the
@@ -569,7 +588,8 @@ Specify the maximum number of tasks that may be created in the unit\&. This ensu
 "infinity", no tasks limit is applied\&. This controls the
 "pids\&.max"
 control group attribute\&. For details about this control group attribute, the
-\m[blue]\fBpids controller\fR\m[]\&\s-2\u[7]\d\s+2\&.
+\m[blue]\fBpids controller\fR\m[]\&\s-2\u[7]\d\s+2\&. The effective configuration is reported as
+\fIEffectiveTasksMax=\fR\&.
 .sp
 The system default for this setting may be controlled with
 \fIDefaultTasksMax=\fR
@@ -702,6 +722,8 @@ The system default for this setting may be controlled with
 in
 \fBsystemd-system.conf\fR(5)\&.
 .sp
+Note that this functionality is currently only available for system services, not for per\-user services\&.
+.sp
 Added in version 235\&.
 .RE
 .PP
@@ -833,9 +855,9 @@ Added in version 235\&.
 .PP
 \fISocketBindAllow=\fR\fI\fIbind\-rule\fR\fR, \fISocketBindDeny=\fR\fI\fIbind\-rule\fR\fR
 .RS 4
-Allow or deny binding a socket address to a socket by matching it with the
-\fIbind\-rule\fR
-and applying a corresponding action if there is a match\&.
+Configures restrictions on the ability of unit processes to invoke
+\fBbind\fR(2)
+on a socket\&. Both allow and deny rules may defined that restrict which addresses a socket may be bound to\&.
 .sp
 \fIbind\-rule\fR
 describes socket properties such as
@@ -964,6 +986,11 @@ and
 \fBcgroup/bind6\fR
 cgroup\-bpf hooks\&.
 .sp
+Note that these settings apply to any
+\fBbind\fR(2)
+system call invocation by the unit processes, regardless in which network namespace they are placed\&. Or in other words: changing the network namespace is not a suitable mechanism for escaping these restrictions on
+\fBbind()\fR\&.
+.sp
 Examples:
 .sp
 .if n \{\
@@ -1739,20 +1766,7 @@ Added in version 252\&.
 .RE
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-system.conf\fR(5),
-\fBsystemd.unit\fR(5),
-\fBsystemd.service\fR(5),
-\fBsystemd.slice\fR(5),
-\fBsystemd.scope\fR(5),
-\fBsystemd.socket\fR(5),
-\fBsystemd.mount\fR(5),
-\fBsystemd.swap\fR(5),
-\fBsystemd.exec\fR(5),
-\fBsystemd.directives\fR(7),
-\fBsystemd.special\fR(7),
-\fBsystemd-oomd.service\fR(8), The documentation for control groups and specific controllers in the Linux kernel:
-\m[blue]\fBControl Groups v2\fR\m[]\&\s-2\u[2]\d\s+2\&.
+\fBsystemd\fR(1), \fBsystemd-system.conf\fR(5), \fBsystemd.unit\fR(5), \fBsystemd.service\fR(5), \fBsystemd.slice\fR(5), \fBsystemd.scope\fR(5), \fBsystemd.socket\fR(5), \fBsystemd.mount\fR(5), \fBsystemd.swap\fR(5), \fBsystemd.exec\fR(5), \fBsystemd.directives\fR(7), \fBsystemd.special\fR(7), \fBsystemd-oomd.service\fR(8), The documentation for control groups and specific controllers in the Linux kernel: \m[blue]\fBControl Groups v2\fR\m[]\&\s-2\u[2]\d\s+2
 .SH "NOTES"
 .IP " 1." 4
 New Control Group Interfaces
@@ -1782,12 +1796,12 @@ Memory Interface Files
 .IP " 6." 4
 Zswap
 .RS 4
-\%https://www.kernel.org/doc/html/latest/admin-guide/mm/zswap.html
+\%https://docs.kernel.org/admin-guide/mm/zswap.html
 .RE
 .IP " 7." 4
 pids controller
 .RS 4
-\%https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html#pid
+\%https://docs.kernel.org/admin-guide/cgroup-v2.html#pid
 .RE
 .IP " 8." 4
 IO Interface Files
diff --git a/upstream/fedora-rawhide/man5/systemd.scope.5 b/upstream/fedora-rawhide/man5/systemd.scope.5
index 64cb28d7..45f17811 100644
--- a/upstream/fedora-rawhide/man5/systemd.scope.5
+++ b/upstream/fedora-rawhide/man5/systemd.scope.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.SCOPE" "5" "" "systemd 255" "systemd.scope"
+.TH "SYSTEMD\&.SCOPE" "5" "" "systemd 256~rc3" "systemd.scope"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -121,7 +121,7 @@ This setting also applies to
 \fBsystemd\-oomd\fR
 kills a cgroup associated with it\&.
 .sp
-Added in version 243\&.
+Added in version 253\&.
 .RE
 .PP
 \fIRuntimeMaxSec=\fR
@@ -151,12 +151,7 @@ Check
 for more settings\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-run\fR(1),
-\fBsystemd.unit\fR(5),
-\fBsystemd.resource-control\fR(5),
-\fBsystemd.service\fR(5),
-\fBsystemd.directives\fR(7)\&.
+\fBsystemd\fR(1), \fBsystemd-run\fR(1), \fBsystemd.unit\fR(5), \fBsystemd.resource-control\fR(5), \fBsystemd.service\fR(5), \fBsystemd.directives\fR(7)\&.
 .SH "NOTES"
 .IP " 1." 4
 New Control Group Interfaces
diff --git a/upstream/fedora-rawhide/man5/systemd.service.5 b/upstream/fedora-rawhide/man5/systemd.service.5
index 098eba50..a53894ed 100644
--- a/upstream/fedora-rawhide/man5/systemd.service.5
+++ b/upstream/fedora-rawhide/man5/systemd.service.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.SERVICE" "5" "" "systemd 255" "systemd.service"
+.TH "SYSTEMD\&.SERVICE" "5" "" "systemd 256~rc3" "systemd.service"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -1079,7 +1079,13 @@ If set to
 \fBon\-abnormal\fR, the service will be restarted when the process is terminated by a signal (including on core dump, excluding the aforementioned four signals), when an operation times out, or when the watchdog timeout is triggered\&. If set to
 \fBon\-abort\fR, the service will be restarted only if the service process exits due to an uncaught signal not specified as a clean exit status\&. If set to
 \fBon\-watchdog\fR, the service will be restarted only if the watchdog timeout for the service expires\&. If set to
-\fBalways\fR, the service will be restarted regardless of whether it exited cleanly or not, got terminated abnormally by a signal, or hit a timeout\&.
+\fBalways\fR, the service will be restarted regardless of whether it exited cleanly or not, got terminated abnormally by a signal, or hit a timeout\&. Note that
+\fIType=oneshot\fR
+services will never be restarted on a clean exit status, i\&.e\&.
+\fBalways\fR
+and
+\fBon\-success\fR
+are rejected for them\&.
 .sp
 .it 1 an-trap
 .nr an-no-space-flag 1
@@ -1316,21 +1322,9 @@ Added in version 189\&.
 \fIRestartPreventExitStatus=\fR
 .RS 4
 Takes a list of exit status definitions that, when returned by the main service process, will prevent automatic service restarts, regardless of the restart setting configured with
-\fIRestart=\fR\&. Exit status definitions can either be numeric exit codes or termination signal names, and are separated by spaces\&. Defaults to the empty list, so that, by default, no exit status is excluded from the configured restart logic\&. For example:
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-RestartPreventExitStatus=1 6 SIGABRT
-.fi
-.if n \{\
-.RE
-.\}
-.sp
-ensures that exit codes 1 and 6 and the termination signal
-\fBSIGABRT\fR
-will not result in automatic service restarting\&. This option may appear more than once, in which case the list of restart\-preventing statuses is merged\&. If the empty string is assigned to this option, the list is reset and all prior assignments of this option will have no effect\&.
+\fIRestart=\fR\&. Exit status definitions can be numeric termination statuses, termination status names, or termination signal names, separated by spaces\&. Defaults to the empty list, so that, by default, no exit status is excluded from the configured restart logic\&.
+.PP \fBExample\ \&2.\ \&A service with the \fIRestartPreventExitStatus=\fR setting\fR .sp .if n \{\ .RS 4 .\} .nf RestartPreventExitStatus=TEMPFAIL 250 SIGKILL .fi .if n \{\ .RE .\} .sp Exit status 75 (\fBTEMPFAIL\fR), 250, and the termination signal \fBSIGKILL\fR will not result in automatic service restarting\&.
+This option may appear more than once, in which case the list of restart\-preventing statuses is merged\&. If the empty string is assigned to this option, the list is reset and all prior assignments of this option will have no effect\&.
 .sp
 Note that this setting has no effect on processes configured via
 \fIExecStartPre=\fR,
@@ -1353,6 +1347,10 @@ Takes a list of exit status definitions that, when returned by the main service
 \fIRestart=\fR\&. The argument format is similar to
 \fIRestartPreventExitStatus=\fR\&.
 .sp
+Note that for
+\fIType=oneshot\fR
+services, a success exit status will prevent them from auto\-restarting, no matter whether the corresponding exit statuses are listed in this option or not\&.
+.sp
 Added in version 215\&.
 .RE
 .PP
@@ -1731,7 +1729,7 @@ T}
 T{
 ":"
 T}:T{
-If the executable path is prefixed with ":", environment variable substitution (as described by the "Command Lines" section below) is not applied\&.
+If the executable path is prefixed with ":", environment variable substitution (as described below this table) is not applied\&.
 T}
 T{
 "+"
@@ -1929,7 +1927,7 @@ with five arguments:
 "ls"\&.
 .SH "EXAMPLES"
 .PP
-\fBExample\ \&2.\ \&Simple service\fR
+\fBExample\ \&3.\ \&Simple service\fR
 .PP
 The following unit file creates a service that will execute
 /usr/sbin/foo\-daemon\&. Since no
@@ -1973,7 +1971,7 @@ if the service can background itself or
 \fIType=\fR\fBdbus\fR
 if the unit acquires a DBus name once initialization is complete\&. See below\&.
 .PP
-\fBExample\ \&3.\ \&Oneshot service\fR
+\fBExample\ \&4.\ \&Oneshot service\fR
 .PP
 Sometimes, units should just execute an action without keeping active processes, such as a filesystem check or a cleanup action on boot\&. For this,
 \fIType=\fR\fBoneshot\fR
@@ -2013,7 +2011,7 @@ are
 \fInot\fR
 allowed\&.
 .PP
-\fBExample\ \&4.\ \&Stoppable oneshot service\fR
+\fBExample\ \&5.\ \&Stoppable oneshot service\fR
 .PP
 Similarly to the oneshot services, there are sometimes units that need to execute a program to set up something and then execute another to shut it down, but no process remains active while they are considered "started"\&. Network configuration can sometimes fall into this category\&. Another use case is if a oneshot service shall not be executed each time when they are pulled in as a dependency, but only the first time\&.
 .PP
@@ -2049,7 +2047,7 @@ Since the unit is considered to be running after the start action has exited, in
 \fBsystemctl start\fR
 on that unit again will cause no action to be taken\&.
 .PP
-\fBExample\ \&5.\ \&Traditional forking services\fR
+\fBExample\ \&6.\ \&Traditional forking services\fR
 .PP
 Many traditional daemons/services background (i\&.e\&. fork, daemonize) themselves when starting\&. Set
 \fIType=\fR\fBforking\fR
@@ -2092,7 +2090,7 @@ Please see
 \fBsystemd.kill\fR(5)
 for details on how you can influence the way systemd terminates the service\&.
 .PP
-\fBExample\ \&6.\ \&DBus services\fR
+\fBExample\ \&7.\ \&DBus services\fR
 .PP
 For services that acquire a name on the DBus system bus, use
 \fIType=\fR\fBdbus\fR
@@ -2143,7 +2141,7 @@ Please see
 \fBsystemd.kill\fR(5)
 for details on how you can influence the way systemd terminates the service\&.
 .PP
-\fBExample\ \&7.\ \&Services that notify systemd about their initialization\fR
+\fBExample\ \&8.\ \&Services that notify systemd about their initialization\fR
 .PP
 \fIType=\fR\fBsimple\fR
 services are really easy to write, but have the major disadvantage of systemd not being able to tell when initialization of the given service is complete\&. For this reason, systemd supports a simple notification protocol that allows daemons to make systemd aware that they are done initializing\&. Use
@@ -2160,7 +2158,7 @@ for this\&. A typical service file for such a daemon would look like this:
 Description=Simple notifying service
 
 [Service]
-Type=notify
+Type=notify\-reload
 ExecStart=/usr/sbin/simple\-notifying\-service
 
 [Install]
@@ -2176,17 +2174,17 @@ Note that the daemon has to support systemd\*(Aqs notification protocol, else sy
 Please see
 \fBsystemd.kill\fR(5)
 for details on how you can influence the way systemd terminates the service\&.
+.PP
+To avoid code duplication, it is preferable to use
+\fBsd_notify\fR(3)
+when possible, especially when other APIs provided by
+\fBlibsystemd\fR(3)
+are also used, but note that the notification protocol is very simple and guaranteed to be stable as per the
+\m[blue]\fBInterface Portability and Stability Promise\fR\m[]\&\s-2\u[4]\d\s+2, so it can be reimplemented by services with no external dependencies\&. For a self\-contained example, see
+\fBsd_notify\fR(3)\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemctl\fR(1),
-\fBsystemd-system.conf\fR(5),
-\fBsystemd.unit\fR(5),
-\fBsystemd.exec\fR(5),
-\fBsystemd.resource-control\fR(5),
-\fBsystemd.kill\fR(5),
-\fBsystemd.directives\fR(7),
-\fBsystemd-run\fR(1)
+\fBsystemd\fR(1), \fBsystemctl\fR(1), \fBsystemd-system.conf\fR(5), \fBsystemd.unit\fR(5), \fBsystemd.exec\fR(5), \fBsystemd.resource-control\fR(5), \fBsystemd.kill\fR(5), \fBsystemd.directives\fR(7), \fBsystemd-run\fR(1)
 .SH "NOTES"
 .IP " 1." 4
 File Descriptor Store
@@ -2203,3 +2201,8 @@ Control Group v2
 .RS 4
 \%https://docs.kernel.org/admin-guide/cgroup-v2.html
 .RE
+.IP " 4." 4
+Interface Portability and Stability Promise
+.RS 4
+\%https://systemd.io/PORTABILITY_AND_STABILITY/
+.RE
diff --git a/upstream/fedora-rawhide/man5/systemd.slice.5 b/upstream/fedora-rawhide/man5/systemd.slice.5
index e4e179cc..98e7cc0b 100644
--- a/upstream/fedora-rawhide/man5/systemd.slice.5
+++ b/upstream/fedora-rawhide/man5/systemd.slice.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.SLICE" "5" "" "systemd 255" "systemd.slice"
+.TH "SYSTEMD\&.SLICE" "5" "" "systemd 256~rc3" "systemd.slice"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -102,16 +102,13 @@ option\&.
 .SH "OPTIONS"
 .PP
 Slice unit files may include [Unit] and [Install] sections, which are described in
-\fBsystemd.unit\fR(5)\&. No options specific to this file type are supported\&.
+\fBsystemd.unit\fR(5)\&.
+.PP
+Slice files may include a [Slice] section\&. Options that may be used in this section are shared with other unit types\&. These options are documented in
+\fBsystemd.resource-control\fR(5)\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd.unit\fR(5),
-\fBsystemd.resource-control\fR(5),
-\fBsystemd.service\fR(5),
-\fBsystemd.scope\fR(5),
-\fBsystemd.special\fR(7),
-\fBsystemd.directives\fR(7)
+\fBsystemd\fR(1), \fBsystemd.unit\fR(5), \fBsystemd.resource-control\fR(5), \fBsystemd.service\fR(5), \fBsystemd.scope\fR(5), \fBsystemd.special\fR(7), \fBsystemd.directives\fR(7)
 .SH "NOTES"
 .IP " 1." 4
 New Control Group Interfaces
diff --git a/upstream/fedora-rawhide/man5/systemd.socket.5 b/upstream/fedora-rawhide/man5/systemd.socket.5
index 1cd05d5c..3112c60a 100644
--- a/upstream/fedora-rawhide/man5/systemd.socket.5
+++ b/upstream/fedora-rawhide/man5/systemd.socket.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.SOCKET" "5" "" "systemd 255" "systemd.socket"
+.TH "SYSTEMD\&.SOCKET" "5" "" "systemd 256~rc3" "systemd.socket"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -191,9 +191,10 @@ Socket unit files may include [Unit] and [Install] sections, which are described
 \fBsystemd.unit\fR(5)\&.
 .PP
 Socket unit files must include a [Socket] section, which carries information about the socket or FIFO it supervises\&. A number of options that may be used in this section are shared with other unit types\&. These options are documented in
-\fBsystemd.exec\fR(5)
+\fBsystemd.exec\fR(5),
+\fBsystemd.kill\fR(5)
 and
-\fBsystemd.kill\fR(5)\&. The options specific to the [Socket] section of socket units are the following:
+\fBsystemd.resource-control\fR(5)\&. The options specific to the [Socket] section of socket units are the following:
 .PP
 \fIListenStream=\fR, \fIListenDatagram=\fR, \fIListenSequentialPacket=\fR
 .RS 4
@@ -243,6 +244,13 @@ address in the
 family\&. The CID is a unique 32\-bit integer identifier in
 \fBAF_VSOCK\fR
 analogous to an IP address\&. Specifying the CID is optional, and may be set to the empty string\&.
+"vsock"
+may be replaced with
+"vsock\-stream",
+"vsock\-dgram"
+or
+"vsock\-seqpacket"
+to force usage of the corresponding socket type\&.
 .sp
 Note that
 \fBSOCK_SEQPACKET\fR
@@ -453,9 +461,11 @@ or datagram sockets\&. Defaults to 64\&.
 .PP
 \fIMaxConnectionsPerSource=\fR
 .RS 4
-The maximum number of connections for a service per source IP address\&. This is very similar to the
+The maximum number of connections for a service per source IP address (in case of IPv4/IPv6), per source CID (in case of
+\fBAF_VSOCK\fR), or source UID (in case of
+\fBAF_UNIX\fR)\&. This is very similar to the
 \fIMaxConnections=\fR
-directive above\&. Disabled by default\&.
+directive above\&. Defaults to 0, i\&.e\&. disabled\&.
 .sp
 Added in version 232\&.
 .RE
@@ -727,7 +737,7 @@ Added in version 247\&.
 .RS 4
 Takes a string value\&. Controls the TCP congestion algorithm used by this socket\&. Should be one of
 "westwood",
-"veno",
+"reno",
 "cubic",
 "lp"
 or any other available algorithm supported by the IP stack\&. This setting applies only to stream sockets\&.
@@ -853,6 +863,21 @@ These setting defaults to 150 (in case of
 Added in version 255\&.
 .RE
 .PP
+\fIPassFileDescriptorsToExec=\fR
+.RS 4
+Takes a boolean argument\&. Defaults to off\&. If enabled, file descriptors created by the socket unit are passed to
+\fIExecStartPost=\fR,
+\fIExecStopPre=\fR, and
+\fIExecStopPost=\fR
+commands from the socket unit\&. The passed file descriptors can be accessed with
+\fBsd_listen_fds\fR(3)
+as if the commands were invoked from the associated service units\&. Note that
+\fIExecStartPre=\fR
+command cannot access socket file descriptors\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 Check
 \fBsystemd.unit\fR(5),
 \fBsystemd.exec\fR(5), and
@@ -860,23 +885,10 @@ Check
 for more settings\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemctl\fR(1),
-\fBsystemd-system.conf\fR(5),
-\fBsystemd.unit\fR(5),
-\fBsystemd.exec\fR(5),
-\fBsystemd.kill\fR(5),
-\fBsystemd.resource-control\fR(5),
-\fBsystemd.service\fR(5),
-\fBsystemd.directives\fR(7),
-\fBsd_listen_fds\fR(3),
-\fBsd_listen_fds_with_names\fR(3)
+\fBsystemd\fR(1), \fBsystemctl\fR(1), \fBsystemd-system.conf\fR(5), \fBsystemd.unit\fR(5), \fBsystemd.exec\fR(5), \fBsystemd.kill\fR(5), \fBsystemd.resource-control\fR(5), \fBsystemd.service\fR(5), \fBsystemd.directives\fR(7), \fBsd_listen_fds\fR(3), \fBsd_listen_fds_with_names\fR(3)
 .PP
 For more extensive descriptions see the "systemd for Developers" series:
-\m[blue]\fBSocket Activation\fR\m[]\&\s-2\u[4]\d\s+2,
-\m[blue]\fBSocket Activation, part II\fR\m[]\&\s-2\u[5]\d\s+2,
-\m[blue]\fBConverting inetd Services\fR\m[]\&\s-2\u[6]\d\s+2,
-\m[blue]\fBSocket Activated Internet Services and OS Containers\fR\m[]\&\s-2\u[7]\d\s+2\&.
+\m[blue]\fBSocket Activation\fR\m[]\&\s-2\u[4]\d\s+2, \m[blue]\fBSocket Activation, part II\fR\m[]\&\s-2\u[5]\d\s+2, \m[blue]\fBConverting inetd Services\fR\m[]\&\s-2\u[6]\d\s+2, \m[blue]\fBSocket Activated Internet Services and OS Containers\fR\m[]\&\s-2\u[7]\d\s+2\&.
 .SH "NOTES"
 .IP " 1." 4
 USB FunctionFS
diff --git a/upstream/fedora-rawhide/man5/systemd.swap.5 b/upstream/fedora-rawhide/man5/systemd.swap.5
index 1cb7edb2..3adcd21b 100644
--- a/upstream/fedora-rawhide/man5/systemd.swap.5
+++ b/upstream/fedora-rawhide/man5/systemd.swap.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.SWAP" "5" "" "systemd 255" "systemd.swap"
+.TH "SYSTEMD\&.SWAP" "5" "" "systemd 256~rc3" "systemd.swap"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -176,13 +176,14 @@ Swap unit files may include [Unit] and [Install] sections, which are described i
 \fBsystemd.unit\fR(5)\&.
 .PP
 Swap unit files must include a [Swap] section, which carries information about the swap device it supervises\&. A number of options that may be used in this section are shared with other unit types\&. These options are documented in
-\fBsystemd.exec\fR(5)
+\fBsystemd.exec\fR(5),
+\fBsystemd.kill\fR(5)
 and
-\fBsystemd.kill\fR(5)\&. The options specific to the [Swap] section of swap units are the following:
+\fBsystemd.resource-control\fR(5)\&. The options specific to the [Swap] section of swap units are the following:
 .PP
 \fIWhat=\fR
 .RS 4
-Takes an absolute path of a device node or file to use for paging\&. See
+Takes an absolute path or a fstab\-style identifier of a device node or file to use for paging\&. See
 \fBswapon\fR(8)
 for details\&. If this refers to a device node, a dependency on the respective device unit is automatically created\&. (See
 \fBsystemd.device\fR(5)
@@ -233,15 +234,4 @@ Check
 for more settings\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemctl\fR(1),
-\fBsystemd-system.conf\fR(5),
-\fBsystemd.unit\fR(5),
-\fBsystemd.exec\fR(5),
-\fBsystemd.kill\fR(5),
-\fBsystemd.resource-control\fR(5),
-\fBsystemd.device\fR(5),
-\fBsystemd.mount\fR(5),
-\fBswapon\fR(8),
-\fBsystemd-fstab-generator\fR(8),
-\fBsystemd.directives\fR(7)
+\fBsystemd\fR(1), \fBsystemctl\fR(1), \fBsystemd-system.conf\fR(5), \fBsystemd.unit\fR(5), \fBsystemd.exec\fR(5), \fBsystemd.kill\fR(5), \fBsystemd.resource-control\fR(5), \fBsystemd.device\fR(5), \fBsystemd.mount\fR(5), \fBswapon\fR(8), \fBsystemd-fstab-generator\fR(8), \fBsystemd.directives\fR(7)
diff --git a/upstream/fedora-rawhide/man5/systemd.target.5 b/upstream/fedora-rawhide/man5/systemd.target.5
index ba0aa547..8d5cb678 100644
--- a/upstream/fedora-rawhide/man5/systemd.target.5
+++ b/upstream/fedora-rawhide/man5/systemd.target.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.TARGET" "5" "" "systemd 255" "systemd.target"
+.TH "SYSTEMD\&.TARGET" "5" "" "systemd 256~rc3" "systemd.target"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -170,8 +170,4 @@ without modifying them by using
 \fBsystemctl add\-wants\fR\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemctl\fR(1),
-\fBsystemd.unit\fR(5),
-\fBsystemd.special\fR(7),
-\fBsystemd.directives\fR(7)
+\fBsystemd\fR(1), \fBsystemctl\fR(1), \fBsystemd.unit\fR(5), \fBsystemd.special\fR(7), \fBsystemd.directives\fR(7)
diff --git a/upstream/fedora-rawhide/man5/systemd.timer.5 b/upstream/fedora-rawhide/man5/systemd.timer.5
index de75ccde..1f5a8fce 100644
--- a/upstream/fedora-rawhide/man5/systemd.timer.5
+++ b/upstream/fedora-rawhide/man5/systemd.timer.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.TIMER" "5" "" "systemd 255" "systemd.timer"
+.TH "SYSTEMD\&.TIMER" "5" "" "systemd 256~rc3" "systemd.timer"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -378,11 +378,4 @@ section in
 \fBsystemd.exec\fR(5)
 for more details\&.
 .PP
-\fBsystemd\fR(1),
-\fBsystemctl\fR(1),
-\fBsystemd.unit\fR(5),
-\fBsystemd.service\fR(5),
-\fBsystemd.time\fR(7),
-\fBsystemd.directives\fR(7),
-\fBsystemd-system.conf\fR(5),
-\fBprctl\fR(2)
+\fBsystemd\fR(1), \fBsystemctl\fR(1), \fBsystemd.unit\fR(5), \fBsystemd.service\fR(5), \fBsystemd.time\fR(7), \fBsystemd.directives\fR(7), \fBsystemd-system.conf\fR(5), \fBprctl\fR(2)
diff --git a/upstream/fedora-rawhide/man5/systemd.unit.5 b/upstream/fedora-rawhide/man5/systemd.unit.5
index 9c3e27c6..7e3e6fae 100644
--- a/upstream/fedora-rawhide/man5/systemd.unit.5
+++ b/upstream/fedora-rawhide/man5/systemd.unit.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.UNIT" "5" "" "systemd 255" "systemd.unit"
+.TH "SYSTEMD\&.UNIT" "5" "" "systemd 256~rc3" "systemd.unit"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,52 +23,92 @@
 systemd.unit \- Unit configuration
 .SH "SYNOPSIS"
 .PP
-\fIservice\fR\&.service,
-\fIsocket\fR\&.socket,
-\fIdevice\fR\&.device,
-\fImount\fR\&.mount,
-\fIautomount\fR\&.automount,
-\fIswap\fR\&.swap,
-\fItarget\fR\&.target,
-\fIpath\fR\&.path,
-\fItimer\fR\&.timer,
-\fIslice\fR\&.slice,
-\fIscope\fR\&.scope
+\fIservice\fR\&.service, \fIsocket\fR\&.socket, \fIdevice\fR\&.device, \fImount\fR\&.mount, \fIautomount\fR\&.automount, \fIswap\fR\&.swap, \fItarget\fR\&.target, \fIpath\fR\&.path, \fItimer\fR\&.timer, \fIslice\fR\&.slice, \fIscope\fR\&.scope
 .SS "System Unit Search Path"
 .PP
-.nf
+.RS 4
 /etc/systemd/system\&.control/*
+.RE
+.RS 4
 /run/systemd/system\&.control/*
+.RE
+.RS 4
 /run/systemd/transient/*
+.RE
+.RS 4
 /run/systemd/generator\&.early/*
+.RE
+.RS 4
 /etc/systemd/system/*
+.RE
+.RS 4
 /etc/systemd/system\&.attached/*
+.RE
+.RS 4
 /run/systemd/system/*
+.RE
+.RS 4
 /run/systemd/system\&.attached/*
+.RE
+.RS 4
 /run/systemd/generator/*
+.RE
+.RS 4
 \&...
+.RE
+.RS 4
 /usr/lib/systemd/system/*
+.RE
+.RS 4
 /run/systemd/generator\&.late/*
-.fi
+.RE
 .SS "User Unit Search Path"
 .PP
-.nf
+.RS 4
 ~/\&.config/systemd/user\&.control/*
+.RE
+.RS 4
 $XDG_RUNTIME_DIR/systemd/user\&.control/*
+.RE
+.RS 4
 $XDG_RUNTIME_DIR/systemd/transient/*
+.RE
+.RS 4
 $XDG_RUNTIME_DIR/systemd/generator\&.early/*
+.RE
+.RS 4
 ~/\&.config/systemd/user/*
+.RE
+.RS 4
 $XDG_CONFIG_DIRS/systemd/user/*
+.RE
+.RS 4
 /etc/systemd/user/*
+.RE
+.RS 4
 $XDG_RUNTIME_DIR/systemd/user/*
+.RE
+.RS 4
 /run/systemd/user/*
+.RE
+.RS 4
 $XDG_RUNTIME_DIR/systemd/generator/*
+.RE
+.RS 4
 $XDG_DATA_HOME/systemd/user/*
+.RE
+.RS 4
 $XDG_DATA_DIRS/systemd/user/*
+.RE
+.RS 4
 \&...
+.RE
+.RS 4
 /usr/lib/systemd/user/*
+.RE
+.RS 4
 $XDG_RUNTIME_DIR/systemd/generator\&.late/*
-.fi
+.RE
 .SH "DESCRIPTION"
 .PP
 A unit file is a plain text ini\-style file that encodes information about a service, a socket, a device, a mount point, an automount point, a swap file or partition, a start\-up target, a watched file system path, a timer controlled and supervised by
@@ -152,7 +192,7 @@ Aliases obey the following restrictions: a unit of a certain type ("\&.service",
 "alias@inst\&.service") may be a symlink to different template (e\&.g\&.
 "template@inst\&.service")\&. In that case, just this specific instance is aliased, while other instances of the template (e\&.g\&.
 "alias@foo\&.service",
-"alias@bar\&.service") are not aliased\&. Those rules preserve the requirement that the instance (if any) is always uniquely defined for a given unit and all its aliases\&. The target of alias symlink must point to a valid unit file location, i\&.e\&. the symlink target name must match the symlink source name as described, and the destination path must be in one of the unit search paths, see UNIT FILE LOAD PATH section below for more details\&. Note that the target file may not exist, i\&.e\&. the symlink may be dangling\&.
+"alias@bar\&.service") are not aliased\&. Those rules preserve the requirement that the instance (if any) is always uniquely defined for a given unit and all its aliases\&. The target of alias symlink must point to a valid unit file location, i\&.e\&. the symlink target name must match the symlink source name as described, and the destination path must be in one of the unit search paths, see UNIT FILE LOAD PATH section below for more details\&. Note that the target file might not exist, i\&.e\&. the symlink may be dangling\&.
 .PP
 Unit files may specify aliases through the
 \fIAlias=\fR
@@ -199,7 +239,7 @@ commands of
 \&.wants/
 or
 \&.requires/
-must thus point to a valid unit file location, i\&.e\&. the symlink target name must satisfy the described requirements, and the destination path must be in one of the unit search paths, see UNIT FILE LOAD PATH section below for more details\&. Note that the target file may not exist, i\&.e\&. the symlink may be dangling\&.
+must thus point to a valid unit file location, i\&.e\&. the symlink target name must satisfy the described requirements, and the destination path must be in one of the unit search paths, see UNIT FILE LOAD PATH section below for more details\&. Note that the target file might not exist, i\&.e\&. the symlink may be dangling\&.
 .PP
 Along with a unit file
 foo\&.service, a "drop\-in" directory
@@ -1057,6 +1097,17 @@ local\-fs\&.target, but are still honored for the purposes of this option, i\&.e
 Added in version 201\&.
 .RE
 .PP
+\fIWantsMountsFor=\fR
+.RS 4
+Same as
+\fIRequiresMountsFor=\fR, but adds dependencies of type
+\fIWants=\fR
+instead of
+\fIRequires=\fR\&.
+.sp
+Added in version 256\&.
+.RE
+.PP
 \fIOnSuccessJobMode=\fR, \fIOnFailureJobMode=\fR
 .RS 4
 Takes a value of
@@ -1196,11 +1247,8 @@ Configure the action to take when the unit stops and enters a failed state or in
 and
 \fBhalt\-immediate\fR\&. In system mode, all options are allowed\&. In user mode, only
 \fBnone\fR,
-\fBexit\fR,
-\fBexit\-force\fR,
-\fBsoft\-reboot\fR
-and
-\fBsoft\-reboot\-force\fR
+\fBexit\fR, and
+\fBexit\-force\fR
 are allowed\&. Both options default to
 \fBnone\fR\&.
 .sp
@@ -1290,7 +1338,7 @@ optionally configures an additional action to take when the timeout is hit, see
 and
 \fIJobRunningTimeoutSec=\fR
 above\&. It takes the same values as
-\fIStartLimitAction=\fR\&. Defaults to
+\fIFailureAction=\fR/\fISuccessAction=\fR\&. Defaults to
 \fBnone\fR\&.
 .sp
 \fIJobTimeoutRebootArgument=\fR
@@ -1446,6 +1494,10 @@ Check whether the system is running on a specific architecture\&. Takes one of
 "arc\-be", or
 "native"\&.
 .sp
+Use
+\fBsystemd-analyze\fR(1)
+for the complete list of known architectures\&.
+.sp
 The architecture is determined from the information returned by
 \fBuname\fR(2)
 and is thus subject to
@@ -1780,7 +1832,7 @@ on the next following boot\&. Units making use of this condition should order th
 \fBsystemd-update-done.service\fR(8), to make sure they run before the stamp file\*(Aqs modification time gets reset indicating a completed update\&.
 .sp
 If the
-\fIsystemd\&.condition\-needs\-update=\fR
+\fIsystemd\&.condition_needs_update=\fR
 option is specified on the kernel command line (taking a boolean), it will override the result of this condition check, taking precedence over any file modification time checks\&. If the kernel command line option is used,
 systemd\-update\-done\&.service
 will not have immediate effect on any following
@@ -1806,12 +1858,19 @@ Added in version 244\&.
 Takes a boolean argument\&. This condition may be used to conditionalize units on whether the system is booting up for the first time\&. This roughly means that
 /etc/
 was unpopulated when the system started booting (for details, see "First Boot Semantics" in
-\fBmachine-id\fR(5))\&. First boot is considered finished (this condition will evaluate as false) after the manager has finished the startup phase\&.
+\fBmachine-id\fR(5))\&. First Boot is considered finished (this condition will evaluate as false) after the manager has finished the startup phase\&.
 .sp
 This condition may be used to populate
 /etc/
 on the first boot after factory reset, or when a new system instance boots up for the first time\&.
 .sp
+Note that the service manager itself will perform setup steps during First Boot: it will initialize
+\fBmachine-id\fR(5)
+and preset all units, enabling or disabling them according to the
+\fBsystemd.preset\fR(5)
+settings\&. Additional setup may be performed via units with
+\fIConditionFirstBoot=yes\fR\&.
+.sp
 For robustness, units with
 \fIConditionFirstBoot=yes\fR
 should order themselves before
@@ -1820,7 +1879,7 @@ and pull in this passive target with
 \fIWants=\fR\&. This ensures that in a case of an aborted first boot, these units will be re\-run during the next system startup\&.
 .sp
 If the
-\fIsystemd\&.condition\-first\-boot=\fR
+\fIsystemd\&.condition_first_boot=\fR
 option is specified on the kernel command line (taking a boolean), it will override the result of this condition check, taking precedence over
 /etc/machine\-id
 existence checks\&.
@@ -2470,6 +2529,7 @@ l l l
 l l l
 l l l
 l l l
+l l l
 l l l.
 T{
 "%a"
@@ -2514,6 +2574,13 @@ T}:T{
 This is the value of the "$CREDENTIALS_DIRECTORY" environment variable if available\&. See section "Credentials" in \fBsystemd.exec\fR(5) for more information\&.
 T}
 T{
+"%D"
+T}:T{
+Shared data directory
+T}:T{
+This is either /usr/share/ (for the system manager) or the path "$XDG_DATA_HOME" resolves to (for user managers)\&.
+T}
+T{
 "%E"
 T}:T{
 Configuration directory root
@@ -2972,26 +3039,7 @@ instance fails it will not trigger an instance named
 failure\-handler@failure\-handler\&.service\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemctl\fR(1),
-\fBsystemd-system.conf\fR(5),
-\fBsystemd.special\fR(7),
-\fBsystemd.service\fR(5),
-\fBsystemd.socket\fR(5),
-\fBsystemd.device\fR(5),
-\fBsystemd.mount\fR(5),
-\fBsystemd.automount\fR(5),
-\fBsystemd.swap\fR(5),
-\fBsystemd.target\fR(5),
-\fBsystemd.path\fR(5),
-\fBsystemd.timer\fR(5),
-\fBsystemd.scope\fR(5),
-\fBsystemd.slice\fR(5),
-\fBsystemd.time\fR(7),
-\fBsystemd-analyze\fR(1),
-\fBcapabilities\fR(7),
-\fBsystemd.directives\fR(7),
-\fBuname\fR(1)
+\fBsystemd\fR(1), \fBsystemctl\fR(1), \fBsystemd-system.conf\fR(5), \fBsystemd.special\fR(7), \fBsystemd.service\fR(5), \fBsystemd.socket\fR(5), \fBsystemd.device\fR(5), \fBsystemd.mount\fR(5), \fBsystemd.automount\fR(5), \fBsystemd.swap\fR(5), \fBsystemd.target\fR(5), \fBsystemd.path\fR(5), \fBsystemd.timer\fR(5), \fBsystemd.scope\fR(5), \fBsystemd.slice\fR(5), \fBsystemd.time\fR(7), \fBsystemd-analyze\fR(1), \fBcapabilities\fR(7), \fBsystemd.directives\fR(7), \fBuname\fR(1)
 .SH "NOTES"
 .IP " 1." 4
 Interface Portability and Stability Promise
diff --git a/upstream/fedora-rawhide/man5/sysupdate.d.5 b/upstream/fedora-rawhide/man5/sysupdate.d.5
index 456bdb01..fbf4facb 100644
--- a/upstream/fedora-rawhide/man5/sysupdate.d.5
+++ b/upstream/fedora-rawhide/man5/sysupdate.d.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSUPDATE\&.D" "5" "" "systemd 255" "sysupdate.d"
+.TH "SYSUPDATE\&.D" "5" "" "systemd 256~rc3" "sysupdate.d"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,12 +23,15 @@
 sysupdate.d \- Transfer Definition Files for Automatic Updates
 .SH "SYNOPSIS"
 .PP
-.nf
+.RS 4
 /etc/sysupdate\&.d/*\&.conf
+.RE
+.RS 4
 /run/sysupdate\&.d/*\&.conf
+.RE
+.RS 4
 /usr/lib/sysupdate\&.d/*\&.conf
-    
-.fi
+.RE
 .SH "DESCRIPTION"
 .PP
 sysupdate\&.d/*\&.conf
@@ -1319,9 +1322,7 @@ and decompresses/unpacks it to
 is created/updated always pointing to the most recent update\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-sysupdate\fR(8),
-\fBsystemd-repart\fR(8)
+\fBsystemd\fR(1), \fBsystemd-sysupdate\fR(8), \fBsystemd-repart\fR(8)
 .SH "NOTES"
 .IP " 1." 4
 Discoverable Partitions Specification
diff --git a/upstream/fedora-rawhide/man5/sysusers.d.5 b/upstream/fedora-rawhide/man5/sysusers.d.5
index a44d461f..22c19b4b 100644
--- a/upstream/fedora-rawhide/man5/sysusers.d.5
+++ b/upstream/fedora-rawhide/man5/sysusers.d.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSUSERS\&.D" "5" "" "systemd 255" "sysusers.d"
+.TH "SYSUSERS\&.D" "5" "" "systemd 256~rc3" "sysusers.d"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,11 +23,15 @@
 sysusers.d \- Declarative allocation of system users and groups
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/sysusers\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /run/sysusers\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /usr/lib/sysusers\&.d/*\&.conf
+.RE
 .sp
 .nf
 #Type Name       ID                  GECOS              Home directory Shell
@@ -367,8 +371,7 @@ sysusers\&.d
 vendor configuration, except to block certain users or groups from being created\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-sysusers\fR(8)
+\fBsystemd\fR(1), \fBsystemd-sysusers\fR(8)
 .SH "NOTES"
 .IP " 1." 4
 User/Group Name Syntax
diff --git a/upstream/fedora-rawhide/man5/termcap.5 b/upstream/fedora-rawhide/man5/termcap.5
index a2fc7839..8aefa689 100644
--- a/upstream/fedora-rawhide/man5/termcap.5
+++ b/upstream/fedora-rawhide/man5/termcap.5
@@ -9,7 +9,7 @@
 .\"   If mistakes in the capabilities are found, please send a bug report to:
 .\"   michael@moria.de
 .\" Modified Mon Oct 21 17:47:19 EDT 1996 by Eric S. Raymond (esr@thyrsus.com)
-.TH termcap 5 2023-10-31 "Linux man-pages 6.06"
+.TH termcap 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 termcap \- terminal capability database
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/timesyncd.conf.5 b/upstream/fedora-rawhide/man5/timesyncd.conf.5
index 33f0675d..663f10bd 100644
--- a/upstream/fedora-rawhide/man5/timesyncd.conf.5
+++ b/upstream/fedora-rawhide/man5/timesyncd.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "TIMESYNCD\&.CONF" "5" "" "systemd 255" "timesyncd.conf"
+.TH "TIMESYNCD\&.CONF" "5" "" "systemd 256~rc3" "timesyncd.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -23,13 +23,24 @@
 timesyncd.conf, timesyncd.conf.d \- Network Time Synchronization configuration files
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/systemd/timesyncd\&.conf
-.PP
+.RE
+.RS 4
+/run/systemd/timesyncd\&.conf
+.RE
+.RS 4
+/usr/lib/systemd/timesyncd\&.conf
+.RE
+.RS 4
 /etc/systemd/timesyncd\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /run/systemd/timesyncd\&.conf\&.d/*\&.conf
-.PP
+.RE
+.RS 4
 /usr/lib/systemd/timesyncd\&.conf\&.d/*\&.conf
+.RE
 .SH "DESCRIPTION"
 .PP
 These configuration files control NTP network time synchronization\&. See
@@ -37,16 +48,16 @@ These configuration files control NTP network time synchronization\&. See
 for a general description of the syntax\&.
 .SH "CONFIGURATION DIRECTORIES AND PRECEDENCE"
 .PP
-The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is either in
-/usr/lib/systemd/
-or
-/etc/systemd/
-and contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
+The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is loaded from one of the listed directories in order of priority, only the first file found is used:
+/etc/systemd/,
+/run/systemd/,
+/usr/local/lib/systemd/,
+/usr/lib/systemd/\&. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can also be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
 /etc/
-if it\*(Aqs shipped in
-/usr/) however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
+if it\*(Aqs shipped under
+/usr/), however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
 .PP
-In addition to the "main" configuration file, drop\-in configuration snippets are read from
+In addition to the main configuration file, drop\-in configuration snippets are read from
 /usr/lib/systemd/*\&.conf\&.d/,
 /usr/local/lib/systemd/*\&.conf\&.d/, and
 /etc/systemd/*\&.conf\&.d/\&. Those drop\-ins have higher precedence and override the main configuration file\&. Files in the
@@ -56,7 +67,12 @@ configuration subdirectories are sorted by their filename in lexicographic order
 When packages need to customize the configuration, they can install drop\-ins under
 /usr/\&. Files in
 /etc/
-are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defined a concept of drop\-in priority to allow distributions to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&.
+are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering of the files\&. This also defines a concept of drop\-in priorities to allow OS vendors to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&. It is recommended to use the range 10\-40 for drop\-ins in
+/usr/
+and the range 60\-90 for drop\-ins in
+/etc/
+and
+/run/, to make sure that local and transient drop\-ins take priority over drop\-ins shipped by the OS vendor\&.
 .PP
 To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
 /dev/null
@@ -135,6 +151,4 @@ Added in version 250\&.
 .RE
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-timesyncd.service\fR(8),
-\fBsystemd-networkd.service\fR(8)
+\fBsystemd\fR(1), \fBsystemd-timesyncd.service\fR(8), \fBsystemd-networkd.service\fR(8)
diff --git a/upstream/fedora-rawhide/man5/tmpfiles.d.5 b/upstream/fedora-rawhide/man5/tmpfiles.d.5
index 9c32f27f..f84439b7 100644
--- a/upstream/fedora-rawhide/man5/tmpfiles.d.5
+++ b/upstream/fedora-rawhide/man5/tmpfiles.d.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "TMPFILES\&.D" "5" "" "systemd 255" "tmpfiles.d"
+.TH "TMPFILES\&.D" "5" "" "systemd 256~rc3" "tmpfiles.d"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -20,25 +20,34 @@
 .\" * MAIN CONTENT STARTS HERE *
 .\" -----------------------------------------------------------------
 .SH "NAME"
-tmpfiles.d \- Configuration for creation, deletion and cleaning of volatile and temporary files
+tmpfiles.d \- Configuration for creation, deletion, and cleaning of files and directories
 .SH "SYNOPSIS"
 .PP
-.nf
+.RS 4
 /etc/tmpfiles\&.d/*\&.conf
+.RE
+.RS 4
 /run/tmpfiles\&.d/*\&.conf
+.RE
+.RS 4
 /usr/lib/tmpfiles\&.d/*\&.conf
-    
-.fi
+.RE
 .PP
-.nf
+.RS 4
 ~/\&.config/user\-tmpfiles\&.d/*\&.conf
+.RE
+.RS 4
 $XDG_RUNTIME_DIR/user\-tmpfiles\&.d/*\&.conf
+.RE
+.RS 4
 ~/\&.local/share/user\-tmpfiles\&.d/*\&.conf
+.RE
+.RS 4
 \&...
+.RE
+.RS 4
 /usr/share/user\-tmpfiles\&.d/*\&.conf
-    
-.fi
-
+.RE
 .sp
 .nf
 #Type Path                                     Mode User Group Age         Argument
@@ -326,21 +335,13 @@ Added in version 214\&.
 .PP
 \fIx\fR
 .RS 4
-Ignore a path during cleaning\&. Use this type to exclude paths from clean\-up as controlled with the Age parameter\&. Note that lines of this type do not influence the effect of
-\fIr\fR
-or
-\fIR\fR
-lines\&. Lines of this type accept shell\-style globs in place of normal path names\&.
+Ignore a path during cleaning\&. Use this type to exclude paths from clean\-up as controlled with the Age parameter\&. Lines of this type accept shell\-style globs in place of normal path names\&.
 .RE
 .PP
 \fIX\fR
 .RS 4
 Ignore a path during cleaning\&. Use this type to exclude paths from clean\-up as controlled with the Age parameter\&. Unlike
-\fIx\fR, this parameter will not exclude the content if path is a directory, but only directory itself\&. Note that lines of this type do not influence the effect of
-\fIr\fR
-or
-\fIR\fR
-lines\&. Lines of this type accept shell\-style globs in place of normal path names\&.
+\fIx\fR, this parameter will not exclude the content if path is a directory, but only directory itself\&. Lines of this type accept shell\-style globs in place of normal path names\&.
 .sp
 Added in version 198\&.
 .RE
@@ -513,7 +514,7 @@ and
 are combined Base64 decoding is applied to the credential contents\&.
 .PP
 Note that for all line types that result in creation of any kind of file node (i\&.e\&.
-\fIf\fR/\fIF\fR,
+\fIf\fR,
 \fId\fR/\fID\fR/\fIv\fR/\fIq\fR/\fIQ\fR,
 \fIp\fR,
 \fIL\fR,
@@ -661,8 +662,8 @@ and
 \fIb\fR, determines the major/minor of the device node, with major and minor formatted as integers, separated by
 ":", e\&.g\&.
 "1:3"\&. For
-\fIf\fR,
-\fIF\fR, and
+\fIf\fR
+and
 \fIw\fR, the argument may be used to specify a short string that is written to the file, suffixed by a newline\&. For
 \fIC\fR, specifies the source file or directory\&. For
 \fIt\fR
@@ -1000,7 +1001,7 @@ will be removed on boot\&. The directory will not be created\&.
 .RS 4
 .\}
 .nf
-\-smbios type=11,value=io\&.systemd\&.credential\&.binary:tmpfiles\&.extra=$(echo "f~ /root/\&.ssh/authorized_keys 700 root root \- $(ssh\-add \-L | base64 \-w 0)" | base64 \-w 0)
+\-smbios type=11,value=io\&.systemd\&.credential\&.binary:tmpfiles\&.extra=$(echo \-e "d /root/\&.ssh 0750 root root \-\enf~ /root/\&.ssh/authorized_keys 0600 root root \- $(ssh\-add \-L | base64 \-w 0)" | base64 \-w 0)
 .fi
 .if n \{\
 .RE
@@ -1021,18 +1022,7 @@ will warn if
 is used\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-tmpfiles\fR(8),
-\fBsystemd-delta\fR(1),
-\fBsystemd.exec\fR(5),
-\fBattr\fR(5),
-\fBgetfattr\fR(1),
-\fBsetfattr\fR(1),
-\fBsetfacl\fR(1),
-\fBgetfacl\fR(1),
-\fBchattr\fR(1),
-\fBbtrfs-subvolume\fR(8),
-\fBbtrfs-qgroup\fR(8)
+\fBsystemd\fR(1), \fBsystemd-tmpfiles\fR(8), \fBsystemd-delta\fR(1), \fBsystemd.exec\fR(5), \fBattr\fR(5), \fBgetfattr\fR(1), \fBsetfattr\fR(1), \fBsetfacl\fR(1), \fBgetfacl\fR(1), \fBchattr\fR(1), \fBbtrfs-subvolume\fR(8), \fBbtrfs-qgroup\fR(8)
 .SH "NOTES"
 .IP " 1." 4
 Base64 decoded
diff --git a/upstream/fedora-rawhide/man5/tmpfs.5 b/upstream/fedora-rawhide/man5/tmpfs.5
index b7c5f407..55fc8265 100644
--- a/upstream/fedora-rawhide/man5/tmpfs.5
+++ b/upstream/fedora-rawhide/man5/tmpfs.5
@@ -2,7 +2,7 @@
 .\"
 .\" SPDX-License-Identifier: Linux-man-pages-copyleft
 .\"
-.TH tmpfs 5 2023-10-31 "Linux man-pages 6.06"
+.TH tmpfs 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 tmpfs \- a virtual memory filesystem
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/ttytype.5 b/upstream/fedora-rawhide/man5/ttytype.5
index 3e9a5a3d..ebe0866a 100644
--- a/upstream/fedora-rawhide/man5/ttytype.5
+++ b/upstream/fedora-rawhide/man5/ttytype.5
@@ -7,7 +7,7 @@
 .\" Modified Thu Oct 19 21:25:21 MET 1995 by Martin Schulze <joey@infodrom.north.de>
 .\" Modified Mon Oct 21 17:47:19 EDT 1996 by Eric S. Raymond
 .\" <esr@thyrsus.com>xk
-.TH ttytype 5 2023-10-31 "Linux man-pages 6.06"
+.TH ttytype 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 ttytype \- terminal device to default terminal type mapping
 .SH DESCRIPTION
diff --git a/upstream/fedora-rawhide/man5/tzfile.5 b/upstream/fedora-rawhide/man5/tzfile.5
index 45afecc1..4aa3f6c2 100644
--- a/upstream/fedora-rawhide/man5/tzfile.5
+++ b/upstream/fedora-rawhide/man5/tzfile.5
@@ -26,23 +26,24 @@ a signed binary integer is represented using two's complement,
 and a boolean is represented by a one-byte binary integer that is
 either 0 (false) or 1 (true).
 The format begins with a 44-byte header containing the following fields:
-.IP * 2
+.RS 2
+.IP \(bu 3
 The magic four-byte ASCII sequence
 .q "TZif"
 identifies the file as a timezone information file.
-.IP *
+.IP \(bu
 A byte identifying the version of the file's format
 (as of 2021, either an ASCII NUL,
 .q "2",
 .q "3",
 or
 .q "4" ).
-.IP *
+.IP \(bu
 Fifteen bytes containing zeros reserved for future use.
-.IP *
+.IP \(bu
 Six four-byte integer values, in the following order:
 .RS
-.TP
+.TP 2
 .B tzh_ttisutcnt
 The number of UT/local indicators stored in the file.
 (UT is Universal Time.)
@@ -65,17 +66,19 @@ in the file (must not be zero).
 The number of bytes of time zone abbreviation strings
 stored in the file.
 .RE
-.P
+.RE
+.PP
 The above header is followed by the following fields, whose lengths
 depend on the contents of the header:
-.IP * 2
+.RS 2
+.IP \(bu 3
 .B tzh_timecnt
 four-byte signed integer values sorted in ascending order.
 These values are written in network byte order.
 Each is used as a transition time (as returned by
 .BR time (2))
 at which the rules for computing local time change.
-.IP *
+.IP \(bu
 .B tzh_timecnt
 one-byte unsigned integer values;
 each one but the last tells which of the different types of local time types
@@ -83,22 +86,22 @@ described in the file is associated with the time period
 starting with the same-indexed transition time
 and continuing up to but not including the next transition time.
 (The last time type is present only for consistency checking with the
-POSIX-style TZ string described below.)
+POSIX.1-2017-style TZ string described below.)
 These values serve as indices into the next field.
-.IP *
+.IP \(bu
 .B tzh_typecnt
 .B ttinfo
 entries, each defined as follows:
-.in +.5i
+.in +2
 .sp
 .nf
-.ta .5i +\w'unsigned char\0\0'u
+.ta \w'\0\0\0\0'u +\w'unsigned char\0'u
 struct ttinfo {
 	int32_t	tt_utoff;
 	unsigned char	tt_isdst;
 	unsigned char	tt_desigidx;
 };
-.in -.5i
+.in
 .fi
 .sp
 Each structure is written as a four-byte signed integer value for
@@ -132,7 +135,7 @@ Also, in realistic applications
 is in the range [\-89999, 93599] (i.e., more than \-25 hours and less
 than 26 hours); this allows easy support by implementations that
 already support the POSIX-required range [\-24:59:59, 25:59:59].
-.IP *
+.IP \(bu
 .B tzh_charcnt
 bytes that represent time zone designations,
 which are null-terminated byte strings, each indexed by the
@@ -140,7 +143,7 @@ which are null-terminated byte strings, each indexed by the
 values mentioned above.
 The byte strings can overlap if one is a suffix of the other.
 The encoding of these strings is not specified.
-.IP *
+.IP \(bu
 .B tzh_leapcnt
 pairs of four-byte values, written in network byte order;
 the first value of each pair gives the nonnegative time
@@ -167,22 +170,24 @@ otherwise, for timestamps before the first occurrence time,
 the leap-second correction is zero if the first pair's correction is 1 or \-1,
 and is unspecified otherwise (which can happen only in files
 truncated at the start).
-.IP *
+.IP \(bu
 .B tzh_ttisstdcnt
 standard/wall indicators, each stored as a one-byte boolean;
 they tell whether the transition times associated with local time types
 were specified as standard time or local (wall clock) time.
-.IP *
+.IP \(bu
 .B tzh_ttisutcnt
 UT/local indicators, each stored as a one-byte boolean;
 they tell whether the transition times associated with local time types
 were specified as UT or local time.
 If a UT/local indicator is set, the corresponding standard/wall indicator
 must also be set.
-.P
+.RE
+.PP
 The standard/wall and UT/local indicators were designed for
 transforming a TZif file's transition times into transitions appropriate
-for another time zone specified via a POSIX-style TZ string that lacks rules.
+for another time zone specified via
+a POSIX.1-2017-style TZ string that lacks rules.
 For example, when TZ="EET\*-2EEST" and there is no TZif file "EET\*-2EEST",
 the idea was to adapt the transition times from a TZif file with the
 well-known name "posixrules" that is present only for this purpose and
@@ -194,7 +199,7 @@ so users desiring (say) Greek time should instead specify
 TZ="Europe/Athens" for better historical coverage, falling back on
 TZ="EET\*-2EEST,M3.5.0/3,M10.5.0/4" if POSIX conformance is required
 and older timestamps need not be handled accurately.
-.P
+.PP
 The
 .BR localtime (3)
 function
@@ -211,13 +216,14 @@ the above header and data are followed by a second header and data,
 identical in format except that
 eight bytes are used for each transition time or leap second time.
 (Leap second counts remain four bytes.)
-After the second header and data comes a newline-enclosed,
-POSIX-TZ-environment-variable-style string for use in handling instants
+After the second header and data comes a newline-enclosed string
+in the style of the contents of a POSIX.1-2017 TZ environment variable,
+for use in handling instants
 after the last transition time stored in the file
 or for all instants if the file has no transitions.
-The POSIX-style TZ string is empty (i.e., nothing between the newlines)
-if there is no POSIX-style representation for such instants.
-If nonempty, the POSIX-style TZ string must agree with the local time
+The TZ string is empty (i.e., nothing between the newlines)
+if there is no POSIX.1-2017-style representation for such instants.
+If nonempty, the TZ string must agree with the local time
 type after the last transition time if present in the eight-byte data;
 for example, given the string
 .q "WET0WEST,M3.5.0/1,M10.5.0"
@@ -229,8 +235,8 @@ Also, if there is at least one transition, time type 0 is associated
 with the time period from the indefinite past up to but not including
 the earliest transition time.
 .SS Version 3 format
-For version-3-format timezone files, the POSIX-TZ-style string may
-use two minor extensions to the POSIX TZ format, as described in
+For version-3-format timezone files, the TZ string may
+use two minor extensions to the POSIX.1-2017 TZ format, as described in
 .BR newtzset (3).
 First, the hours part of its transition times may be signed and range from
 \-167 through 167 instead of the POSIX-required unsigned values
@@ -250,14 +256,14 @@ releases will likely add leap second entries after the expiration, and
 the added leap seconds will change how post-expiration timestamps are treated.
 .SS Interoperability considerations
 Future changes to the format may append more data.
-.P
+.PP
 Version 1 files are considered a legacy format and
 should not be generated, as they do not support transition
 times after the year 2038.
 Readers that understand only Version 1 must ignore
 any data that extends beyond the calculated end of the version
 1 data block.
-.P
+.PP
 Other than version 1, writers should generate
 the lowest version number needed by a file's data.
 For example, a writer should generate a version 4 file
@@ -266,7 +272,7 @@ Likewise, a writer not generating a version 4 file
 should generate a version 3 file only if
 TZ string extensions are necessary to accurately
 model transition times.
-.P
+.PP
 The sequence of time changes defined by the version 1
 header and data block should be a contiguous sub-sequence
 of the time changes defined by the version 2+ header and data
@@ -278,12 +284,12 @@ supporting obsolescent readers use a
 .B tzh_timecnt
 of zero
 in the version 1 data block to save space.
-.P
+.PP
 When a TZif file contains a leap second table expiration
 time, TZif readers should either refuse to process
 post-expiration timestamps, or process them as if the expiration
 time did not exist (possibly with an error indication).
-.P
+.PP
 Time zone designations should consist of at least three (3)
 and no more than six (6) ASCII characters from the set of
 alphanumerics,
@@ -292,15 +298,15 @@ and
 .q "+".
 This is for compatibility with POSIX requirements for
 time zone abbreviations.
-.P
+.PP
 When reading a version 2 or higher file, readers
 should ignore the version 1 header and data block except for
 the purpose of skipping over them.
-.P
+.PP
 Readers should calculate the total lengths of the
 headers and data blocks and check that they all fit within
 the actual file size, as part of a validity check for the file.
-.P
+.PP
 When a positive leap second occurs, readers should append an extra
 second to the local minute containing the second just before the leap
 second.  If this occurs when the UTC offset is not a multiple of 60
@@ -312,16 +318,18 @@ This section documents common problems in reading or writing TZif files.
 Most of these are problems in generating TZif files for use by
 older readers.
 The goals of this section are:
-.IP * 2
+.RS 2
+.IP \(bu 3
 to help TZif writers output files that avoid common
 pitfalls in older or buggy TZif readers,
-.IP *
+.IP \(bu
 to help TZif readers avoid common pitfalls when reading
 files generated by future TZif writers, and
-.IP *
+.IP \(bu
 to help any future specification authors see what sort of
 problems arise when the TZif format is changed.
-.P
+.RE
+.PP
 When new versions of the TZif format have been defined, a
 design goal has been that a reader can successfully use a TZif
 file even if the file is of a later TZif version than what the
@@ -333,23 +341,24 @@ new-version data useful even for older-version readers.
 This section attempts to document these compatibility issues and
 workarounds, as well as to document other common bugs in
 readers.
-.P
+.PP
 Interoperability problems with TZif include the following:
-.IP * 2
+.RS 2
+.IP \(bu 3
 Some readers examine only version 1 data.
 As a partial workaround, a writer can output as much version 1
 data as possible.
 However, a reader should ignore version 1 data, and should use
 version 2+ data even if the reader's native timestamps have only
 32 bits.
-.IP *
+.IP \(bu
 Some readers designed for version 2 might mishandle
 timestamps after a version 3 or higher file's last transition, because
-they cannot parse extensions to POSIX in the TZ-like string.
+they cannot parse extensions to POSIX.1-2017 in the TZ-like string.
 As a partial workaround, a writer can output more transitions
 than necessary, so that only far-future timestamps are
 mishandled by version 2 readers.
-.IP *
+.IP \(bu
 Some readers designed for version 2 do not support
 permanent daylight saving time with transitions after 24:00
 \(en e.g., a TZ string
@@ -367,22 +376,22 @@ for the next time zone east \(en e.g.,
 .q "AST4"
 for permanent
 Atlantic Standard Time (\-04).
-.IP *
+.IP \(bu
 Some readers designed for version 2 or 3, and that require strict
 conformance to RFC 8536, reject version 4 files whose leap second
 tables are truncated at the start or that end in expiration times.
-.IP *
+.IP \(bu
 Some readers ignore the footer, and instead predict future
 timestamps from the time type of the last transition.
 As a partial workaround, a writer can output more transitions
 than necessary.
-.IP *
+.IP \(bu
 Some readers do not use time type 0 for timestamps before
 the first transition, in that they infer a time type using a
 heuristic that does not always select time type 0.
 As a partial workaround, a writer can output a dummy (no-op)
 first transition at an early time.
-.IP *
+.IP \(bu
 Some readers mishandle timestamps before the first
 transition that has a timestamp not less than \-2**31.
 Readers that support only 32-bit timestamps are likely to be
@@ -391,12 +400,12 @@ more prone to this problem, for example, when they process
 bits.
 As a partial workaround, a writer can output a dummy
 transition at timestamp \-2**31.
-.IP *
+.IP \(bu
 Some readers mishandle a transition if its timestamp has
 the minimum possible signed 64-bit value.
 Timestamps less than \-2**59 are not recommended.
-.IP *
-Some readers mishandle POSIX-style TZ strings that
+.IP \(bu
+Some readers mishandle TZ strings that
 contain
 .q "<"
 or
@@ -407,11 +416,11 @@ or
 .q ">"
 for time zone abbreviations containing only alphabetic
 characters.
-.IP *
+.IP \(bu
 Many readers mishandle time zone abbreviations that contain
 non-ASCII characters.
 These characters are not recommended.
-.IP *
+.IP \(bu
 Some readers may mishandle time zone abbreviations that
 contain fewer than 3 or more than 6 characters, or that
 contain ASCII characters other than alphanumerics,
@@ -419,23 +428,23 @@ contain ASCII characters other than alphanumerics,
 and
 .q "+".
 These abbreviations are not recommended.
-.IP *
+.IP \(bu
 Some readers mishandle TZif files that specify
 daylight-saving time UT offsets that are less than the UT
 offsets for the corresponding standard time.
 These readers do not support locations like Ireland, which
-uses the equivalent of the POSIX TZ string
+uses the equivalent of the TZ string
 .q "IST\*-1GMT0,M10.5.0,M3.5.0/1",
 observing standard time
 (IST, +01) in summer and daylight saving time (GMT, +00) in winter.
 As a partial workaround, a writer can output data for the
-equivalent of the POSIX TZ string
+equivalent of the TZ string
 .q "GMT0IST,M3.5.0/1,M10.5.0",
 thus swapping standard and daylight saving time.
 Although this workaround misidentifies which part of the year
 uses daylight saving time, it records UT offsets and time zone
 abbreviations correctly.
-.IP *
+.IP \(bu
 Some readers generate ambiguous timestamps for positive leap seconds
 that occur when the UTC offset is not a multiple of 60 seconds.
 For example, in a timezone with UTC offset +01:23:45 and with
@@ -446,38 +455,41 @@ instead of mapping the latter to 01:23:46, and they will map 78796815 to
 This has not yet been a practical problem, since no civil authority
 has observed such UTC offsets since leap seconds were
 introduced in 1972.
-.P
+.RE
+.PP
 Some interoperability problems are reader bugs that
 are listed here mostly as warnings to developers of readers.
-.IP * 2
+.RS 2
+.IP \(bu 3
 Some readers do not support negative timestamps.
 Developers of distributed applications should keep this
 in mind if they need to deal with pre-1970 data.
-.IP *
+.IP \(bu
 Some readers mishandle timestamps before the first
 transition that has a nonnegative timestamp.
 Readers that do not support negative timestamps are likely to
 be more prone to this problem.
-.IP *
+.IP \(bu
 Some readers mishandle time zone abbreviations like
 .q "\*-08"
 that contain
 .q "+",
 .q "\*-",
 or digits.
-.IP *
+.IP \(bu
 Some readers mishandle UT offsets that are out of the
 traditional range of \-12 through +12 hours, and so do not
 support locations like Kiritimati that are outside this
 range.
-.IP *
+.IP \(bu
 Some readers mishandle UT offsets in the range [\-3599, \-1]
 seconds from UT, because they integer-divide the offset by
 3600 to get 0 and then display the hour part as
 .q "+00".
-.IP *
+.IP \(bu
 Some readers mishandle UT offsets that are not a multiple
 of one hour, or of 15 minutes, or of 1 minute.
+.RE
 .SH SEE ALSO
 .BR time (2),
 .BR localtime (3),
@@ -485,7 +497,7 @@ of one hour, or of 15 minutes, or of 1 minute.
 .BR tzselect (8),
 .BR zdump (8),
 .BR zic (8).
-.P
+.PP
 Olson A, Eggert P, Murchison K. The Time Zone Information Format (TZif).
 2019 Feb.
 .UR https://\:datatracker.ietf.org/\:doc/\:html/\:rfc8536
diff --git a/upstream/fedora-rawhide/man5/udev.conf.5 b/upstream/fedora-rawhide/man5/udev.conf.5
index db1e9cec..635aa734 100644
--- a/upstream/fedora-rawhide/man5/udev.conf.5
+++ b/upstream/fedora-rawhide/man5/udev.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "UDEV\&.CONF" "5" "" "systemd 255" "udev.conf"
+.TH "UDEV\&.CONF" "5" "" "systemd 256~rc3" "udev.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -20,15 +20,35 @@
 .\" * MAIN CONTENT STARTS HERE *
 .\" -----------------------------------------------------------------
 .SH "NAME"
-udev.conf \- Configuration for device event managing daemon
+udev.conf, udev.conf.d \- Configuration for device event managing daemon
 .SH "SYNOPSIS"
 .PP
+.RS 4
 /etc/udev/udev\&.conf
+.RE
+.RS 4
+/run/udev/udev\&.conf
+.RE
+.RS 4
+/usr/lib/udev/udev\&.conf
+.RE
+.RS 4
+/etc/udev/udev\&.conf\&.d/*\&.conf
+.RE
+.RS 4
+/run/udev/udev\&.conf\&.d/*\&.conf
+.RE
+.RS 4
+/usr/lib/udev/udev\&.conf\&.d/*\&.conf
+.RE
 .SH "DESCRIPTION"
 .PP
-\fBsystemd-udevd\fR(8)
-expects its main configuration file at
-/etc/udev/udev\&.conf\&. It consists of a set of variables allowing the user to override default udev values\&. All empty lines or lines beginning with \*(Aq#\*(Aq are ignored\&. The following variables can be set:
+These files contain configuration options for
+\fBsystemd-udevd\fR(8)\&. The syntax of these files is very simple: a list of assignments, one per line\&. All empty lines or lines beginning with
+"#"
+are ignored\&.
+.PP
+The following options can be set:
 .PP
 \fIudev_log=\fR
 .RS 4
@@ -37,7 +57,22 @@ The log level\&. Valid values are the numerical syslog priorities or their textu
 \fBinfo\fR
 and
 \fBdebug\fR\&.
+.if n \{\
 .sp
+.\}
+.RS 4
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+.ps +1
+\fBNote\fR
+.ps -1
+.br
+This option is also honored by
+\fBudevadm\fR(8)\&.
+.sp .5v
+.RE
 Added in version 216\&.
 .RE
 .PP
@@ -107,6 +142,4 @@ can be configured by command line options and the kernel command line (see
 \fBsystemd-udevd\fR(8))\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd-udevd\fR(8),
-\fBudev\fR(7),
-\fBudevadm\fR(8)
+\fBsystemd-udevd\fR(8), \fBudev\fR(7), \fBudevadm\fR(8)
diff --git a/upstream/fedora-rawhide/man5/updatedb.conf.5 b/upstream/fedora-rawhide/man5/updatedb.conf.5
deleted file mode 100644
index 89181379..00000000
--- a/upstream/fedora-rawhide/man5/updatedb.conf.5
+++ /dev/null
@@ -1,138 +0,0 @@
-.\" A man page for updatedb.conf. -*- nroff -*-
-.\"
-.\" Copyright (C) 2005, 2007, 2008 Red Hat, Inc. All rights reserved.
-.\"
-.\" This copyrighted material is made available to anyone wishing to use,
-.\" modify, copy, or redistribute it subject to the terms and conditions of the
-.\" GNU General Public License v.2.
-.\"
-.\" This program is distributed in the hope that it will be useful, but WITHOUT
-.\" ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or 
-.\" FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for 
-.\" more details.
-.\"
-.\" You should have received a copy of the GNU General Public License along
-.\" with this program; if not, write to the Free Software Foundation, Inc.,
-.\" 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-.\"
-.\" Author: Miloslav Trmac <mitr@redhat.com>
-.TH updatedb.conf 5 "Jun 2008" mlocate
-
-.SH NAME
-/etc/updatedb.conf \- a configuration file for updatedb(8)
-
-.SH DESCRIPTION
-.B /etc/updatedb.conf
-is a text file.
-Blank lines are ignored.
-A
-.B #
-character outside of a quoted string starts a comment
-extending until end of line.
-
-Other lines must be of the following form:
-.RS
-.I VARIABLE
-.B =
-\fB"\fIVALUE\fB"\fR
-.RE
-
-White space between tokens is ignored.
-.I VARIABLE
-is an alphanumeric string which does not start with a digit.
-.I VALUE
-can contain any character except for \fB\(dq\fR.
-No escape mechanism is supported within
-.I VALUE
-and there is no way to write
-.I VALUE
-spanning more than one line.
-
-Unknown
-.I VARIABLE
-values are considered an error.
-The defined variables are:
-
-.TP
-\fBPRUNEFS\fR
-A whitespace-separated list of file system types (as used in \fB/etc/mtab\fR)
-which should not be scanned by
-.BR updatedb (8).
-The file system type matching is case-insensitive.  By default, no file system
-types are skipped.
-
-When scanning a file system is skipped,
-all file systems mounted in the subtree are skipped too,
-even if their type does not match any entry in \fBPRUNEFS\fR.
-
-.TP
-\fBPRUNENAMES\fR
-A whitespace-separated list of directory names (without paths) which should not
-be scanned by
-.BR updatedb (8).
-By default, no directory names are skipped.
-
-Note that only directories can be specified, and no pattern mechanism (e.g.
-globbing) is used.
-
-.TP
-\fBPRUNEPATHS\fR
-A whitespace-separated list of path names of directories which should not be
-scanned by
-.BR updatedb (8).
-Each path name must be exactly in the form
-in which the directory would be reported by
-.BR locate (1).
-
-By default, no paths are skipped.
-
-.TP
-\fBPRUNE_BIND_MOUNTS\FR
-One of the strings \fB0\fR, \fBno\fR, \fB1\fR or \fByes\fR.
-If
-.B PRUNE_BIND_MOUNTS
-is \fB1\fR or \fByes\fR,
-bind mounts are not scanned by
-.BR updatedb (8).
-All file systems mounted in the subtree of a bind mount are skipped as well,
-even if they are not bind mounts.
-As an exception, bind mounts of a directory on itself are not skipped.
-
-By default, bind mounts are not skipped.
-
-.SH NOTES
-When a directory is matched by \fBPRUNEFS\fR, \fBPRUNENAMES\fR or
-\fBPRUNEPATHS\fR,
-.BR updatedb (8)
-does not scan the contents of the directory.
-The path of the directory itself is, however, entered in the created database.
-For example, if
-.I /tmp
-is in \fBPRUNEPATHS\fR,
-.BR locate (1)
-will not show any files stored in \fI/tmp\fR,
-but it can show the
-.I /tmp
-directory.
-This behavior differs from traditional
-.B locate
-implementations.
-
-In some
-.BR updatedb (8)
-implementations \fBPRUNEPATHS\fR can be used to exclude non-directory files.
-This is not the case in this implementation.
-
-.B /etc/updatedb.conf
-is a shell script in some implementations,
-which allows much more flexibility in defining the variables.
-Equivalent functionality can be achieved by using the command-line options
-to
-.BR updatedb (8).
-
-.SH AUTHOR
-Miloslav Trmac <mitr@redhat.com>
-
-.SH SEE ALSO
-.BR locate (1),
-.BR updatedb (8)
diff --git a/upstream/fedora-rawhide/man5/user@.service.5 b/upstream/fedora-rawhide/man5/user@.service.5
index 0f068135..e6e5d656 100644
--- a/upstream/fedora-rawhide/man5/user@.service.5
+++ b/upstream/fedora-rawhide/man5/user@.service.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "USER@\&.SERVICE" "5" "" "systemd 255" "user@.service"
+.TH "USER@\&.SERVICE" "5" "" "systemd 256~rc3" "user@.service"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -188,10 +188,4 @@ user\-\fIUID\fR\&.slice
 units by default don\*(Aqt have a unit file\&. The resource limits are set through a drop\-in, which can be easily replaced or extended following standard drop\-in mechanisms discussed in the first section\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd.service\fR(5),
-\fBsystemd.slice\fR(5),
-\fBsystemd.resource-control\fR(5),
-\fBsystemd.exec\fR(5),
-\fBsystemd.special\fR(7),
-\fBpam\fR(8)
+\fBsystemd\fR(1), \fBsystemd.service\fR(5), \fBsystemd.slice\fR(5), \fBsystemd.resource-control\fR(5), \fBsystemd.exec\fR(5), \fBsystemd.special\fR(7), \fBcapsule@.service\fR(5), \fBpam\fR(8)
diff --git a/upstream/fedora-rawhide/man5/utmp.5 b/upstream/fedora-rawhide/man5/utmp.5
index 99d3fed5..48f300e4 100644
--- a/upstream/fedora-rawhide/man5/utmp.5
+++ b/upstream/fedora-rawhide/man5/utmp.5
@@ -8,7 +8,7 @@
 .\" Modified 1996-07-20 by Michael Haardt
 .\" Modified 1997-07-02 by Nicolás Lichtmaier <nick@debian.org>
 .\" Modified 2004-10-31 by aeb, following Gwenole Beauchesne
-.TH utmp 5 2023-10-31 "Linux man-pages 6.06"
+.TH utmp 5 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 utmp, wtmp \- login records
 .SH SYNOPSIS
diff --git a/upstream/fedora-rawhide/man5/vconsole.conf.5 b/upstream/fedora-rawhide/man5/vconsole.conf.5
index ef220e50..04d58ef0 100644
--- a/upstream/fedora-rawhide/man5/vconsole.conf.5
+++ b/upstream/fedora-rawhide/man5/vconsole.conf.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "VCONSOLE\&.CONF" "5" "" "systemd 255" "vconsole.conf"
+.TH "VCONSOLE\&.CONF" "5" "" "systemd 256~rc3" "vconsole.conf"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -119,9 +119,4 @@ FONT=eurlatgr
 .\}
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-vconsole-setup.service\fR(8),
-\fBloadkeys\fR(1),
-\fBsetfont\fR(8),
-\fBlocale.conf\fR(5),
-\fBsystemd-localed.service\fR(8)
+\fBsystemd\fR(1), \fBsystemd-vconsole-setup.service\fR(8), \fBloadkeys\fR(1), \fBsetfont\fR(8), \fBlocale.conf\fR(5), \fBsystemd-localed.service\fR(8)
diff --git a/upstream/fedora-rawhide/man5/veritytab.5 b/upstream/fedora-rawhide/man5/veritytab.5
index d68a8af4..c8b0b5d3 100644
--- a/upstream/fedora-rawhide/man5/veritytab.5
+++ b/upstream/fedora-rawhide/man5/veritytab.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "VERITYTAB" "5" "" "systemd 255" "veritytab"
+.TH "VERITYTAB" "5" "" "systemd 256~rc3" "veritytab"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -40,7 +40,7 @@ Each line is in the form
 .RS 4
 .\}
 .nf
-\fIvolume\-name\fR \fIdata\-device\fR \fIhash\-device\fR \fIroothash\fR \fIoptions\fR
+\fIvolume\-name\fR \fIdata\-device\fR \fIhash\-device\fR \fIroothash\fR [\fIoptions\fR]
 .fi
 .if n \{\
 .RE
@@ -52,15 +52,17 @@ The first field contains the name of the resulting verity volume; its block devi
 /dev/mapper/\&.
 .PP
 The second field contains a path to the underlying block data device, or a specification of a block device via
-"UUID="
-followed by the UUID\&.
+\fIUUID=\fR
+followed by the
+\fIUUID\fR\&.
 .PP
 The third field contains a path to the underlying block hash device, or a specification of a block device via
-"UUID="
-followed by the UUID\&.
+\fIUUID=\fR
+followed by the
+\fIUUID\fR\&.
 .PP
 The fourth field is the
-"roothash"
+\fIroothash\fR
 in hexadecimal\&.
 .PP
 The fifth field, if present, is a comma\-delimited list of options\&. The following options are recognized:
@@ -74,7 +76,11 @@ Added in version 254\&.
 .PP
 \fBformat=\fR\fB\fINUMBER\fR\fR
 .RS 4
-Specifies the hash version type\&. Format type 0 is original Chrome OS version\&. Format type 1 is modern version\&.
+Specifies the hash version type\&. Format type
+"0"
+is original Chrome OS version\&. Format type
+"1"
+is modern version\&.
 .sp
 Added in version 254\&.
 .RE
@@ -111,26 +117,38 @@ Added in version 254\&.
 \fBsalt=\fR\fB\fIHEX\fR\fR
 .RS 4
 Salt used for format or verification\&. Format is a hexadecimal string; 256 bytes long maximum;
-"\-"is the special value for empty\&.
+"\-"
+is the special value for empty\&.
 .sp
 Added in version 254\&.
 .RE
 .PP
 \fBuuid=\fR\fB\fIUUID\fR\fR
 .RS 4
-Use the provided UUID for format command instead of generating new one\&. The UUID must be provided in standard UUID format, e\&.g\&. 12345678\-1234\-1234\-1234\-123456789abc\&.
+Use the provided
+\fIUUID\fR
+instead of generating new one\&. The
+\fIUUID\fR
+must be provided in standard
+UUID
+format, e\&.g\&.
+"12345678\-1234\-1234\-1234\-123456789abc"\&.
 .sp
 Added in version 254\&.
 .RE
 .PP
 \fBignore\-corruption\fR, \fBrestart\-on\-corruption\fR, \fBpanic\-on\-corruption\fR
 .RS 4
-Defines what to do if a data verity problem is detected (data corruption)\&. Without these options kernel fails the IO operation with I/O error\&. With
-"\-\-ignore\-corruption"
+Defines what to do if a data verity problem is detected (data corruption)\&. Without these options kernel fails the
+IO
+operation with
+I/O
+error\&. With
+\fB\-\-ignore\-corruption\fR
 option the corruption is only logged\&. With
-"\-\-restart\-on\-corruption"
+\fB\-\-restart\-on\-corruption\fR
 or
-"\-\-panic\-on\-corruption"
+\fB\-\-panic\-on\-corruption\fR
 the kernel is restarted (panicked) immediately\&. (You have to provide way how to avoid restart loops\&.)
 .sp
 Added in version 248\&.
@@ -138,15 +156,43 @@ Added in version 248\&.
 .PP
 \fBignore\-zero\-blocks\fR
 .RS 4
-Instruct kernel to not verify blocks that are expected to contain zeroes and always directly return zeroes instead\&. WARNING: Use this option only in very specific cases\&. This option is available since Linux kernel version 4\&.5\&.
+Instruct kernel to not verify blocks that are expected to contain zeroes and always directly return zeroes instead\&.
+.if n \{\
 .sp
+.\}
+.RS 4
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+.ps +1
+\fBWarning\fR
+.ps -1
+.br
+Use this option only in very specific cases\&. This option is available since Linux kernel version 4\&.5\&.
+.sp .5v
+.RE
 Added in version 248\&.
 .RE
 .PP
 \fBcheck\-at\-most\-once\fR
 .RS 4
-Instruct kernel to verify blocks only the first time they are read from the data device, rather than every time\&. WARNING: It provides a reduced level of security because only offline tampering of the data device\*(Aqs content will be detected, not online tampering\&. This option is available since Linux kernel version 4\&.17\&.
+Instruct kernel to verify blocks only the first time they are read from the data device, rather than every time\&.
+.if n \{\
 .sp
+.\}
+.RS 4
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+.ps +1
+\fBWarning\fR
+.ps -1
+.br
+It provides a reduced level of security because only offline tampering of the data device\*(Aqs content will be detected, not online tampering\&. This option is available since Linux kernel version 4\&.17\&.
+.sp .5v
+.RE
 Added in version 248\&.
 .RE
 .PP
@@ -160,14 +206,16 @@ Added in version 254\&.
 .PP
 \fBfec\-device=\fR\fB\fIPATH\fR\fR
 .RS 4
-Use forward error correction (FEC) to recover from corruption if hash verification fails\&. Use encoding data from the specified device\&. The fec device argument can be block device or file image\&. For format, if fec device path doesn\*(Aqt exist, it will be created as file\&. Note: block sizes for data and hash devices must match\&. Also, if the verity data_device is encrypted the fec_device should be too\&.
+Use forward error correction (FEC) to recover from corruption if hash verification fails\&. Use encoding data from the specified device\&. The fec device argument can be block device or file image\&. If fec device path doesn\*(Aqt exist, it will be created as file\&. Note: block sizes for data and hash devices must match\&. Also, if the verity data_device is encrypted the fec_device should be too\&.
 .sp
 Added in version 254\&.
 .RE
 .PP
 \fBfec\-offset=\fR\fB\fIBYTES\fR\fR
 .RS 4
-This is the offset, in bytes, from the start of the FEC device to the beginning of the encoding data\&. (Aligned on 512 bytes\&.)
+This is the offset, in bytes, from the start of the
+FEC
+device to the beginning of the encoding data\&. (Aligned on 512 bytes\&.)
 .sp
 Added in version 254\&.
 .RE
@@ -268,8 +316,4 @@ data /etc/data /etc/hash a5ee4b42f70ae1f46a08a7c92c2e0a20672ad2f514792730f5d49d7
 .\}
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemd-veritysetup@.service\fR(8),
-\fBsystemd-veritysetup-generator\fR(8),
-\fBfstab\fR(5),
-\fBveritysetup\fR(8),
+\fBsystemd\fR(1), \fBsystemd-veritysetup@.service\fR(8), \fBsystemd-veritysetup-generator\fR(8), \fBfstab\fR(5), \fBveritysetup\fR(8)
author	Daniel Baumann <daniel.baumann@progress-linux.org>	2024-06-17 10:52:03 +0000
committer	Daniel Baumann <daniel.baumann@progress-linux.org>	2024-06-17 10:52:03 +0000
commit	932e4432596447eb9331cc2a2bb74a26a35b4efc (patch)
tree	95161711ea07fd64f0c82d6e7943024c033dd5a8 /upstream/fedora-rawhide/man5
parent	Adding debian version 4.22.0-1. (diff)
download	manpages-l10n-932e4432596447eb9331cc2a2bb74a26a35b4efc.tar.xz manpages-l10n-932e4432596447eb9331cc2a2bb74a26a35b4efc.zip