sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

dev-manual: Fixed some "systemd" capitalization issues. 

I was using this term inconsistently.  I have cleaned it up so
that no initial capital is used.

(From yocto-docs rev: 7dea2c5ef067d81b8350cd54ba4082c35d7077b1)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2014-04-21 08:33:36 -07:00 committed by Richard Purdie
parent 3f0a863ad0
commit 601d5f1af0
1 changed files with 12 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -2082,14 +2082,15 @@
and
<ulink url='&YOCTO_DOCS_REF_URL;#var-INITSCRIPT_PARAMS'><filename>INITSCRIPT_PARAMS</filename></ulink>
variables within your recipe.</para></listitem>
<listitem><para><emphasis>Systemd:</emphasis>
Systemd was designed to replace SysVinit and to provide
<listitem><para><emphasis>systemd:</emphasis>
System Management Daemon (systemd) was designed to
replace SysVinit and to provide
enhanced management of services.
For more information on Systemd, see the Systemd
For more information on systemd, see the systemd
homepage at
<ulink url='http://freedesktop.org/wiki/Software/systemd/'></ulink>.
</para>
<para>To enable a service using Systemd, your recipe
<para>To enable a service using systemd, your recipe
needs to inherit the
<ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-systemd'><filename>systemd</filename></ulink>
class.
@ -5340,7 +5341,7 @@
<para>
By default, the Yocto Project uses SysVinit as the initialization
manager.
However, support also exists for Systemd,
However, support also exists for systemd,
which is a full replacement for init with
parallel starting of services, reduced shell overhead and other
features that are used by many distributions.
@ -5349,12 +5350,12 @@
<para>
If you want to use SysVinit, you do
not have to do anything.
But, if you want to use Systemd, you must
But, if you want to use systemd, you must
take some steps as described in the following sections.
</para>
<section id='using-systemd-exclusively'>
<title>Using Systemd Exclusively</title>
<title>Using systemd Exclusively</title>
<para>
Set the these variables in your distribution configuration
@ -5387,7 +5388,7 @@
</section>
<section id='using-systemd-for-the-main-image-and-using-sysvinit-for-the-rescue-image'>
<title>Using Systemd for the Main Image and Using SysVinit for the Rescue Image</title>
<title>Using systemd for the Main Image and Using SysVinit for the Rescue Image</title>
<para>
Set the these variables in your distribution configuration
@ -5398,11 +5399,11 @@
</literallayout>
Doing so causes your main image to use the
<filename>packagegroup-core-boot.bb</filename> recipe and
Systemd.
systemd.
The rescue/minimal image cannot use this package group.
However, it can install SysVinit
and the appropriate packages will have support for both
Systemd and SysVinit.
systemd and SysVinit.
</para>
</section>
</section>
@ -6014,7 +6015,7 @@
A test name maps directly to a Python module.
Each test module may contain a number of individual tests.
Tests are usually grouped together by the area
tested (e.g tests for Systemd reside in
tested (e.g tests for systemd reside in
<filename>meta/lib/oeqa/runtime/systemd.py</filename>).
</para>