📄 00000093.htm
字号:
<HTML><HEAD> <TITLE>BBS水木清华站∶精华区</TITLE></HEAD><BODY><CENTER><H1>BBS水木清华站∶精华区</H1></CENTER>发信人: reden (鱼 ~ 梦娜丽莎的微笑 流星的故事), 信区: Linux <BR>标 题: The Boot Procedure <BR>发信站: BBS 水木清华站 (Wed Nov 25 01:13:49 1998) <BR> <BR>Last modified: Thursday, 21 August 1997 15:09 EST <BR> <BR> <BR> <BR> <BR> <BR> <BR>The Boot Procedure <BR> <BR>Bootstrapping is the process of starting up a computer from a halted or powered-down condition. When the computer is <BR>switched on, it activates the memory-resident code which resides on the CPU board. The normal facilities of the operating <BR>system are not available at this stage and the computer must 'pull itself up by its own boot-straps' so to speak. This <BR>procedure therefore is often referred to as bootstrapping, also known as cold boot. Although the bootstrap procedure is <BR>very hardware dependent, it typically consists of the following steps: <BR> <BR> The memory-resident code <BR> Runs self-test. <BR> Probes bus for the boot device <BR> Reads the boot program from the boot device. <BR> Boot program reads in the kernel and passes control to it. <BR> Kernel identifies and configures the devices. <BR> Initializes the system and starts the system processes. <BR> Brings up the system in single-user mode (if necessary). <BR> Runs the appropriate startup scripts. <BR> Brings up the system for multi-user operation. <BR> <BR>Kernel <BR> <BR>Most Unix systems implement a two-stage loading process. During the first stage, a small boot program is read into <BR>memory from a default or specified device. It is this program that reads in the kernel and relinquishes the control to it. <BR>The path to the kernel is vendor-dependent. For example, it is /vmunix on SunOS 4.x, Digital Unix and Ultrix, /kernel/unix <BR>on SunOS 5.x, /hp-ux on HP-UX, and /unix on IRIX and AIX systems. <BR> <BR>One of the very first, probably the most difficult, tasks a system administrator must perform, is configuring the kernel. <BR>You'll read the details later in the sections dealing with the 'Operating System Installation'. Once the kernel is loaded, it <BR>remains in the memory during the running of the system and is usually run in a fixed amount of memory. When the kernel <BR>starts, it normally displays its size and the amount of physical memory remaining after the kernel is loaded. The kernel <BR>probes the bus to locate the devices specified during the configuration, and initializes the located devices (ignoring those <BR>that it can't contact). Any device not detected and initialized during the boot will not be accessible to system until it is <BR>properly connected and the system is rebooted. <BR> <BR>System Processes <BR> <BR>The kernel identifies the root, swap, and dump devices and then starts programs to schedule processes, manage <BR>physical memory and virtual memory, and the init process. BSD systems starts three initialization processes; swapper, init <BR>and pagedaemon. On the SVR4 systems the initialization processes include sched, init, and various memory handlers <BR>(except on Solaris). <BR> <BR>sched <BR> <BR>The real-time scheduler, sched, runs as process 0 on SVR5 systems. It can be used to set priority for real-time <BR>processes so that they can be given fast access to the kernel. <BR> <BR>swapper <BR> <BR>The swapper daemon runs as process 0 on BSD systems. It manages the physical memory by moving process from <BR>physical memory to swap space when more physical memory is needed. <BR> <BR>Page Daemon <BR> <BR>Various memory handlers run as process 2. When a page of virtual memory is accessed, the page table within the kernel <BR>is consulted and if necessary, the pagedaemon (SunOS 4.x) or pageout (SunOS 5.x) is used to move pages in and out of <BR>physical memory and to update page tables. Similar memory handlers exist on other SVR5 systems. <BR> <BR>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -