This protects the root filesystem during the boot and ensures that the filesystem check (fsck) runs reliably. Later in the startup process, the root will be re-mounted as read/write after fsck completes. See the discussion of rc.sysinit later in this chapter. The root=/dev/hda3 option is also kernel-specific. It defines the location of the root filesystem for the kernel. The lilo.conf file should have a root option associated with the kernel image. If it is not defined here, the root filesystem must be defined separately with the rdev command. However, don’t do that; define the root in the LILO configuration. The last three lines in the sample file define the other operating system that LILO is able to boot. The other OS is located in partition 1 of the first IDE drive, other=/dev/hda1. As the label=dos entry indicates, it is Microsoft Windows. The optional command tells /sbin/lilo, which is called the mapper, that when it builds the map file, it should consider this operating system optional. That means that /sbin/lilo should complete building the map file, even if this operating system is not found. Whenever you modify the LILO configuration, invoke /sbin/lilo to install the new configuration. Until /sbin/lilo is run and maps the new configuration options, they have no effect. The grub.conf file, on the other hand, does not require any special processing. Changes to the GRUB configuration take effect immediately. Only Linux and one other operating system appear in the sample file, which is the most common case for desktop clients. However, LILO can act as the boot manager for up to 16 different operating systems. It is possible to see several other and image options in a lilo.conf file. Multiple image options are used when testing different Linux kernels. The most common reason for multiple other options is a training system in which users boot different OSs to learn about them. In an average operational environment, only one operating system is installed on a server, and no more than two operating systems are installed on a client. lilo.conf Hardware Options There are many more lilo.conf configuration options than those described previously, but you won’t need to use most of them. The sample configuration file in Listing 1.2 is almost identical to the one built by the installation program on any other system. Basically, the small subset of options just described includes the options used to build 99 percent of all LILO configuration files. The one percent of systems that cannot be configured with the usual commands are often those systems with hardware difficulties. The lilo.conf file provides several options for dealing with hardware problems. The lba32 option is used when the boot partition is placed above the 1024-cylinder limit. This option requires a BIOS that supports 32-bit Logical Block Addresses (LBA32) for booting. The Red Hat installation program displays a “Force use of LBA32″ check box in the boot loader installation screen. If this is available in your BIOS, it is the simplest way to boot from beyond the 1024-cylinder barrier. The linear option forces the system to use linear sector addresses sequential sector numbers instead of traditional cylinder, head, and sector addresses. This is sometimes necessary to handle large SCSI disks. It is even possible to manually define the disk geometry and linear addresses of the partitions directly in the LILO configuration file. For example: disk=/dev/hda bios=0×80 sectors=63 19
Note: If you are looking for cheap and inexpensive provider to host and run your tomcat application check Actions tomcat hosting services