V254 stable batch

NEWS

@@ -34,6 +34,9 @@ CHANGES WITH 254:
           trailing with escape as a non comment line. For details, see:
           https://github.com/systemd/systemd/issues/27975
 
+        * PrivateNetwork=yes and NetworkNamespacePath= now imply
+          PrivateMounts=yes unless PrivateMounts=no is explicitly specified.
+
         * Behaviour of sandboxing options for the per-user service manager
           units has changed. They now imply PrivateUsers=yes, which means user
           namespaces will be implicitly enabled when a sandboxing option is
@@ -71,10 +74,12 @@ CHANGES WITH 254:
 
         Service Manager:
 
-        * "Startup" memory settings are now supported. Previously IO and CPU
-          settings were already supported via StartupCPUWeight= and similar.
-          The same logic has been added for the various per-unit memory
-          settings StartupMemoryMax= and related.
+        * Memory limits that apply while the unit is activating are now
+          supported. Previously IO and CPU settings were already supported via
+          StartupCPUWeight= and similar. The same logic has been added for the
+          various manager and unit memory settings (DefaultStartupMemoryLow=,
+          StartupMemoryLow=, StartupMemoryHigh=, StartupMemoryMax=,
+          StartupMemorySwapMax=, StartupMemoryZSwapMax=).
 
         * The service manager gained support for enqueuing POSIX signals to
           services that carry an additional integer value, exposing the
@@ -574,7 +579,7 @@ CHANGES WITH 254:
           specified command line after sending the requested messages. This is
           useful for sending out READY=1 first, and then continuing invocation
           without changing process ID, so that the tool can be nicely used
-          within an ExecStart= line of a unit file that uses Type=ready.
+          within an ExecStart= line of a unit file that uses Type=notify.
 
         sd-event + sd-bus APIs:
 
@@ -658,8 +663,8 @@ CHANGES WITH 254:
           server-side environment variable expansion in specified command
           lines. Expansion defaults to enabled for all execution types except
           --scope, where it defaults to off (and prints a warning) for backward
-          compatibility reasons. --scope will be flipped to default enabled too
-          in a future release, so if you are using --scope and passing a '$'
+          compatibility reasons. --scope will be flipped to enabled by default
+          too in a future release. If you are using --scope and passing a '$'
           character in the payload you should start explicitly using
           --expand-environment=yes/no according to the use case.
 
@@ -722,7 +727,7 @@ CHANGES WITH 254:
           systemd.battery-check=0 through the kernel command line.
 
         * The 'passwdqc' library is now supported as an alternative to the
-          'pwquality' library and it can be selected at build time.
+          'pwquality' library and can be selected at build time.
 
         Contributions from: 김인수, 07416, Addison Snelling, Adrian Vovk,
         Aidan Dang, Alexander Krabler, Alfred Klomp, Anatoli Babenia,

configure

@@ -21,4 +21,4 @@ done
 
 export "${cflags?}" "${cxxflags?}"
 set -x
-exec meson build "${args[@]}"
+exec meson setup build "${args[@]}"

hwdb.d/60-keyboard.hwdb

@@ -1438,9 +1438,13 @@ evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMicro-Star*:pn*PR200*:*
  KEYBOARD_KEY_f7=reserved
  KEYBOARD_KEY_f8=reserved
 
-# MSI Wind U90/U100 generates separate touchpad on/off keycodes so ignore touchpad toggle keycode
+# MSI Wind U90/U100 generates separate touchpad on/off keycodes so ignore touchpad toggle keycode.
+# Also ignore Wi-Fi and Bluetooth keycodes, because they are generated when the HW rfkill state
+# changes, but the userspace also toggles the SW rfkill upon receiving these keycodes.
 evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMICRO-STAR*:pnU90/U100:*
- KEYBOARD_KEY_e4=reserved
+ KEYBOARD_KEY_e4=unknown
+ KEYBOARD_KEY_e2=unknown
+ KEYBOARD_KEY_f6=unknown
 
 # Keymaps MSI Prestige And MSI Modern FnKeys and Special keys
 evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMicro-Star*:pn*Prestige*:*

man/journalctl.xml

@@ -814,7 +814,7 @@
         <term><option>--smart-relinquish-var</option></term>
 
         <listitem><para>Similar to <option>--relinquish-var</option>, but executes no operation if the root
-        file system and <filename>/var/lib/journal/</filename> reside on the same mount point. This operation
+        file system and <filename>/var/log/journal/</filename> reside on the same mount point. This operation
         is used during system shutdown in order to make the journal daemon stop writing data to
         <filename>/var/log/journal/</filename> in case that directory is located on a mount point that needs
         to be unmounted.</para></listitem>

man/systemd-fsck@.service.xml

@@ -41,12 +41,11 @@
     filesystem was not checked in the initrd. <filename>[email protected]</filename> is used for all
     other file systems and for the root file system in the initrd.</para>
 
-    <para>These services are started at boot if
-    <option>passno</option> in <filename>/etc/fstab</filename> for the
-    file system is set to a value greater than zero. The file system
-    check for root is performed before the other file systems. Other
-    file systems may be checked in parallel, except when they are on
-    the same rotating disk.</para>
+    <para>These services are started at boot if <option>passno</option> in <filename>/etc/fstab</filename>
+    for the file system is set to a value greater than zero, but only if it is also configured to be
+    mounted at boot (i.e. without <literal>noauto</literal> option). The file system check for root is
+    performed before the other file systems. Other file systems may be checked in parallel, except when
+    they are on the same rotating disk.</para>
 
     <para><filename>systemd-fsck</filename> does not know any details
     about specific filesystems, and simply executes file system