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

dev-manual: First draft of new init manager section. 

I created a first draft of a section titled "Selecting an
Initialization Manager."  The text was based on information
from Ross burton.  This is for the "systemd" support that
is new for 1.4.  There is a lot of work left on the section.
This is the first draft.

Reported-by: Ross Burton <ross.burton@intel.com>
(From yocto-docs rev: ad358b96834879abe8a10d89e77453e30799ac0a)

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 2013-03-27 18:23:25 -07:00 committed by Richard Purdie
parent 072b38a5c2
commit 4a4d342264
1 changed files with 91 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -3074,6 +3074,61 @@
</para>
</section>
<section id="selecting-an-initialization-manager">
<title>Selecting an Initialization Manager</title>
<para>
By default, the Yocto Project uses
<filename>SysVinit</filename> as the initialization manager.
However, support also exists for <filename>systemd</filename>.
If you want to use <filename>SysVinit</filename>, you do
not have to do anything.
But, if you want to use <filename>systemd</filename>, you must
take some steps as described in the following sections.
</para>
<section id='using-systemd-exclusively'>
<title>Using systemd Exclusively</title>
<para>
Set the following variables in your
<filename>local.conf</filename> file as follows:
<literallayout class='monospaced'>
DISTRO_FEATURES = "systemd"
VIRTUAL-RUNTIME_init-manager = "systemd"
</literallayout>
You can save some disk space by adding
<filename>sysvinit</filename> to the distribution features
considered for backfill as follows:
<literallayout class='monospaced'>
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
</literallayout>
Doing so removes any redundant <filename>sysvinit</filename>
scripts.
</para>
</section>
<section id='use-systemd-for-the-main-image-and-use-sysvinit-for-the-rescue-image'>
<title>Use systemd for the Main Image and Use SysVinit for the Rescue Image</title>
<para>
Set the following variables in your
<filename>local.conf</filename> file as follows:
<literallayout class='monospaced'>
DISTRO_FEATURES = "systemd"
VIRTUAL-RUNTIME_init-manager = "systemd"
</literallayout>
Doing so causes your main image to use
<filename>packagegroup-core-boot</filename> and
<filename>systemd</filename>.
The rescue/minimal image cannot use this group.
However, it can install <filename>sysvinit</filename>
and the appropriate packages with have both
<filename>systemd</filename> and <filename>sysvinit</filename>.
</para>
</section>
</section>
<section id='excluding-recipes-from-the-build'>
<title>Excluding Recipes From the Build</title>