From owner-doc-jp@jp.freebsd.org  Thu Mar  9 01:07:16 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id BAA74675;
	Thu, 9 Mar 2000 01:07:16 +0900 (JST)
	(envelope-from owner-doc-jp@jp.FreeBSD.org)
Received: from sv01.geocities.co.jp (sv01.geocities.co.jp [210.153.89.155])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id BAA74670
	for <doc-jp@jp.freebsd.org>; Thu, 9 Mar 2000 01:07:15 +0900 (JST)
	(envelope-from hrs@geocities.co.jp)
Received: from mail.geocities.co.jp (mail.geocities.co.jp [210.153.89.137]) by sv01.geocities.co.jp (8.9.3+3.2W/3.7W) with ESMTP id BAA00417 for <doc-jp@jp.freebsd.org>; Thu, 9 Mar 2000 01:07:15 +0900 (JST)
Received: from mail.hrs.jp (sutnmax2-ppp07.ed.noda.sut.ac.jp [133.31.173.77]) by mail.geocities.co.jp (1.3G-GeocitiesJ-3.3) with ESMTP id BAA22458 for <doc-jp@jp.freebsd.org>; Thu, 9 Mar 2000 01:07:11 +0900 (JST)
Message-Id: <200003081607.BAA22458@mail.geocities.co.jp>
Received: from localhost (alph.hrs.jp [192.168.0.10])
	by mail.hrs.jp (8.9.3/3.7W/DomainMaster) with ESMTP id AAA20607
	for <doc-jp@jp.freebsd.org>; Thu, 9 Mar 2000 00:24:33 +0900 (JST)
	(envelope-from hrs@hrs.jp)
To: doc-jp@jp.freebsd.org
X-Mailer: Mew version 1.94 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Date: Thu, 09 Mar 2000 00:24:32 +0900
From: Hiroki Sato <hrs@geocities.co.jp>
X-Dispatcher: imput version 990905(IM130)
Lines: 97
Reply-To: doc-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+990727
X-Sequence: doc-jp 7144
Subject: [doc-jp 7144] books/handbook/internals/chapter.sgml #5
Errors-To: owner-doc-jp@jp.freebsd.org
Sender: owner-doc-jp@jp.freebsd.org
X-Originator: hrs@geocities.co.jp

$B:4F#!wEl5~M}2JBg3X$G$9!#(B

$B$5$i$KB3$-$G$9!#(B

(books/handbook/internals/chapter.sgml 1.15 -> 1.16 #5)
  
    <sect2 id="boot-kernel">
      <title>Kernel interaction during boot</title>
      
      <para>Once the kernel is loaded by either <link
	  linkend="boot-loader">loader</link> (as usual) or <link
	  linkend="boot-boot2">boot2</link> (bypassing the loader), it
	examines its boot flags, if any, and adjusts its behaviour as
	necessary.</para>

      <sect3 id="boot-kernel-bootflags">
	<title>Kernel bootflags</title>

	<para>Here are the more common boot flags:</para>

	<variablelist id="boot-kernel-bootflags-list">
	  <varlistentry>
	    <term><option>-a</option></term>

	    <listitem>
	      <para>during kernel initialization, ask for the device
		to mount as as the root file system.</para>
	    </listitem>
	  </varlistentry>

	  <varlistentry>
	    <term><option>-C</option></term>

	    <listitem>
	      <para>boot from CDROM.</para>
	    </listitem>
	  </varlistentry>

	  <varlistentry>
	    <term><option>-c</option></term>

	    <listitem>
	      <para>run UserConfig, the boot-time kernel
		configurator</para>
	    </listitem>
	  </varlistentry>

	  <varlistentry>
	    <term><option>-s</option></term>

	    <listitem>
	      <para>boot into single-user mode</para>
	    </listitem>
	  </varlistentry>

	  <varlistentry>
	    <term><option>-v</option></term>

	    <listitem>
	      <para>be more verbose during kernel startup</para>
	    </listitem>
	  </varlistentry>
	</variablelist>

	<note>
	  <para>There are other boot flags, read &man.boot.8; for more
	    information on them.</para>
	</note>
      </sect3>

  <!--    <sect3 id="boot-kernel-userconfig">
	<title>UserConfig: The boot-time kernel configurator</title>
	
	<para> </para>
      </sect3> -->
    </sect2>
  
    <sect2 id="boot-init">
      <title>Init: Process control initialization</title>
	  
      <para>Onqe the kernel has finished booting, it passes control to
	the usqr process <command>init</command>, which is located at
	<filename>/sbin/init</filename>, or the program path specified
	in the <envar>init_path</envar> variable in
	<command>loader</command>.</para>

      <sect3 id="boot-autoreboot">
	<title>Automatic reboot sequence</title>
	
	<para>The automatic reboot sequence makes sure that the
	  filesystems available on the system are consistent.  If they
	  are not, and <command>fsck</command> can not fix the
	  inconsistencies, <command>init</command> drops the system
	  into <link linkend="boot-singleuser">single-user mode</link>
	  for the system administrator to take care of the problems
	  directly.</para>
      </sect3>
