Practical lilo management tools

Lilo is a linux boot manager. It works like OS/2, NT BootManager, and system commander that many people use. When you press the Tab key at this prompt, it will display the currently bootable system: lilo: dos smplinux. In fact, lilo is a small boot program, which can be located in any location that may be used to guide the system, but we usually place it in the master boot area of the hard disk. This concept should be very familiar to anyone who has been dealing with viruses. After the system self-check is completed, it reads the content in the master boot area from the hard disk. Therefore, lilo takes over control of the system and can guide Linux. Theoretically, many books recommend that you use a floppy disk to guide the server to avoid possible damages. This is a typical example of a "textbook solution. You can see that multiple system names are displayed on the page. Enter a name to guide the corresponding system. lilo will automatically select the corresponding partition and Startup File to start the system. A duel with lilo is part of the life of the system administrator. The hard disk may be damaged, the virus may change the boot record, and the kernel may be incorrectly compiled to reimburse the system, even some stupid anti-virus programs may corrupt lilo. In this case, you may have to boot from DOS and reconfigure lilo. How to start Linux from DOS. Let's talk about how to deal with lilo now. Lilo configuration relies on editing/etc/lilo. conf implementation. The rule for this file is very simple. For example, this is my lilo file: [wanghy @ openlab/etc] $ cat lilo. confboot =/dev/hdainstall =/boot. bprompttimeout = 50 default = smpimage =/boot/bzImagelabel = smpread-onlyappend = "mem = 256 M" root =/dev/hda1image =/boot/vmlinuz-2.2.12-20label = linuxread-onlyroot =/dev /hda1 other =/dev/hda3label = dostable =/dev/hda first is boot =/dev/hda, this means that the disk you use is the first IDE hard disk. For this reason, you usually cannot start Linux from the disk ). Next, install =/boot. B to write the/boot. B file to the boot Record. This file has been created when Linux is installed. Prompttimeout = 50 default = smp indicates that a lilo will be displayed when the system starts: prompt information and wait for 5 seconds. Note that the timeout is measured in 0.1 seconds. If the system name is not entered within five seconds, the system labeled "smp" will be booted by default. Next, we define various boot projects. First, we define two Linux boot projects. lines such as image =/root/bzImage define the kernel image used at startup. Next, label = smp defines the name of the startup selection item as smp. In the following lines, some additional parameters are used when bzImage is used to start the system: read-only is used to connect to the file system in read-only mode. Because the system needs to check the integrity of the file system at startup, therefore, you need to use this option. After the system starts, the startup script automatically switches it to read-write mode. Append = "mem = 256 M" by default, the Linux kernel uses only 64 MB of memory space. because the system has MB of memory, you must use the command line to directly notify the kernel, the content after append is the command line parameter added to the kernel at startup. Note that sometimes you need to write it as mem = 255 M, because the bios occupies part of the storage space on many systems. If you are not sure, subtract one from the amount of memory. Root =/dev/hda1 after the kernel is started, use the/dev/hda1 file system as the root of the local file system. The effect of the following section is the same as what we just explained. We just defined a startup Item named "smp", which starts Linux and connects to the/dev/hda1 file system, while the Section starting with image =/boot/vmlinuz-2.2.12-20 defines an option named "Linux" that uses/boot/vmlinuz-2.2.12-20 as the kernel image to mount the/dev/hda1 file system, however, only the default 64 MB memory is used. The next section other =/dev/hda3label = dostable =/dev/hda defines a startup Item named dos, which is used to start the MS-DOS partition located on/dev/hda3. Because DOS uses boot records instead of kernel images, the system must be able to find partition table information to locate boot records, table =/dev/hda indicates that the DOS partition table of the system is on/dev/hda. When lilo. after conf is set, execute/sbin/lilo to display the following information: [openlab] #/sbin/liloAdded smp * Added linux Added dos * indicates that the Added item is the default startup Item. The three lines of information indicate that all the three startup items we have defined have been added, and you can use the new startup definition after the startup. Lilo also supports many other definitions, but for the system administrator, the above explanation is enough. To learn more, execute man lilo. conf. As mentioned above, Linux makes the kernel into a compressed binary memory image during kernel compilation, automatically copies the image to the memory during startup, decompress the image, and then takes over the system with the core code. After the core code gets control of the system, the next step is to detect the system device and activate the required device, during which a string of initialization information is rolled over on the screen: Linux version 2.2.14 (root@openlab.asnc.edu.cn) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) #9 SMP Sat Jan 29 10:07:06 EST 2000 Intel MultiProcessor Specification v1.1Virtual Wire compatibility mode. oem id: MSIProduct ID: 440 BXAPIC at: 0xFEE00000Processor #0 Pentium (tm) Pro APIC version 17 Processor #1 Pentium (tm) Pro APIC ver Sion 17I/o apic #2 Version 17 at 0xFEC00000. processors: 2 mapped APIC to ffffe000 (fee00000) mapped IOAPIC to ffffd000 (fec00000) Detected 451033204Hz processor. console: color VGA + 80x25Calibrating delay loop... 448.92 BogoMIPSMemory: 257700 k/262144 k available (1044 k kernel code, 424 k reserved, 2920 k data, 56 k init) Dentry hash table entries: 32768 (order 6,256 k) buffer cache hash table entries: 262 144 (order 8, 1024 k) Page cache hash table entries: 65536 (order 6,256 k) VFS: Diskquotas version dquot_6.4.0 initializedChecking 386/387 coupling... OK, FPU using exception 16 error reporting. checking 'hlt 'instruction... OK .............. this information is very long, and almost every initialized device will display a message, from which we can see that those devices in the system have started to work and those devices have failed. If the information is rolled too fast, you can use the dmesg command to display all the information after the startup is complete. After the initialization is completed, Linux is linked to lilo. conf root = the root file system defined in the row. When the init process is started, remember that it is the initial initiator of all programs.) Search for the/etc/inittab file and enter the runtime settings.