<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
  <!ENTITY % general-entities SYSTEM "../general.ent">
  %general-entities;
]>

<sect1 id="ch-scripts-introduction" revision="sysv">
  <?dbhtml filename="introduction.html"?>

  <title>概述</title>

    <!--para>Booting a Linux system involves several tasks.  The process must
    mount both virtual and real file systems, initialize devices, activate swap,
    check file systems for integrity, mount any swap partitions or files, set
    the system clock, bring up networking, start any daemons required by the
    system, and accomplish any other custom tasks needed by the user.  This
    process must be organized to ensure the tasks are performed in the correct
    order but, at the same time, be executed as fast as possible.</para-->
    <para>引导 Linux 系统需要完成若干任务。
		引导过程必须挂载虚拟和真实文件系统、初始化设备、启用交换、
		检查文件系统完整性、挂载所有交换分区或文件、设定系统时钟、
		启用网络、启动系统需要的守护进程，并完成用户自定义的其他工作。
		引导过程必须被组织好，以保证这些任务以正确顺序进行，
		并以尽量快的速度完成。</para>

<!--    <para>In the packages that were installed in Chapter&nbsp;6, there were two
    different boot systems installed.  LFS provides the ability to easily
    select which system the user wants to use and to compare and contrast the
    two systems by actually running each system on the local computer.  The
    advantages and disadvantages of these systems is presented below.</para>-->

  <sect2 id='sysv-desc'>
    <title>System V</title>

    <!--para>System V is the classic boot process that has been used in Unix and
    Unix-like systems such as Linux since about 1983.  It consists of a small
    program, <command>init</command>, that sets up basic programs such as
    <command>login</command> (via getty) and runs a script.  This script,
    usually named <command>rc</command>,  controls the execution of a set of
    additional scripts that perform the tasks required to initialize the
    system.</para>

    <para>The <command>init</command> program is controlled by the 
    <filename>/etc/inittab</filename> file and is organized into run levels that
    can be run by the user:</para-->
    <para>System V 是自 1983 年以来就在 Unix 和 Linux 等类 Unix
		系统中被广泛应用的经典引导过程。它包含一个小程序
		<command>init</command>，该程序设定 <command>login</command>
		（通过 getty）并运行一个脚本。该脚本一般被命名为
		<command>rc</command>，控制一组附加脚本的运行，
		这些附加脚本完成初始化系统需要的各项工作。</para>
	<para><command>init</command> 程序受到 <filename>/etc/inittab</filename>
		文件的控制，被组织为用户可以选择的系统运行级别：</para>

<literallayout>
0 &mdash; 停止运行
1 &mdash; 单用户模式
2 &mdash; 多用户模式，没有网络
3 &mdash; 完整的多用户模式
4 &mdash; 用户自定义模式
5 &mdash; 拥有显示管理器的完整多用户模式
6 &mdash; 重启系统
</literallayout>

    <para>通常的默认运行级别是 3 或 5。</para>

    <bridgehead renderas="sect3">优点</bridgehead>

    <itemizedlist>
      <listitem>
          <para>完备的，已经被详细理解的系统。</para>
      </listitem>

      <listitem>
          <para>容易定制。</para>
      </listitem>

    </itemizedlist>


    <bridgehead renderas="sect3">缺点</bridgehead>

    <itemizedlist>
      <listitem>
          <!--para>Slower to boot.  A medium speed base LFS system 
          takes 8-12 seconds where the boot time is measured from the 
          first kernel message to the login prompt.  Network 
          connectivity is typically established about 2 seconds 
          after the login prompt.</para-->
          <para>引导速度较慢。一个中等速度的基本 LFS
			  系统从第一个内核消息开始，到出现登录提示符为止，
			  需要 8-12 秒的引导时间，之后还需要约 2 秒启动网络连接。
		  </para>
      </listitem>

      <listitem>
          <!--para>Serial processing of boot tasks. This is related to the previous
          point.  A delay in any process such as a file system check, will
          delay the entire boot process.</para-->
	      <para>串行执行引导任务，这与前一项缺点相关。
			  引导过程中的延迟（如文件系统检查）会延迟整个引导过程。</para>
      </listitem>

      <listitem>
          <para>不支持控制组（cgroups）、每用户公平共享调度等高级特性。
          </para>
      </listitem>

      <listitem>
          <para>添加脚本时，需要手动决定它在引导过程中的次序。</para>
      </listitem>

    </itemizedlist>

  </sect2>
<!--
  <sect2 id='sysd-desc'>
    <title>Systemd</title>

    <para>Systemd is a group of interconnected programs that handles system and
    individual process requests.  It provides a dependency system between
    various entities called "units".  It automatically addresses dependencies
    between units and can execute several startup tasks in parallel.  It
    provides login, inetd, logging, time, and networking services. </para>

    <bridgehead renderas="sect3">Advantages</bridgehead>

    <itemizedlist>
      <listitem>
          <para>Used on many established distributions by default.</para>
      </listitem>

      <listitem>
          <para>There is extensive documentation. 
          See <ulink url="http://www.freedesktop.org/wiki/Software/systemd/"/>.</para>
      </listitem>

      <listitem>
          <para>Parallel execution of boot processes. A medium speed
          base LFS system takes 6-10 seconds from kernel start to a 
          login prompt.  Network connectivity is typically established 
          about 2 seconds after the login prompt.  More complex startup
          procedures may show a greater speedup when compared to System V.</para>
      </listitem>

      <listitem>
          <para>Implements advanced features such as control groups to 
          manage related processes.</para>
      </listitem>

      <listitem>
          <para>Maintains backward compatibility with System V programs 
          and scripts.</para>
      </listitem>
    </itemizedlist>

    <bridgehead renderas="sect3">Disadvantages</bridgehead>

    <itemizedlist>
      <listitem>
          <para>There is a substantial learning curve.</para>
      </listitem>

      <listitem>
          <para>Some advanced features such as dbus or cgroups cannot be
          disabled if they are not otherwise needed.</para>
      </listitem>

      <listitem>
          <para>Although implemented as several executable programs
          the user cannot choose to implement only the portions desired.</para>
      </listitem>

      <listitem>
          <para>Due to the nature of using compiled programs, systemd is
          more difficult to debug.</para>
      </listitem>

      <listitem>
          <para>Logging is done in a binary format.  Extra tools must
          be used to process logs or additional processes must be implemented
          to duplicate traditional logging programs.</para>
      </listitem>

    </itemizedlist>

  </sect2>
-->
<!--
  <sect2 id='sysv'>
    <title>Selecting a Boot Method</title>

    <para>Selecting a boot method in LFS is relatively easy.  
    Both systems are installed side-by-side.  The only task needed is to
    ensure the files that are needed by the system have the correct names.
    The following scripts do that.</para>

<screen><userinput remap="install">cat &gt; /usr/sbin/set-systemd &lt;&lt; "EOF"
#! /bin/bash

ln -svfn init-systemd   /sbin/init
ln -svfn init.d-systemd /etc/init.d

for tool in halt poweroff reboot runlevel shutdown telinit; do
  ln -sfvn  ${tool}-systemd   /sbin/${tool}
  ln -svfn  ${tool}-systemd.8 /usr/share/man/man8/${tool}.8
done

echo "Now reboot with /sbin/reboot-sysv"
EOF

chmod 0744 /usr/sbin/set-systemd

cat &gt; /usr/sbin/set-sysv &lt;&lt; "EOF"
#! /bin/bash

ln -sfvn init-sysv    /sbin/init
ln -svfn init.d-sysv  /etc/init.d

for tool in halt poweroff reboot runlevel shutdown telinit; do
  ln -sfvn  ${tool}-sysv   /sbin/${tool}
  ln -svfn  ${tool}-sysv.8 /usr/share/man/man8/${tool}.8
done

echo "Now reboot with /sbin/reboot-systemd"
EOF

chmod 0744 /usr/sbin/set-sysv</userinput></screen>

  <note><para>The comment about the correct command to reboot in the 
  above scripts is correct.  The reboot command for the current boot
  system must be used after the script changes the default reboot command.
  </para></note>

  <para>Now set the desired boot system.  The default is System V:</para>

<screen><userinput remap="install">/usr/sbin/set-sysv</userinput></screen>

  <para>Changing the boot system can be done at any time by running the 
  appropriate script above and rebooting.</para>

  </sect2>
-->
</sect1>
