man/systemd: drop explanation about SysV compatibilities

Sooner or later, we will drop the explained SysV compatibilities.
Let's remove them from the man page now to make not people rely on that.

diff --git a/man/systemd.xml b/man/systemd.xml
index 204f31ff29b0b800b9e2b1535d607c9e66dec101..88dd158021b68e18dfbb5a456d2d8d5ed81b624b 100644 (file)
--- a/man/systemd.xml
+++ b/man/systemd.xml
@@ -30,7 +30,6 @@
     <cmdsynopsis>
       <command>init</command>
       <arg choice="opt" rep="repeat">OPTIONS</arg>
-      <arg choice="req">COMMAND</arg>
     </cmdsynopsis>
   </refsynopsisdiv>
 
@@ -47,13 +46,6 @@
     <citerefentry><refentrytitle>user@.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
     service.</para>
 
-    <para>For compatibility with SysV, if the binary is called as <command>init</command> and is not the
-    first process on the machine (PID is not 1), it will execute <command>telinit</command> and pass all
-    command line arguments unmodified. That means <command>init</command> and <command>telinit</command> are
-    mostly equivalent when invoked from normal login sessions. See
-    <citerefentry><refentrytitle>telinit</refentrytitle><manvolnum>8</manvolnum></citerefentry> for more
-    information.</para>
-
     <para>When run as a system instance, systemd interprets the
     configuration file <filename>system.conf</filename> and the files
     in <filename>system.conf.d</filename> directories; when run as a
@@ -235,14 +227,8 @@
     xawf -eo pid,user,cgroup,args</command> is particularly useful to list all processes and the systemd
     units they belong to.).</para>
 
-    <para>systemd is compatible with the SysV init system to a large
-    degree: SysV init scripts are supported and simply read as an
-    alternative (though limited) configuration file format. The SysV
-    <filename>/dev/initctl</filename> interface is provided, and
-    compatibility implementations of the various SysV client tools are
-    available. In addition to that, various established Unix
-    functionality such as <filename>/etc/fstab</filename> or the
-    <filename>utmp</filename> database are supported.</para>
+    <para>systemd is compatible with various established Unix functionality such as
+    <filename>/etc/fstab</filename> or the <filename>utmp</filename> database.</para>
 
     <para>systemd has a minimal transaction system: if a unit is
     requested to start up or shut down it will add it and all its
@@ -328,32 +314,6 @@
         </para></listitem>
       </varlistentry>
     </variablelist>
-
-    <variablelist>
-      <varlistentry>
-        <term>SysV init scripts directory</term>
-
-        <listitem><para>The location of the SysV init script directory
-        varies between distributions. If systemd cannot find a native
-        unit file for a requested service, it will look for a SysV
-        init script of the same name (with the
-        <filename>.service</filename> suffix
-        removed).</para></listitem>
-      </varlistentry>
-    </variablelist>
-
-    <variablelist>
-      <varlistentry>
-        <term>SysV runlevel link farm directory</term>
-
-        <listitem><para>The location of the SysV runlevel link farm
-        directory varies between distributions. systemd will take the
-        link farm into account when figuring out whether a service
-        shall be enabled. Note that a service unit with a native unit
-        configuration file cannot be started by activating it in the
-        SysV runlevel link farm.</para></listitem>
-      </varlistentry>
-    </variablelist>
   </refsect1>
 
   <refsect1>
@@ -1519,16 +1479,6 @@
         projects.</para></listitem>
       </varlistentry>
 
-      <varlistentry>
-        <term><filename>/dev/initctl</filename></term>
-
-        <listitem><para>Limited compatibility support for the SysV
-        client interface, as implemented by the
-        <filename>systemd-initctl.service</filename> unit. This is a
-        named pipe in the file system. This interface is obsolete and
-        should not be used in new applications.</para></listitem>
-      </varlistentry>
-
       <varlistentry>
         <term><filename>/usr/lib/clock-epoch</filename></term>
 

diff --git a/tools/command_ignorelist b/tools/command_ignorelist
index 50f01c9544d8be06faef0fd42668abb44ada744f..fed0bf052dcf4997daf4f35f04b62ade13a1a4bf 100644 (file)
--- a/tools/command_ignorelist
+++ b/tools/command_ignorelist
@@ -359,8 +359,6 @@ systemd.xml ./refsect1[title="Options"]/refsect2[title="Options that duplicate k
 systemd.xml ./refsect1[title="Options"]/refsect2[title="Options that duplicate kernel command line settings"]/variablelist/varlistentry[term="--default-standard-output="]
 systemd.xml ./refsect1[title="Directories"]/variablelist[1]/varlistentry[term="System unit directories"]
 systemd.xml ./refsect1[title="Directories"]/variablelist[2]/varlistentry[term="User unit directories"]
-systemd.xml ./refsect1[title="Directories"]/variablelist[3]/varlistentry[term="SysV init scripts directory"]
-systemd.xml ./refsect1[title="Directories"]/variablelist[4]/varlistentry[term="SysV runlevel link farm directory"]
 systemd.xml ./refsect1[title="Signals"]/variablelist/varlistentry[term="SIGTERM"]
 systemd.xml ./refsect1[title="Signals"]/variablelist/varlistentry[term="SIGINT"]
 systemd.xml ./refsect1[title="Signals"]/variablelist/varlistentry[term="SIGWINCH"]