Experienced personnel guide you to install LINUX

LINUX is still quite common, So I studied the LINU file and shared it with you here. I hope it will be useful to you. Installing the last LINUX system is not difficult. installing it in the extended partition is the correct solution. We recommend that you check the excellent posts of the old knife ).

However, it is difficult for many cainiao to set the position of the boot program. One is to attach the program to MBR, and the other is to install the program in the first sector of the partition where the LINUX system is located, these two options are available when GRUB is installed on LINUX systems of each release. Based on my actual experience, it is absolutely no problem to install MBR. Don't trust the content in the so-called LINUX system tutorial. Try it on your own.) GRUB's multi-boot menu will definitely come out, in the following method, I tried to install FC1, FC4, and MDK10). After the system is installed, only the WINDOWS Multi-Start Menu is displayed, and GRUB restart is unavailable. However, MBR is a battle for various systems. In particular, once WINDOWS is reinstalled, MBR records will be overwritten, and GRUB will be gone. It is no wonder that we do not recommend you to install MBR in various books. We recommend that you do a good job of GHOST after installing WINDOWS. If you reinstall the system, you do not need to use the installation disc and restore it directly. Rest assured that GHOST restoration will not affect MBR information based on my experience. GRUB provides a strong multi-system boot function. After installing it on MBR, you can export the WINDOWS Multi-boot menu from the boot menu and then start WINDOWS of various versions.

This time, I installed FC4Fedora Core 4 and RFDT5Red Flag Desktop 2.6 on a WINDOWS XP laptop that only supports LINUX systems with the kernel version 5.0 ). FC4 is specialized in advanced operations and development of LINUX systems. RFDT5 is developed in China and is easy to use and superior to Chinese culture. It is suitable for personal applications of LINUX systems. During installation, a large amount of free space is allocated at the end of the extended partition, which is about 15 GB for the installation of two LINUX systems. After FC4 is installed, there is more than 7 GB of free space at the end of the extended partition, and RFDT5 is mounted to this 7 GB space. GRUB of both systems are mounted to MBR. Of course, it will only be later. The partition table after installation is as follows:
Operating System File System Format label/mount point to which the Partition Number belongs
Hda1 (hd0, 0) windows xp ntfs System
Hda2 (hd0, 1) windows xp ntfs Security
Hda5 (hd0, 4) WINDOWS XP VFAT
Hda6 (hd0, 5) windows xp ntfs NTFS-1.
Hda7 (hd0, 6) windows xp ntfs NTFS-2.
Hda8 (hd0, 7) Fedora Core 4 EXT3/boot
Hda9 (hd0, 8) Fedora Core 4 EXT3/home
Hda10 (hd0, 9) Fedora Core 4 EXT3/usr
SWAP sharing between hda11 (hd0, 10) FC4 and RFDT5 is not applicable.
Hda12 (hd0, 11) Fedora Core 4 EXT3/
Hda13 (hd0, 12) RFDT5 EXT3/boot
Hda14 (hd0, 13) RFDT5 EXT3/
Hda15 (hd0, 14) RFDT5 EXT3/usr
Hda16 (hd0, 15) RFDT5 EXT3/home

Note: A general MBR hard disk supports a maximum of four primary partitions, or a maximum of three primary partitions plus an extended partition. In theory, the number of logical partitions that can be divided in an extended partition is unlimited; GTPGUID Partition Table) a hard disk can support a maximum of 128 primary partitions, so you do not need to expand the partition.

Although FC4 is added when GRUB of RFDT5 is installed, the boot location points to the root directory of FC4/) The mounted partition hda12 (hd0, 11 ). However, RFDT5 can boot normally, while FC4 cannot boot, and "file not found" is always displayed ". GRUB should mount the kernel of this version of LINUX system during LINUX boot. Find vmlinuz-xxx and initrd in the/boot directory of FC4. -xxx. img files, GRUB also needs to know the Partition Number mounted to the root directory. To enable the FC4 boot option to appear in the Multi-boot menu of GRUB, you must change the GRUB configuration file of RFDT5, which is in the hda13 (hd0, 12) partition, path:/boot/grub. conf. You must use the vi editor to change the configuration file in LINUX. Next we will introduce how to change it:
Start the command line terminal in the RFDT5 system; command: vi/boot/grub. conf start the vi editor and open the grub. conf file. Note that this part of the opened file contains:
The following statements are correct:

Title Red Flag Desktop 5.0 (2.6.9-5.34DT)
Root (hd0, 12)
Kernel/vmlinuz-2.6.9-5.34DT ro root = LABEL =/1 vga = 785 splash = silent resume2 = swap:/dev/hda11
Initrd/initrd-2.6.9-5.34DT.img

Title Red Flag Desktop 5.0-2.6.9-5.34DT (Safe Mode)
Root (hd0, 12)
Kernel/vmlinuz-2.6.9-5.34DT ro root = LABEL =/1 4
Initrd/initrd-2.6.9-5.34DT.img

Title Red Flag Desktop 5.0-2.6.9-5.34DT (Console Mode)
Root (hd0, 12)
Kernel/vmlinuz-2.6.9-5.34DT ro root = LABEL =/1 3
Initrd/initrd-2.6.9-5.34DT.img

Title Microsoft Windows
Rootnoverify (hd0, 0)
Chainloader + 1

Title Red Hat Fedora Core 4
Root (hd0, 7)
Kernel/vmlinuz-2.6.11-1.1369_FC4 root =/dev/hda12
Initrd/initrd-2.6.11-1.1369_FC4.img

Obviously, the title statement is the name of each option in the GRUB menu. It can be seen that there are five objects to be guided in the GRUB boot menu.

For LINUX systems, the root statement specifies the partition to be mounted to the GRUB root file system. Note that the GRUB root file system does not have any relationship with the LINUX root file system, only to mount the partition; the kernel statement is to load the LINUX kernel in the specified path. Note that this path is determined according to the GRUB root file system, it is not the root file system of LINUX.

For example, the FC4 kernel vmlinuz-2.6.11-1.1369_FC4 is located on the hda8 (hd0, 7) Partition mounted on the/boot directory of FC4, the path of the kernel in FC4 is/boot/vmlinuz-2.6.11-1.1369_FC4, in fact, the LINUX kernel is in the/boot directory of LINUX, but the partition is mounted on the GRUB root file system/), the path should be/vmlinuz-2.6.11-1.1369_FC4, the content in/is the content in hda8 (hd0, 7) instead of the content in hda12 (hd0, 11) mounted to FC4. Therefore, the parameter after kernel is/vmlinuz-2.6.11-1.1369_FC4, rather than/boot/vmlinuz-2.6.11-1.1369_FC4, the value assigned to the root variable is the Partition Number of FC4/hanging, during the boot process, GRUB must let the kernel know the location of the LINUX system after it is started. Ro generally indicates that the partition is mounted in read-only mode.

The initrd statement is used to load the initrd file. I am not very clear about the role of this file. It is said that it is an available ramdisk. This file is very important when you start the LINUX system. Therefore, you must specify the path in the GRUB root file system, which is always in the same path as the kernel.
Since WINDOWS uses the chain Loading Method to start, the boot statement under the title is different from that in LINUX. I don't know much about writing block lists. The content in the general GRUB configuration file about Booting WINDOWS is exactly the same as that listed above.

After understanding the above content, to guide FC4, you only need to write the root kernel initrd statement to the example above. The key is that the path and partition number must be accurate. At the beginning, I couldn't boot FC4, because RFDT5's GRUB identified it as a WINDOWS system that uses chained loading. The statement under the title is to guide the writing of WINDOWS.

To change the text in vi, you need to know the basic operations of vi:
Directly input vi and file name in the command line to start vi to enter normal mode and open the file, but it cannot be edited in general mode; as long as you press the I, o, a and other characters, you can enter the editing mode to change the content in the text. After editing, Press Esc to exit the editing mode and return to the general mode. In general mode, press: To Enter: the cursor moves to the lower left corner of the screen. Wait for the input command, enter q for execution, and exit from the non-stored disk. Enter wq for execution, save the disk, and exit. Enter wq! Execute, force save the disk and exit, which is used when the file permission is not allowed to be written.

1. Operation notes: Linux system backup tar Compression
2. What makes Linux brilliant?
3. Detailed explanation of insecure Linux system programs and replacements
4. Teach you how to back up data in Linux
5. Detailed description of Linux boot program Switching