Method for repairing Grub boot loader based on Anaconda

Abstract

The invention relates to a method for repairing a Grub boot loader based on Anaconda installation program. In the invention, by abandoning the traditional method for repairing the Grub boot loader through a grubinstall command, the repairing of the Grub boot loader is realized by adding corresponding function module to the Anaconda installation program. In addition, according to the invention, an encryption function to the Grub boot loader is realized, kernel parameters are transmitted, and an installation position of the Grub boot loader can be customized. The method mainly comprises three steps of registering, configuring and repairing, and overcomes the defects of the prior art that the repairing of the Grub boot loader is incomplete, the operation steps are complicated, the requirements on the capability of an executor are high, an operation interface is unfriendly, and the like.

Description

technical field [0001] The invention relates to a method for repairing a Grub boot loader, in particular to a method for repairing a Grub boot loader based on Anaconda under a Linux system. Background technique [0002] Usually users install Grub on the MBR when installing the Linux operating system. However, due to various reasons, such as installing the Windows operating system on the machine where Linux is installed or cleaning the data due to misoperation, the MBR data may be cleared, causing the Linux system to fail. Unable to find Grub and unable to boot the installed Linux system. [0003] At present, there are three main solutions: [0004] 1) Linux environment Live CD to repair Grub [0005] At present, mainstream Linux operating systems such as Ubuntu and Fedora series provide Live CDs. The environment provided by Live CDs can be repaired by using the command to repair the bootloader. The specific operation process is as follows: figure 1 shown; [0006] 2) Lin...

AI Technical Summary

Problems solved by technology

The principle of repairing the Grub boot loader in the above three methods is the same, that is, it is realized by running an external command—grubinstall, and there is a common problem: poor usability

[0012] The existing technical solutions only provide basic repair work for the Grub boot loader, and only the operating system can be booted after the repair is completed, lacking the function of customizing the Grub boot loader by passing parameters

[0013] 2) The operation steps are complicated

[0014] From the above operation flow chart, it can be seen that at least 5 complicated steps are required to complete the repair of the Grub bootloader, and almost every step requires the input of some commands and parameters. If the input is inaccurate, the system may need to be restarted. bring unnecessary trouble

[0015] 3) High requirements for implementers

[0016] The above solution requires the implementer to have a relatively in-depth understanding of the Linux system and the working mechanism of Grub before it can be implemented. For ordinary Linux users, this repair method is a challenge

[0017] 4) The operation interface is not friendly

Users can only edit the configuration file and execute the repair command on the terminal as a command line, which brings great inconvenience to the repair operation

[0019] 5) Cannot encrypt the Grub boot loader

[0020] Existing solutions do not provide a method for encrypting the Grub boot loader, which poses a security risk for systems with high security requirements

[0021] 6) Cannot pass kernel parameters for Grub bootloader

[0022] Existing solutions cannot pass kernel parameters, and cannot meet the needs of users to customize the kernel parameters booted by the operating system according to their own preferences or needs when starting the operating system

[0023] 7) Cannot customize where the Grub bootloader is installed

It cannot meet the needs of users to customize the installation location

Images