11.01.2015 Views

Red Hat Enterprise Linux Installation Guide 5.2 - linux.meuhobby.com

Red Hat Enterprise Linux Installation Guide 5.2 - linux.meuhobby.com

Red Hat Enterprise Linux Installation Guide 5.2 - linux.meuhobby.com

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The Kernel<br />

following format — /boot/vmlinuz- file (where <br />

corresponds to the kernel version specified in the boot loader's settings).<br />

For instructions on using the boot loader to supply <strong>com</strong>mand line arguments to the kernel, refer<br />

to Chapter 9, The GRUB Boot Loader. For information on changing the runlevel at the boot<br />

loader prompt, refer Section 8, “Changing Runlevels at Boot Time”.<br />

The boot loader then places one or more appropriate initramfs images into memory. Next, the<br />

kernel de<strong>com</strong>presses these images from memory to /sysroot/, a RAM-based virtual file<br />

system, via cpio. The initramfs is used by the kernel to load drivers and modules necessary<br />

to boot the system. This is particularly important if SCSI hard drives are present or if the<br />

systems use the ext3 file system.<br />

Once the kernel and the initramfs image(s) are loaded into memory, the boot loader hands<br />

control of the boot process to the kernel.<br />

For a more detailed overview of the GRUB boot loader, refer to Chapter 9, The GRUB Boot<br />

Loader.<br />

2.2.1. Boot Loaders for Other Architectures<br />

Once the kernel loads and hands off the boot process to the init <strong>com</strong>mand, the same<br />

sequence of events occurs on every architecture. So the main difference between each<br />

architecture's boot process is in the application used to find and load the kernel.<br />

For example, the Itanium architecture uses the ELILO boot loader, the IBM eServer pSeries<br />

architecture uses yaboot, and the IBM System z systems use the z/IPL boot loader.<br />

2.3. The Kernel<br />

When the kernel is loaded, it immediately initializes and configures the <strong>com</strong>puter's memory and<br />

configures the various hardware attached to the system, including all processors, I/O<br />

subsystems, and storage devices. It then looks for the <strong>com</strong>pressed initramfs image(s) in a<br />

predetermined location in memory, de<strong>com</strong>presses it directly to /sysroot/, and loads all<br />

necessary drivers. Next, it initializes virtual devices related to the file system, such as LVM or<br />

software RAID, before <strong>com</strong>pleting the initramfs processes and freeing up all the memory the<br />

disk image once occupied.<br />

The kernel then creates a root device, mounts the root partition read-only, and frees any unused<br />

memory.<br />

At this point, the kernel is loaded into memory and operational. However, since there are no<br />

user applications that allow meaningful input to the system, not much can be done with the<br />

system.<br />

To set up the user environment, the kernel executes the /sbin/init program.<br />

2.4. The /sbin/init Program<br />

The /sbin/init program (also called init) coordinates the rest of the boot process and<br />

339

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!