(split) LDP v3.30, v3.31 の定型的な変更内容を反映。

[linuxjm/LDP_man-pages.git] / draft / man7 / boot.7

.\" Written by Oron Peled <oron@actcom.co.il>.
.\" May be distributed subject to the GPL.
.\"
.\" I tried to be as much generic in the description as possible:
.\" - General boot sequence is applicable to almost any
.\" OS/Machine (DOS/PC, Linux/PC, Solaris/SPARC, CMS/S390)
.\" - kernel and init(8) is applicable to almost any UNIX/Linux
.\" - boot scripts are applicable to SYSV-R4 based UNIX/Linux
.\"
.\" Modified 2004-11-03 patch from Martin Schulze <joey@infodrom.org>
.\"
.\" Japanese Version Copyright (c) 2002 NAKANO Takeo all rights reserved.
.\" Translated 2002-08-07, NAKANO Takeo <nakano@apm.seikei.ac.jp>
.\" Updated 2005-02-21, Akihiro MOTOKI <amotoki@dd.iij4u.or.jp>
.\"
.TH BOOT 7 2010-09-19 "Linux" "Linux Programmer's Manual"
.\"O .SH NAME
.\"O boot-scripts \- General description of boot sequence
.SH ̾Á°
boot-scripts \- ¥Ö¡¼¥È¥·¡¼¥±¥ó¥¹¤Î°ìÈÌŪ¤Ê²òÀâ
.\"O .SH DESCRIPTION
.SH ÀâÌÀ
.\"O .LP
.\"O The boot sequence varies in details among systems
.\"O but can be roughly divided to the following steps:
.\"O (i) hardware boot, (ii) OS loader,
.\"O (iii) kernel startup, (iv) init and inittab,
.\"O (v) boot scripts.
.\"O We will describe each of these in more detail below.
ºÙ¤«¤¤¤È¤³¤í¤Ï¥·¥¹¥Æ¥à¤Ë¤è¤Ã¤Æ°Û¤Ê¤ë¤¬¡¢Âç¤Þ¤«¤Ë¸À¤¦¤È¡¢
¥Ö¡¼¥È¥·¡¼¥±¥ó¥¹¤Ï°Ê²¼¤ÎÃʳ¬¤Ëʬ¤±¤é¤ì¤ë:
(1) ¥Ï¡¼¥É¥¦¥§¥¢¤Î¥Ö¡¼¥È (2) OS ¥í¡¼¥À¡¼
(3) ¥«¡¼¥Í¥ë¤Îµ¯Æ° (4) init ¤È inittab
(5) ¥Ö¡¼¥È¥¹¥¯¥ê¥×¥È
.\"O .SS "Hardware-boot"
.SS ¥Ï¡¼¥É¥¦¥§¥¢¤Î¥Ö¡¼¥È
.\"O After power-on or hard reset, control is given
.\"O to a program stored on read-only memory (normally
.\"O PROM).
.\"O In PC we usually call this program the \fBBIOS\fR.
ÅŸ»ÅêÆþ¤ä¥Ï¡¼¥É¥ê¥»¥Ã¥È¤¬¹Ô¤ï¤ì¤ë¤È¡¢
ROM (Ä̾ï¤Ï PROM) ¤ËÊݸ¤µ¤ì¤Æ¤¤¤ë¥×¥í¥°¥é¥à¤ËÀ©¸æ¤¬ÅϤµ¤ì¤ë¡£
PC ¤Ç¤Ï¤³¤Î¥×¥í¥°¥é¥à¤ÏÄ̾ï \fBBIOS\fR ¤È¸Æ¤Ð¤ì¤ë¡£

.\"O This program normally makes a basic self-test of the
.\"O machine and accesses nonvolatile memory to read
.\"O further parameters.
.\"O This memory in the PC is
.\"O battery-backed CMOS memory, so most people
.\"O refer to it as the \fBCMOS\fR, although outside
.\"O of the PC world, it is usually called \fBnvram\fR
.\"O (nonvolatile ram).
¤Õ¤Ä¤¦¤³¤Î¥×¥í¥°¥é¥à¤Ï¡¢¤Þ¤º¥Þ¥·¥ó¤Î´ðËÜŪ¤Ê¼«¸Ê¿ÇÃǤò¹Ô¤¤¡¢
¤½¤·¤ÆÉÔ´øȯÀ­¥á¥â¥ê¤Ë¥¢¥¯¥»¥¹¤·¤Æ³Æ¼ï¤Î¥Ñ¥é¥á¡¼¥¿¤òÆɤ߹þ¤à¡£
PC ¤Ç¤Ï¡¢¤³¤Î¥á¥â¥ê¤ÏÅÅÃӤˤè¤Ã¤Æ¥Ð¥Ã¥¯¥¢¥Ã¥×¤µ¤ì¤Æ¤¤¤ë CMOS ¥á¥â¥ê¤Ç¤¢¤ë¡£
¤½¤Î¤¿¤á \fBCMOS\fR ¤È¸Æ¤Ð¤ì¤ë¤³¤È¤¬Â¿¤¤¡£
¤·¤«¤· PC °Ê³°¤ÎÀ¤³¦¤Ç¤Ï¡¢Ä̾ï \fBnvram\fR
(nonvolatile ram) ¤È¸Æ¤Ð¤ì¤Æ¤¤¤ë¡£

.\"O The parameters stored in the nvram vary between
.\"O systems, but as a minimum, the hardware boot program
.\"O should know what is the boot device, or which devices
.\"O to probe as possible boot devices.
nvram ¤ËÊݸ¤µ¤ì¤Æ¤¤¤ë¥Ñ¥é¥á¡¼¥¿¤Ï¥·¥¹¥Æ¥à¤Ë¤è¤Ã¤Æ°Û¤Ê¤ë¡£
¤·¤«¤·¡¢¥Ï¡¼¥É¥¦¥§¥¢¥Ö¡¼¥È¥×¥í¥°¥é¥à¤Ï¡¢¾¯¤Ê¤¯¤È¤â¡¢
¥Ö¡¼¥È¥Ç¥Ð¥¤¥¹¤¬¤É¤ì¤Ç¤¢¤ë¤«¡¢¤â¤·¤¯¤Ï
¥Ö¡¼¥È¥Ç¥Ð¥¤¥¹¤È¤·¤Æõº÷¤¹¤ë¥Ç¥Ð¥¤¥¹¤¬¤É¤ì¤Ç¤¢¤ë¤«¤ò
ÃΤäƤ¤¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£

.\"O Then the hardware boot stage accesses the boot device,
.\"O loads the OS Loader, which is located on a fixed position
.\"O on the boot device, and transfers control to it.
¥Ï¡¼¥É¥¦¥§¥¢¥Ö¡¼¥È¤Î¥·¡¼¥±¥ó¥¹¤Ï¡¢¼¡¤Ë¥Ö¡¼¥È¥Ç¥Ð¥¤¥¹¤Ë¥¢¥¯¥»¥¹¤·¡¢
¥Ö¡¼¥È¥Ç¥Ð¥¤¥¹¤Î¤¢¤é¤«¤¸¤á·è¤Þ¤Ã¤¿¾ì½ê¤ËÃÖ¤«¤ì¤Æ¤¤¤ë
OS ¥í¡¼¥À¡¼¤ò¥í¡¼¥É¤·¡¢À©¸æ¤òÅϤ¹¡£
.TP
.\"O Note:
.\"O We do not cover here booting from network.
.\"O Those who want
.\"O to investigate this subject may want to research:
.\"O DHCP, TFTP, PXE, Etherboot.
Ãí°Õ:
¤³¤³¤Ç¤Ï¥Í¥Ã¥È¥ï¡¼¥¯¥Ö¡¼¥È¤Ë¤Ä¤¤¤Æ¤Ï¿¨¤ì¤Ê¤¤¡£
¤³¤ÎÏÃÂê¤Ë¤Ä¤¤¤ÆÄ´ºº¤·¤¿¤¤ÆɼԤϡ¢
DHCP, TFTP, PXE, Etherboot Åù¤Ë¤Ä¤¤¤ÆÄ´¤Ù¤Æ¤ß¤ë¤È¤è¤¤¡£
.\"O .SS "OS Loader"
.SS OS ¥í¡¼¥À¡¼
.\"O In PC, the OS Loader is located in the first sector
.\"O of the boot device \- this is the \fBMBR\fR
.\"O (Master Boot Record).
PC ¤Ç¤Ï¡¢OS ¥í¡¼¥À¡¼¤Ï¥Ö¡¼¥È¥Ç¥Ð¥¤¥¹¤ÎÀèƬ¥»¥¯¥¿¤ËÃÖ¤«¤ì¤ë¡£
¤³¤ì¤Ï \fBMBR\fR (Master Boot Record) ¤È¸Æ¤Ð¤ì¤ë¡£

.\"O In most systems, this primary loader is very
.\"O limited due to various constraints.
.\"O Even on non-PC systems
.\"O there are some limitations to the size and complexity
.\"O of this loader, but the size limitation of the PC MBR
.\"O (512 bytes including the partition table) makes it
.\"O almost impossible to squeeze a full OS Loader into it.
ÍÍ¡¹¤ÊÀ©Ìó¤Î¤¿¤á¡¢
¤Û¤È¤ó¤É¤Î¥·¥¹¥Æ¥à¤ÇÂè°ì¥í¡¼¥À¡¼¤ÏÈó¾ï¤Ë´Êñ¤Êµ¡Ç½¤·¤«»ý¤Ã¤Æ¤¤¤Ê¤¤¡£
PC °Ê³°¤Î¥·¥¹¥Æ¥à¤Ç¤â¡¢
¥µ¥¤¥º¤ÎÀ©¸Â¤ä¥í¡¼¥À¡¼¤Îµ¡Ç½¤Ê¤É¤Ë¤¢¤ëÄøÅÙ¤ÎÀ©¸Â¤Ï¸ºß¤¹¤ë¡£
¤·¤«¤·¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥Æ¡¼¥Ö¥ë¤ò´Þ¤á¤Æ 512 ¥Ð¥¤¥È¤È¤¤¤¦
PC ¤Î MBR ¤Ç¤Ï¡¢OS ¥í¡¼¥À¡¼¤ÎÁ´µ¡Ç½¤ò¤³¤³¤Ë²¡¤·¹þ¤à¤Î¤Ï¤Þ¤ºÉÔ²Äǽ¤À¡£

.\"O Therefore, most operating systems make the primary loader
.\"O call a secondary OS loader which may be located on
.\"O a specified disk partition.
¤·¤¿¤¬¤Ã¤ÆÂçÄñ¤Î OS ¤Ç¤Ï¡¢Âè°ì¥í¡¼¥À¡¼¤ÏÂèÆó¥í¡¼¥À¡¼¤ò¸Æ¤Ö¤è¤¦¤Ë¤Ê¤Ã¤Æ¤ª¤ê¡¢
¸å¼Ô¤Ï¤¢¤é¤«¤¸¤á»ØÄꤵ¤ì¤¿¥Ç¥£¥¹¥¯¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ËÃÖ¤±¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤ë¡£

.\"O In Linux the OS loader is normally
.\"O .BR lilo (8)
.\"O or
.\"O .BR grub (8).
.\"O Both of them may install either as secondary loaders
.\"O (where the DOS installed MBR points to them), or
.\"O as a two part loader where they provide special MBR
.\"O containing the bootstrap code to load the second part
.\"O of the loader from the root partition.
Linux ¤Ë¤ª¤±¤ë OS ¥í¡¼¥À¡¼¤Ï¡¢¤Õ¤Ä¤¦
.BR lilo (8)
¤«
.BR grub (8)
¤Ç¤¢¤ë¡£Î¾¼Ô¤È¤âÂèÆó¥í¡¼¥À¡¼¤È¤·¤Æ¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤³¤È¤â¤Ç¤­
(¤³¤Î¾ì¹ç DOS ¤¬¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿ MBR ¤¬¤³¤ì¤é¤ò»Ø¤¹¤è¤¦¤Ë¤¹¤ë)¡¢
¤Þ¤¿Âè°ì¡¦ÂèÆó¥í¡¼¥À¡¼¤ÎξÊý¤È¤·¤Æ¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤³¤È¤â¤Ç¤­¤ë¡£
¸å¼Ô¤Î¾ì¹ç¸þ¤±¤Ë¡¢Î¾¼Ô¤ÏÆÃÊÌ¤Ê MBR ¥¤¥á¡¼¥¸¤òÄ󶡤·¤Æ¤¤¤ë¡£
¤³¤ì¤Ë¤ÏÂèÆó¥í¡¼¥À¡¼¤ò¥ë¡¼¥È¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤«¤é¥í¡¼¥É¤¹¤ë¤è¤¦¤Ê
¥Ö¡¼¥È¥¹¥È¥é¥Ã¥×¥³¡¼¥É¤¬´Þ¤Þ¤ì¤Æ¤¤¤ë¡£

.\"O The main job of the OS Loader is to locate the kernel
.\"O on the disk, load it and run it.
.\"O Most OS loaders allow
.\"O interactive use, to enable specification of alternative
.\"O kernel (maybe a backup in case the last compiled one
.\"O isn't functioning) and to pass optional parameters
.\"O to the kernel.
OS ¥í¡¼¥À¡¼¤Î¼ç¤Ê»Å»ö¤Ï¡¢¥«¡¼¥Í¥ë¤Î¥Ç¥£¥¹¥¯¾å¤Î°ÌÃÖ¤òÆÃÄꤷ¡¢
¥í¡¼¥É¤·¤Æµ¯Æ°¤¹¤ë¤³¤È¤Ç¤¢¤ë¡£¤Û¤È¤ó¤É¤Î OS ¥í¡¼¥À¡¼¤Ï¡¢
ÂÐÏå⡼¥É¤Ç»ÈÍѤ¹¤ë¤³¤È¤â¤Ç¤­¡¢ÄɲäΥѥé¥á¡¼¥¿¤ò¥«¡¼¥Í¥ë¤ËÅϤ·¤¿¤ê¡¢
¥Ç¥Õ¥©¥ë¥È¤È¤ÏÊ̤Υ«¡¼¥Í¥ë¤ò»ØÄꤷ¤¿¤ê¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë
(Î㤨¤Ð¡¢ºÇ¸å¤Ë¥³¥ó¥Ñ¥¤¥ë¤·¤¿¥«¡¼¥Í¥ë¤¬µ¡Ç½¤·¤Ê¤«¤Ã¤¿»þ¤Ë
¥Ð¥Ã¥¯¥¢¥Ã¥×¤Î¥«¡¼¥Í¥ë¤ò»ØÄꤷ¤Æµ¯Æ°¤¹¤ë¤È¤¤¤Ã¤¿¤³¤È¤¬¤Ç¤­¤ë)¡£
.\"O .SS "Kernel Startup"
.SS ¥«¡¼¥Í¥ë¤Îµ¯Æ°
.\"O When the kernel is loaded, it initializes the devices (via
.\"O their drivers), starts the swapper (it is a "kernel process",
.\"O called kswapd in modern Linux kernels), and mounts the root
.\"O file system (/).
¥«¡¼¥Í¥ë¤Ï¥í¡¼¥É¤µ¤ì¤ë¤È¡¢¥Ç¥Ð¥¤¥¹¤ò (¥É¥é¥¤¥Ð¤Ë¤è¤Ã¤Æ)
½é´ü²½¤·¡¢¥¹¥ï¥Ã¥Ñ¤òµ¯Æ°¤· (ºÇ¶á¤Î Linux ¥«¡¼¥Í¥ë¤Ç¤Ï¡¢
¥¹¥ï¥Ã¥Ñ¤Ï kswapd ¤È¤¤¤¦¡Ö¥«¡¼¥Í¥ë¥×¥í¥»¥¹¡×¤Ë¤Ê¤ë)¡¢
¥ë¡¼¥È¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à (/) ¤ò¥Þ¥¦¥ó¥È¤¹¤ë¡£

.\"O Some of the parameters that may be passed to the kernel
.\"O relate to these activities (e.g: You can override the
.\"O default root file system).
.\"O For further information
.\"O on Linux kernel parameters read
.\"O .BR bootparam (7).
¥«¡¼¥Í¥ë¤ËÅϤ¹¤³¤È¤Î¤Ç¤­¤ë¥Ñ¥é¥á¡¼¥¿¤Î¤¤¤¯¤Ä¤«¤Ï¡¢
¤³¤ì¤é¤ÎÆ°ºî¤Ë´Ø·¸¤¹¤ë¡£
(Î㤨¤Ð¥Ç¥Õ¥©¥ë¥È¤Î¥ë¡¼¥È¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òÊѹ¹¤·¤¿¤ê¤Ç¤­¤ë)¡£
Linux ¥«¡¼¥Í¥ë¥Ñ¥é¥á¡¼¥¿¤Ë´Ø¤¹¤ë¤è¤ê¾Ü¤·¤¤¾ðÊó¤Ï
.BR bootparam (7)
¤òÆɤó¤Ç¤Û¤·¤¤¡£

.\"O Only then the kernel creates the first (user land)
.\"O process which is numbered 1.
.\"O This process executes the
.\"O program
.\"O .IR /sbin/init ,
.\"O passing any parameters that weren't handled by the kernel already.
¤³¤ì¤é¤¬ºÑ¤ó¤Ç¤Ï¤¸¤á¤Æ¡¢
¥«¡¼¥Í¥ë¤ÏºÇ½é¤Î (¥æ¡¼¥¶¥é¥ó¥É¤Î) ¥×¥í¥»¥¹¤òÀ¸À®¤·¡¢
ÈÖ¹æ 1 ¤òÍ¿¤¨¤ë¡£¤³¤Î¥×¥í¥»¥¹¤Ï
.I /sbin/init
¥×¥í¥°¥é¥à¤ò¼Â¹Ô¤¹¤ë¡£
¥«¡¼¥Í¥ë¤Ë¤è¤Ã¤Æ²ò¼á¤µ¤ì¤Æ¤¤¤Ê¤¤¥Ñ¥é¥á¡¼¥¿¤Ï¤¹¤Ù¤Æ
.I /sbin/init
¤ËÅϤµ¤ì¤ë¡£
.\"O .SS "init and inittab"
.SS init ¤È inittab
.\"O When init starts it reads
.\"O .I /etc/inittab
.\"O for further instructions.
.\"O This file defines what should be run in different \fIrun-levels\fR.
init ¤Ï¡¢µ¯Æ°¤¹¤ë¤È¤Þ¤º
.I /etc/inittab
¤òÆɤߡ¢¤½¤Î¸å¤Î¹ÔÆ°¤Ë´Ø¤¹¤ë¾ðÊó¤òÆÀ¤ë¡£
¤³¤Î¥Õ¥¡¥¤¥ë¤Ï
.I ¥é¥ó¥ì¥Ù¥ë
¤Ë¤è¤Ã¤Æ¤É¤Î¤è¤¦¤ÊÆ°ºî¤ò¹Ô¤¦¤Ù¤­¤Ç¤¢¤ë¤«¤òÄêµÁ¤¹¤ë¡£

.\"O This gives the system administrator an easy management scheme, where
.\"O each run-level is associated with a set of services (e.g:
.\"O \fBS\fR is \fIsingle-user\fR, on \fB2\fR most network
.\"O services start, etc.).
.\"O The administrator may change the current
.\"O run-level via
.\"O .BR init (8)
.\"O and query the current run-level via
.\"O .BR runlevel (8).
¤³¤ì¤Ë¤è¤Ã¤Æ¥·¥¹¥Æ¥à´ÉÍý¼Ô¤Î´ÉÍý¤¬³Ú¤Ë¤Ê¤ë¡£
³Æ\fI¥é¥ó¥ì¥Ù¥ë\fR¤ÏÄ󶡤¹¤ë¥µ¡¼¥Ó¥¹¤Î½¸¹ç¤ËÂбþ¤¹¤ë
(Î㤨¤Ð \fBS\fR ¤Ï \fI¥·¥ó¥°¥ë¥æ¡¼¥¶\fR¡¢
\fB2\fR ¤Ç¤ÏÂçÄñ¤Î¥Í¥Ã¥È¥ï¡¼¥¯¥µ¡¼¥Ó¥¹¤òµ¯Æ°¤¹¤ë¡¢¤Ê¤É)¡£
¥·¥¹¥Æ¥à´ÉÍý¼Ô¤Ï¡¢
.BR init (8)
¤òÍѤ¤¤Æ¸½ºß¤Î¥é¥ó¥ì¥Ù¥ë¤òÊѹ¹¤Ç¤­¡¢
.BR runlevel (8)
¤Ë¤è¤Ã¤Æ¸½ºß¤Î¥é¥ó¥ì¥Ù¥ë¤ò³Îǧ¤Ç¤­¤ë¡£

.\"O However, since it is not convenient to manage individual services
.\"O by editing this file, inittab only bootstraps a set of scripts
.\"O that actually start/stop the individual services.
¤·¤«¤·¡¢¤³¤Î¥Õ¥¡¥¤¥ë¤òÊÔ½¸¤·¤Æ¸Ä¡¹¤Î¥µ¡¼¥Ó¥¹¤ò´ÉÍý¤¹¤ë¤Î¤ÏÉÔÊؤʤΤǡ¢
inittab ¤Ïñ¤Ë¥¹¥¯¥ê¥×¥È¤Î½¸¹ç¤ËÂФ¹¤ë¥Ö¡¼¥È¥¹¥È¥é¥Ã¥×¤Ë¤Ê¤Ã¤Æ¤¤¤ë¡£
¼ÂºÝ¤Î¸Ä¡¹¤Î¥µ¡¼¥Ó¥¹¤Îµ¯Æ°¤äÄä»ß¤Ï¡¢¤³¤ì¤é¤Î¥¹¥¯¥ê¥×¥È¤Ç¹Ô¤¦¡£
.\"O .SS "Boot Scripts"
.SS ¥Ö¡¼¥È¥¹¥¯¥ê¥×¥È
.\"O
.TP
.\"O Note:
.\"O The following description applies to System V release 4-based systems, which
.\"O currently covers most commercial UNIX systems (Solaris, HP-UX, Irix, Tru64)
.\"O as well as the major Linux distributions (Red Hat, Debian, Mandriva,
.\"O SUSE, Ubuntu).
.\"O Some systems (Slackware Linux, FreeBSD, OpenBSD)
.\"O have a somewhat different scheme of boot scripts.
Ãí°Õ:
°Ê²¼¤ÎÀâÌÀ¤Ï System V Release 4 ¤ò¥Ù¡¼¥¹¤È¤·¤¿¥·¥¹¥Æ¥à¤Ë´Ø¤¹¤ë¤â¤Î¤Ç¤¢¤ë¡£
¸½ºß¤ÎÂçÄñ¤Î¾¦ÍÑ UNIX ¥·¥¹¥Æ¥à (Solaris, HP-UX, Irix, Tru64) ¤ä¡¢
¥á¥¸¥ã¡¼¤Ê Linux ¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó (Red Hat, Debian, Mandriva,
SUSE, Ubuntu) ¤Ï¤³¤ì¤ò¥Ù¡¼¥¹¤Ë¤·¤¿¤â¤Î¤Ç¤¢¤ë¡£
¥·¥¹¥Æ¥à¤Ë¤è¤Ã¤Æ¤Ï¡¢¥Ö¡¼¥È¥¹¥¯¥ê¥×¥È¤Îµ¡¹½¤¬
¤¤¤¯¤é¤«°Û¤Ê¤ë¤³¤È¤â¤¢¤ë (Slackware Linux, FreeBSD, OpenBSD ¤Ê¤É)¡£
.LP
.\"O For each managed service (mail, nfs server, cron, etc.) there is
.\"O a single startup script located in a specific directory
.\"O .RI ( /etc/init.d
.\"O in most versions of Linux).
.\"O Each of these scripts accepts as a single argument
.\"O the word "start" \-\- causing it to start the service, or the word
.\"O \&"stop" \-\- causing it to stop the service.
.\"O The script may optionally
.\"O accept other "convenience" parameters (e.g: "restart", to stop and then
.\"O start, "status" do display the service status).
.\"O Running the script
.\"O without parameters displays the possible arguments.
´ÉÍý¤¹¤Ù¤­³Æ¥µ¡¼¥Ó¥¹ (¥á¡¼¥ë¡¢nfs ¥µ¡¼¥Ð¡¢cron ¤Ê¤É¤Ê¤É)
¤½¤ì¤¾¤ì¤ËÂФ·¤Æ¡¢¥Ö¡¼¥È¥¹¥¯¥ê¥×¥È¤¬¤Ò¤È¤Ä¤º¤ÄÆÃÄê¤Î¥Ç¥£¥ì¥¯¥È¥ê
(¤Û¤È¤ó¤É¤Î Linux ¤Ç
.IR /etc/init.d )
¤ËÇÛÃÖ¤µ¤ì¤ë¡£¤³¤ì¤é¤Î¥¹¥¯¥ê¥×¥È¤Ï¡¢
¤½¤ì¤¾¤ì°ú¿ô¤È¤·¤Æ¤Ò¤È¤Ä¤Îñ¸ì¤ò¼è¤ë¡£"start" ¤¬»ØÄꤵ¤ì¤ë¤È
¤½¤Î¥µ¡¼¥Ó¥¹¤òµ¯Æ°¤·¡¢"stop" ¤¬»ØÄꤵ¤ì¤ë¤È¥µ¡¼¥Ó¥¹¤òÄä»ß¤¹¤ë¡£
¥¹¥¯¥ê¥×¥È¤Ï¾¤Î¡ÖÊØÍø¤Ê¡×°ú¿ô¤ò¼è¤Ã¤Æ¤â¤è¤¤
(Î㤨¤Ð "restart" ¤ÇÄä»ß¡¦µ¯Æ°¤ò½çÈ֤˹Ԥ俤ꡢ"status"
¤Ç¥µ¡¼¥Ó¥¹¤Î¾õÂÖ¤òɽ¼¨¤¹¤ë¤Ê¤É)¡£
¥¹¥¯¥ê¥×¥È¤ò°ú¿ô¤Ê¤·¤Ç¼Â¹Ô¤¹¤ë¤È¡¢
»ØÄê¤Ç¤­¤ë°ú¿ô¤Î°ìÍ÷¤¬É½¼¨¤µ¤ì¤ë¡£
.\"O .SS "Sequencing Directories"
.SS ½ç½ø¤Å¤±¥Ç¥£¥ì¥¯¥È¥ê
.\"O To make specific scripts start/stop at specific run-levels and in
.\"O specific order, there are \fIsequencing directories\fR.
.\"O These
.\"O are normally in \fI/etc/rc[0\-6S].d\fR.
.\"O In each of these directories
.\"O there are links (usually symbolic) to the scripts in the \fI/etc/init.d\fR
.\"O directory.
¤¢¤ë¥é¥ó¥ì¥Ù¥ë¤Ç¡¢ÆÃÄê¤Î¥¹¥¯¥ê¥×¥È¤ò»ØÄꤷ¤¿½ç½ø¤Ç¼Â¹Ô¤µ¤»¤ë¤¿¤á¡¢
.I ½ç½øÉÕ¤±¥Ç¥£¥ì¥¯¥È¥ê (sequencing directory)
¤È¤¤¤¦»ÅÁȤߤ¬Â¸ºß¤¹¤ë¡£
¤³¤ì¤é¤Ï¤Õ¤Ä¤¦
.I /etc/rc[0\-6S].d
¤Ç¤¢¤ë¡£³Æ¥Ç¥£¥ì¥¯¥È¥ê¤ÎÆâÉô¤Ë¤Ï¡¢
.I /etc/init.d
¥Ç¥£¥ì¥¯¥È¥ê¤ËÃÖ¤«¤ì¤¿¥¹¥¯¥ê¥×¥È¤Ø¤Î¥ê¥ó¥¯ (¤Õ¤Ä¤¦¤Ï¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯)
¤¬ÃÖ¤«¤ì¤ë¡£

.\"O A primary script (usually \fI/etc/rc\fR) is called from
.\"O .BR inittab (5)
.\"O and calls the services scripts via the links in the sequencing directories.
.\"O All links with names that begin with \(aqS\(aq are being called with
.\"O the argument "start" (thereby starting the service).
.\"O All links with
.\"O names that begin with \(aqK\(aq are being called with the argument "stop"
.\"O (thereby stopping the service).
Âè°ì¥¹¥¯¥ê¥×¥È (Ä̾ï
.IR /etc/rc )
¤Ï
.BR inittab (5)
¤«¤é¸Æ¤Ð¤ì¡¢
½ç½øÉÕ¤±¥Ç¥£¥ì¥¯¥È¥ê¤ËÃÖ¤«¤ì¤¿¥ê¥ó¥¯·Ðͳ¤Ç³Æ¥µ¡¼¥Ó¥¹¥¹¥¯¥ê¥×¥È¤ò¸Æ¤Ó½Ð¤¹¡£
̾Á°¤¬ \(aqS\(aq ¤Ç¤Ï¤¸¤Þ¤ë¥ê¥ó¥¯¤Ï "start" ¤È¤¤¤¦°ú¿ô¤ò¤Ä¤±¤Æ¸Æ¤Ó½Ð¤µ¤ì
(¤¹¤Ê¤ï¤Á¥µ¡¼¥Ó¥¹¤¬µ¯Æ°¤·)¡£Ì¾Á°¤¬ \(aqK\(aq ¤Ç¤Ï¤¸¤Þ¤ë¥ê¥ó¥¯¤Ï "stop"
¤È¤¤¤¦°ú¿ô¤ò¤Ä¤±¤Æ¸Æ¤Ó½Ð¤µ¤ì¤ë (¤¹¤Ê¤ï¤Á¥µ¡¼¥Ó¥¹¤¬Ää»ß¤¹¤ë)¡£

.\"O To define the starting or stopping order within the same run-level,
.\"O the names of the links contain order-numbers.
.\"O Also, to make the names clearer, they usually
.\"O end with the name of the service they refer to.
.\"O Example:
.\"O the link \fI/etc/rc2.d/S80sendmail\fR starts the sendmail service on
.\"O runlevel 2.
.\"O This happens after \fI/etc/rc2.d/S12syslog\fR is run
.\"O but before \fI/etc/rc2.d/S90xfs\fR is run.
Ʊ¤¸¥é¥ó¥ì¥Ù¥ë¤ÎÆâÉô¤Ç¤Îµ¯Æ°¤äÄä»ß¤Î½ç½ø¤òµ¬Äꤹ¤ë¤¿¤á¤Ë¡¢
¥ê¥ó¥¯¤Î̾Á°¤Ë¤Ï½ç½ø¤ò¼¨¤¹¿ô»ú¤¬´Þ¤Þ¤ì¤ë¡£
¤Þ¤¿¡¢Ì¾Á°¤ò¤ï¤«¤ê¤ä¤¹¤¯¤¹¤ë¤¿¤á¡¢
¥ê¥ó¥¯Ì¾¤ÎËöÈø¤Ë¤ÏÂбþ¤¹¤ë¥µ¡¼¥Ó¥¹¤Î̾Á°¤¬¤Ä¤±¤é¤ì¤ë¡£
Î㤨¤Ð¡¢
.I /etc/rc2.d/S80sendmail
¤È¤¤¤¦¥ê¥ó¥¯¤Ï¡¢sendmail ¥µ¡¼¥Ó¥¹¤ò¥é¥ó¥ì¥Ù¥ë 2 ¤Ë¤ª¤¤¤Æµ¯Æ°¤¹¤ë¡£
¤³¤ì¤Ï¡¢
.I /etc/rc2.d/S12syslog
¤è¤ê¤â¸å¤Ë¡¢¤Þ¤¿
.I /etc/rc2.d/S90xfs
¤è¤ê¤âÀè¤Ë¼Â¹Ô¤µ¤ì¤ë¡£

.\"O To manage the boot order and run-levels, we have to manage these links.
.\"O However, on many versions of Linux, there are tools to help with this task
.\"O (e.g:
.\"O .BR chkconfig (8)).
¥Ö¡¼¥È¤Î½ç½ø¤È¥é¥ó¥ì¥Ù¥ë¤ò´ÉÍý¤¹¤ë¤Ë¤Ï¡¢
¤³¤ì¤é¤Î¥ê¥ó¥¯¤ò´ÉÍý¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
¤·¤«¤·Â¿¤¯¤Î Linux ¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó¤Ç¤Ï¡¢
¤³¤ì¤é¤Îºî¶È¤ò¼ê½õ¤±¤·¤Æ¤¯¤ì¤ë¥Ä¡¼¥ë¤¬Â¸ºß¤¹¤ë
(Î㤨¤Ð
.BR chkconfig (8)
¤Ê¤É)¡£
.\"O .SS "Boot Configuration"
.SS ¥Ö¡¼¥È¤ÎÀßÄê
.\"O Usually the daemons started may optionally receive command-line options
.\"O and parameters.
.\"O To allow system administrators to change these
.\"O parameters without editing the boot scripts themselves,
.\"O configuration files are used.
.\"O These are located in a specific
.\"O directory (\fI/etc/sysconfig\fR on Red Hat systems) and are
.\"O used by the boot scripts.
¥Ç¡¼¥â¥ó¤Îµ¯Æ°»þ¤Ë¤Ï¡¢
¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤ä¥Ñ¥é¥á¡¼¥¿¤ò»ØÄê¤Ç¤­¤ë¤Î¤¬ÉáÄ̤Ǥ¢¤ë¡£
¥·¥¹¥Æ¥à´ÉÍý¼Ô¤¬¤³¤ì¤é¤Î¥Ñ¥é¥á¡¼¥¿¤òÊѹ¹¤·¤¿¤¤¤È»×¤Ã¤¿¤È¤­¤Ë¡¢
¥Ö¡¼¥È¥¹¥¯¥ê¥×¥È¤½¤Î¤â¤Î¤òÊÔ½¸¤·¤Ê¤¯¤Æ¤â¤¹¤à¤è¤¦¡¢
ÀßÄê¥Õ¥¡¥¤¥ë¤¬ÍѤ¤¤é¤ì¤ë¡£¤³¤ì¤é¤ÏÆÃÄê¤Î¥Ç¥£¥ì¥¯¥È¥ê
(Red Hat ¥·¥¹¥Æ¥à¤Ç¤Ï
.IR /etc/sysconfig )
¤ËÃÖ¤«¤ì¡¢¥Ö¡¼¥È¥¹¥¯¥ê¥×¥È¤«¤é»²¾È¤µ¤ì¤ë¡£

.\"O In older UNIX systems, these files contained the actual command line
.\"O options for the daemons, but in modern Linux systems (and also
.\"O in HP-UX), these files just contain shell variables.
.\"O The boot scripts in \fI/etc/init.d\fR
.\"O \fBsource\fR the configuration
.\"O files, and then use the variable values.
¸Å¤¤ UNIX ¥·¥¹¥Æ¥à¤Ç¤Ï¡¢¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤Ë¤Ï
¥Ç¡¼¥â¥ó¤ËÍ¿¤¨¤ë¼ÂºÝ¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤¬½ñ¤«¤ì¤Æ¤¤¤¿¡£
¤·¤«¤·ºÇ¶á¤Î Linux ¥·¥¹¥Æ¥à (¤ä HP-UX) ¤Ç¤Ï¡¢
¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤Ë¤Ïñ¤Ë¥·¥§¥ëÊÑ¿ô¤¬½ñ¤«¤ì¤Æ¤¤¤ë¤À¤±¤Ç¤¢¤ë¡£
.I /etc/init.d
¤ËÃÖ¤«¤ì¤¿¥Ö¡¼¥È¥¹¥¯¥ê¥×¥È¤Ï¡¢¤³¤ì¤é¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤ò
.B source
¤·¡¢¤½¤ÎÊÑ¿ô¤ÎÃͤòÍѤ¤¤ë¡£
.\"O .SH FILES
.SH ¥Õ¥¡¥¤¥ë
.\"O .LP
.IR /etc/init.d/ ,
.\"O .IR /etc/rc[S0\-6].d/ ,
.IR /etc/rc[S0\-6].d/ ,
.I /etc/sysconfig/
.\"O .SH SEE ALSO
.SH ´ØÏ¢¹àÌÜ
.BR inittab (5),
.BR bootparam (7),
.BR init (8),
.BR runlevel (8),
.BR shutdown (8)