systemd-245-3.parabola1: updating version

1 files changed, 15 insertions, 15 deletions

diff --git a/libre/systemd/0001-FSDG-man-Refer-to-the-operating-system-as-GNU-Linux.patch b/libre/systemd/0001-FSDG-man-Refer-to-the-operating-system-as-GNU-Linux.patch
index 92d9f0ee8..c626c48cc 100644
--- a/libre/systemd/0001-FSDG-man-Refer-to-the-operating-system-as-GNU-Linux.patch
+++ b/libre/systemd/0001-FSDG-man-Refer-to-the-operating-system-as-GNU-Linux.patch
@@ -143,23 +143,23 @@ index c4763fd561..54bba23666 100644
  
            <row>
 diff --git a/man/systemd-machine-id-setup.xml b/man/systemd-machine-id-setup.xml
-index 9e84fd8ccb..7f0dcd14d7 100644
+index 7caf35f8e8..18d9c5a33b 100644
 --- a/man/systemd-machine-id-setup.xml
 +++ b/man/systemd-machine-id-setup.xml
-@@ -58,7 +58,7 @@
+@@ -55,7 +55,7 @@
        and is different for every booted instance of the
        VM.</para></listitem>
  
--      <listitem><para>Similarly, if run inside a Linux container
-+      <listitem><para>Similarly, if run inside a container
-       environment and a UUID is configured for the container, this is
-       used to initialize the machine ID. For details, see the
-       documentation of the <ulink
+-      <listitem><para>Similarly, if run inside a Linux container environment and a UUID is configured for the
++      <listitem><para>Similarly, if run inside a container environment and a UUID is configured for the
+       container, this is used to initialize the machine ID. For details, see the documentation of the <ulink
+       url="https://systemd.io/CONTAINER_INTERFACE">Container Interface</ulink>.</para></listitem>
+
 diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml
-index c895adaaf3..d2dc0538ca 100644
+index 53c46a1018..a2ccf4fae2 100644
 --- a/man/systemd-resolved.service.xml
 +++ b/man/systemd-resolved.service.xml
-@@ -47,7 +47,7 @@
+@@ -44,7 +44,7 @@
        <citerefentry project='man-pages'><refentrytitle>getaddrinfo</refentrytitle><manvolnum>3</manvolnum></citerefentry> API as defined
        by <ulink url="https://tools.ietf.org/html/rfc3493">RFC3493</ulink> and its related resolver functions,
        including <citerefentry project='man-pages'><refentrytitle>gethostbyname</refentrytitle><manvolnum>3</manvolnum></citerefentry>. This
@@ -168,7 +168,7 @@ index c895adaaf3..d2dc0538ca 100644
        validation status information however, and is synchronous only. This API is backed by the glibc Name Service
        Switch (<citerefentry project='man-pages'><refentrytitle>nss</refentrytitle><manvolnum>5</manvolnum></citerefentry>). Usage of the
        glibc NSS module <citerefentry><refentrytitle>nss-resolve</refentrytitle><manvolnum>8</manvolnum></citerefentry>
-@@ -153,7 +153,7 @@
+@@ -190,7 +190,7 @@
  
      <itemizedlist>
        <listitem><para><command>systemd-resolved</command> maintains the
@@ -177,7 +177,7 @@ index c895adaaf3..d2dc0538ca 100644
        programs. This file may be symlinked from <filename>/etc/resolv.conf</filename>. This file lists the 127.0.0.53
        DNS stub (see above) as the only DNS server. It also contains a list of search domains that are in use by
        systemd-resolved. The list of search domains is always kept up-to-date. Note that
-@@ -169,7 +169,7 @@
+@@ -206,7 +206,7 @@
        <command>systemd-resolved</command>. This file does not contain any search domains.</para></listitem>
  
        <listitem><para><command>systemd-resolved</command> maintains the
@@ -213,7 +213,7 @@ index 19c2ca9907..5fd6c1598f 100644
          can be inherited between processes.</para></listitem>
        </varlistentry>
 diff --git a/man/systemd.xml b/man/systemd.xml
-index 17ab59beb5..89086558c7 100644
+index 28bf49e131..5cfd0de31a 100644
 --- a/man/systemd.xml
 +++ b/man/systemd.xml
 @@ -37,7 +37,7 @@
@@ -222,10 +222,10 @@ index 17ab59beb5..89086558c7 100644
  
 -    <para>systemd is a system and service manager for Linux operating systems. When run as first process on
 +    <para>systemd is a system and service manager for GNU/Linux operating systems. When run as first process on
-     boot (as PID 1), it acts as init system that brings up and maintains userspace services. Seperate
+     boot (as PID 1), it acts as init system that brings up and maintains userspace services. Separate
      instances are started for logged-in users to start their services.</para>
  
-@@ -704,9 +704,9 @@
+@@ -703,9 +703,9 @@
      <title>Kernel Command Line</title>
  
      <para>When run as the system instance systemd parses a number of options listed below. They can be
@@ -233,7 +233,7 @@ index 17ab59beb5..89086558c7 100644
 +    specified as kernel command line arguments<footnote><para>If run inside a container these arguments
      may be passed as command line arguments to systemd itself, next to any of the command line options listed
 -    in the Options section above. If run outside of Linux containers, these arguments are parsed from
-+    in the Options section above. If run outside of a container, these arguments are parsed from
++    in the Options section above. If run outside of containers, these arguments are parsed from
      <filename>/proc/cmdline</filename> instead.</para></footnote>, or through the
      <literal>SystemdOptions</literal> EFI variable (on EFI systems). The kernel command line has higher
      priority. Following variables are understood:</para>