Fix typo in SANE

Fix the instructions for Fcron in the systemd book. We have a systemd unit, not an init script.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@20878 af4574ff-66df-0310-9fd7-8a98e5e911e0
This commit is contained in:
Douglas R. Reno 2018-12-28 15:57:47 +00:00
parent a17dfe79ec
commit ecd1111822
4 changed files with 16 additions and 4 deletions

View File

@ -1,12 +1,12 @@
<!-- $LastChangedBy$ $Date$ -->
<!ENTITY day "27"> <!-- Always 2 digits -->
<!ENTITY day "28"> <!-- Always 2 digits -->
<!ENTITY month "12"> <!-- Always 2 digits -->
<!ENTITY year "2018">
<!ENTITY copyrightdate "2001-&year;">
<!ENTITY copyholder "The BLFS Development Team">
<!ENTITY version "&year;-&month;-&day;">
<!ENTITY releasedate "December 27th, &year;">
<!ENTITY releasedate "December 28th, &year;">
<!ENTITY pubdate "&year;-&month;-&day;"> <!-- metadata req. by TLDP -->
<!ENTITY blfs-version "svn"> <!-- svn|[release #] -->
<!ENTITY lfs-version "development"> <!-- x.y|development -->

View File

@ -335,9 +335,11 @@ EOF</userinput></screen>
user, start fcron and generate the
<filename>/var/spool/fcron/systab</filename> file:</para>
<screen role="root"><userinput>/etc/rc.d/init.d/fcron start &amp;&amp;
<screen role="root" revision="sysv"><userinput>/etc/rc.d/init.d/fcron start &amp;&amp;
fcrontab -z -u systab</userinput></screen>
<screen role="root" revision="systemd"><userinput>systemctl start fcron &amp;&amp;
fcrontab -z -u systab</userinput></screen>
</sect3>
</sect2>

View File

@ -41,6 +41,16 @@
</itemizedlist>
</listitem>
-->
<listitem revision="systemd">
<para>December 28th, 2018</para>
<itemizedlist>
<listitem>
<para>[renodr] - Fix Fcron's configuration instructions to support systemctl instead of sysvinit
bootscripts.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>December 27th, 2018</para>
<itemizedlist>

View File

@ -37,7 +37,7 @@
<title>Introduction to SANE</title>
<para><application>SANE</application> is short for Scanner Access Now Easy.
Scanner access; however, is far from easy, since every vendor has their own
Scanner access, however, is far from easy, since every vendor has their own
protocols. The only known protocol that should bring some unity into this
chaos is the TWAIN interface, but this is too imprecise to allow a stable
scanning framework. Therefore, <application>SANE</application> comes with