CN114090052A - Method, device, terminal and storage medium for repairing Linux system - Google Patents
Method, device, terminal and storage medium for repairing Linux system Download PDFInfo
- Publication number
- CN114090052A CN114090052A CN202111449589.XA CN202111449589A CN114090052A CN 114090052 A CN114090052 A CN 114090052A CN 202111449589 A CN202111449589 A CN 202111449589A CN 114090052 A CN114090052 A CN 114090052A
- Authority
- CN
- China
- Prior art keywords
- software
- bottom layer
- system bottom
- repair
- layer software
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention discloses a method, a device, a terminal and a storage medium for repairing a Linux system, wherein the method comprises the following steps: if the repair request is received, reading software installation data of the current system bottom layer software of the Linux system corresponding to the repair request; comparing the current software installation data with the initial software installation data; if the system bottom layer software with the fault and the fault type are determined based on the comparison, providing a repair option corresponding to the fault type for a user; and if a user's instruction for confirming repair is received, performing repair on the system bottom layer software with the fault based on the repair option. According to the scheme, based on the comparison of the initial software installation data and the software installation data of the current system bottom layer software, the system bottom layer software with the fault and the type of the fault are determined, and corresponding repair options are provided for a user based on the type of the fault, so that the Linux system is repaired.
Description
Technical Field
The present invention relates to the field of system repair technologies, and in particular, to a method, an apparatus, a terminal, and a storage medium for repairing a Linux system.
Background
In a Linux (an operating system free of charge and propagation), a Red Hat system (a Linux system distributed by Red Hat company) employs an rpm (Red-Hat Package Manager) Package management mechanism; due to the management mechanism, a user may delete or damage some software packages by misoperation or install some software package versions outside the system in the using process; these operations may cause the system to fail to operate properly, but there is no corresponding solution for this situation at present.
Thus, there is a need for a solution to the problems of the prior art.
Disclosure of Invention
In view of the above, the present invention provides a method, an apparatus, a terminal and a storage medium for repairing a Linux system, so as to solve the problems in the prior art.
Specifically, the present invention proposes the following specific examples:
the embodiment of the invention provides a method for repairing a Linux system, which comprises the following steps:
if a repair request is received, reading software installation data of the current system bottom layer software of the Linux system corresponding to the repair request;
comparing the current software installation data with the initial software installation data; the initial software installation data is stored with data generated by first installing system bottom software on the Linux system;
if the system bottom layer software with the fault and the fault type are determined based on the comparison, providing a repair option corresponding to the fault type for a user; different repair options correspond to different fault types;
and if a user's instruction for confirming repair is received, performing repair on the system bottom layer software with the fault based on the repair option.
In a specific embodiment, the software installation data includes: the name of the system bottom layer software, the version information of the system bottom layer software, the name of each file generated after the system bottom layer software is installed and the level information of each file.
In a specific embodiment, the fault types include: the method comprises the following steps that system bottom layer software is unloaded, files of the system bottom layer software are lost, the system bottom layer software is upgraded and the system bottom layer software is degraded;
the repair options include: reinstalling system bottom software, degrading the system bottom software and upgrading the system bottom software.
In a specific embodiment, the method further comprises the following steps:
if the system bottom layer software with the fault cannot be determined based on the comparison, providing all reinstallation options for the user; and the all-reinstallation option is used for reinstalling all system bottom-layer software in the initial software installation data.
In a specific embodiment, the method further comprises the following steps:
counting the number of faults of the bottom software of each system in the Linux system;
and backing up the files generated after the system bottom layer software with the number larger than the threshold value is installed, so that the system bottom layer software is operated based on the backed-up files after the files generated by the original installation are damaged.
The embodiment of the invention also provides a device for repairing the Linux system, which comprises the following components:
the reading module is used for reading the software installation data of the current system bottom layer software of the Linux system corresponding to the repair request if the repair request is received;
the comparison module is used for comparing the current software installation data with the initial software installation data; the initial software installation data is stored with data generated by first installing system bottom software on the Linux system;
the option module is used for providing a repair option corresponding to the fault type for a user if the system bottom layer software with the fault and the fault type are determined based on the comparison; different repair options correspond to different fault types;
and the repair module is used for repairing the failed system bottom layer software based on the repair option if a repair confirmation instruction of the user is received.
In a specific embodiment, the software installation data includes: the name of the system bottom layer software, the version information of the system bottom layer software, the name of each file generated after the system bottom layer software is installed and the level information of each file.
In a specific embodiment, the fault types include: the method comprises the following steps that system bottom layer software is unloaded, files of the system bottom layer software are lost, the system bottom layer software is upgraded and the system bottom layer software is degraded;
the repair options include: reinstalling system bottom software, degrading the system bottom software and upgrading the system bottom software.
The embodiment of the invention also provides a terminal which comprises a memory and a processor, wherein the memory is stored with an application program, and the processor is used for realizing the method for repairing the Linux system when executing the application program.
The embodiment of the invention also provides a storage medium, wherein an application program is stored in the storage medium, and the method for repairing the Linux system is realized when the application program is executed.
Therefore, the embodiment of the invention provides a method, a device, a terminal and a storage medium for repairing a Linux system, wherein the method comprises the following steps: if a repair request is received, reading software installation data of the current system bottom layer software of the Linux system corresponding to the repair request; comparing the current software installation data with the initial software installation data; the initial software installation data is stored with data generated by first installing system bottom software on the Linux system; if the system bottom layer software with the fault and the fault type are determined based on the comparison, providing a repair option corresponding to the fault type for a user; different repair options correspond to different fault types; and if a user's instruction for confirming repair is received, performing repair on the system bottom layer software with the fault based on the repair option. According to the scheme, the system bottom layer software with the fault and the type of the fault are determined in a mode of comparing the initial software installation data with the software installation data of the current system bottom layer software, and therefore, corresponding repair options are provided for users based on the type of the fault, and the Linux system is repaired.
Drawings
In order to more clearly illustrate the technical solution of the present invention, the drawings required to be used in the embodiments will be briefly described below, and it should be understood that the following drawings only illustrate some embodiments of the present invention, and therefore should not be considered as limiting the scope of the present invention. Like components are numbered similarly in the various figures.
Fig. 1 is a schematic flow chart illustrating a method for repairing a Linux system according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram illustrating an apparatus for repairing a Linux system according to an embodiment of the present invention;
FIG. 3 is another schematic structural diagram of an apparatus for repairing a Linux system according to an embodiment of the present invention;
fig. 4 shows a third structural schematic diagram of an apparatus for repairing a Linux system according to an embodiment of the present invention.
Illustration of the drawings:
201-a reading module; 202-an alignment module; 203-option module; 204-repair module;
205-a processing module; 206-backup module.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments.
The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present invention without making any creative effort, shall fall within the protection scope of the present invention.
Hereinafter, the terms "including", "having", and their derivatives, which may be used in various embodiments of the present invention, are only intended to indicate specific features, numbers, steps, operations, elements, components, or combinations of the foregoing, and should not be construed as first excluding the existence of, or adding to, one or more other features, numbers, steps, operations, elements, components, or combinations of the foregoing.
Furthermore, the terms "first," "second," "third," and the like are used solely to distinguish one from another and are not to be construed as indicating or implying relative importance.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which various embodiments of the present invention belong. The terms (such as those defined in commonly used dictionaries) should be interpreted as having a meaning that is consistent with their contextual meaning in the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein in various embodiments of the present invention.
Example 1
The embodiment 1 of the invention discloses a method for repairing a Linux system, which comprises the following steps as shown in FIG. 1:
step S101, if a repair request is received, reading software installation data of the current system bottom layer software of the Linux system corresponding to the repair request;
specifically, before step S101, that is, when the Linux system is initially installed, one or more system bottom layer software may be installed at the same time, and when the system bottom layer software is initially installed, data generated by installing the system bottom layer software, that is, initial software installation data may be stored, where the specific initial software installation data may include a name of the system bottom layer software, version information of the system bottom layer software, names of files generated after the system bottom layer software is installed, and hierarchy information of the files.
The specific system bottom layer software is software at the system bottom layer in the Linux system (different from software of a general application layer, the damage of the software of the application layer only affects the software of the application layer), and the system bottom layer software affects the normal operation of the Linux system. The system underlying software may be some module/sub-software/rpm package of the Linux system.
When finding that the Linux system cannot be started, a user sends a repair request, and under the condition, the installation data of the current system bottom layer software of the Linux system can be obtained.
S102, comparing the current software installation data with the initial software installation data; the initial software installation data is stored with data generated by first installing system bottom software on the Linux system;
comparing the current software installation data with the initial software installation data, and specifically comparing the data difference between the current software installation data and the initial software installation data, such as comparing the name of the installed software, the version number of the same software, the name of each file generated after the same software is installed and whether the level information of each file is different or not;
if there is a difference, it may be confirmed that there is a failure, and the system underlying software having the failure and the corresponding failure type may be determined, thereby proceeding to step S103.
Step S103, if the system bottom layer software with faults and the fault types are determined based on comparison, repair options corresponding to the fault types are provided for users; different repair options correspond to different fault types;
specifically, the fault types include: the method comprises the following steps that system bottom layer software is unloaded, files of the system bottom layer software are lost, the system bottom layer software is upgraded and the system bottom layer software is degraded; correspondingly, the repair options include: reinstalling system bottom software, degrading the system bottom software and upgrading the system bottom software.
Specifically, for example, the comparison determines that the current software installation data includes the software name: software 2, software 3, but the software name included in the initial software installation data: software 1, software 2, software 3; in this case, it may then be confirmed that software 1 is uninstalled, and thus, the corresponding repair option may be to reinstall software 1.
In addition, if the comparison determines that the version of the software 2 installed in the current software installation data is 1.1; but the version of the software 2 in the initial software installation data is 1.0; the degradation process needs to be performed on the software 2; if the version of the software 2 installed in the current software installation data is 0.9; the upgrade process needs to be performed on the software 2.
The specific version is distinguished by the size of a general number, and if there are other distinguishing ways for the version, the description is not repeated here.
For another example, if it is determined that the file of the software 2 installed in the initial software installation data includes the file 3, but the file 3 does not exist in the file of the software 2 installed in the current software installation data, it may be determined that the file of the software 2 is lost.
And step S104, if a repair confirmation instruction of the user is received, performing repair on the system bottom layer software with the fault based on the repair option.
The above steps are methods executed by software that has confirmed a fault, and further, if no comparison is made to confirm a fault, the method further includes: if the system bottom layer software with the fault cannot be determined based on the comparison, providing all reinstallation options for the user; and the all-reinstallation option is used for reinstalling all system bottom-layer software in the initial software installation data.
Specifically, if the failed system bottom layer software cannot be confirmed, a repair option for reinstalling all system bottom layer software in the initial software installation data may be provided. And if the repair option obtains the confirmed execution instruction of the user, executing the reinstallation of all system bottom layer software.
Further, the above steps are processing procedures after the occurrence of the fault, and the scheme is based on fault prevention and further includes: counting the number of faults of the bottom software of each system in the Linux system; and backing up the files generated after the system bottom layer software with the number larger than the threshold value is installed, so that the system bottom layer software is operated based on the backed-up files after the files generated by the original installation are damaged.
Specifically, the faults that have occurred may be counted to determine which software is particularly prone to faults, for example, when it is determined that the software 2 or 3 is particularly prone to faults, files generated during the initial installation of the software 2 or 3 may be backed up, so that when the files generated during the initial installation are damaged, the operation may be continued based on the backed-up files; compared with reinstallation, the time can be greatly shortened, so that the processing efficiency can be improved, and the use experience of a user is improved.
Example 2
For further explanation of the present invention, embodiment 2 of the present invention further discloses a device for repairing a Linux system, as shown in fig. 2, including:
the reading module 201 is configured to, if a repair request is received, read software installation data of current system bottom layer software of the Linux system corresponding to the repair request;
a comparison module 202, configured to compare the current software installation data with the initial software installation data; the initial software installation data is stored with data generated by first installing system bottom software on the Linux system;
the option module 203 is configured to provide a repair option corresponding to a fault type to a user if the system bottom layer software with the fault and the fault type are determined based on the comparison; different repair options correspond to different fault types;
and the repair module 204 is configured to, if a repair confirmation instruction of the user is received, perform repair on the failed system bottom layer software based on the repair option.
In a specific embodiment, the software installation data includes: the name of the system bottom layer software, the version information of the system bottom layer software, the name of each file generated after the system bottom layer software is installed and the level information of each file.
In a specific embodiment, the fault types include: the method comprises the following steps that system bottom layer software is unloaded, files of the system bottom layer software are lost, the system bottom layer software is upgraded and the system bottom layer software is degraded;
the repair options include: reinstalling system bottom software, degrading the system bottom software and upgrading the system bottom software.
In a specific embodiment, as shown in fig. 3, the apparatus further comprises:
the processing module 205 is configured to provide all reinstallation options to the user if the failed system bottom layer software cannot be determined based on the comparison; and the all-reinstallation option is used for reinstalling all system bottom-layer software in the initial software installation data.
In a specific embodiment, as shown in fig. 4, the apparatus further comprises:
the backup module 206 is used for counting the number of faults of the bottom software of each system in the Linux system;
and backing up the files generated after the system bottom layer software with the number larger than the threshold value is installed, so that the system bottom layer software is operated based on the backed-up files after the files generated by the original installation are damaged.
Example 3
The embodiment 3 of the invention also discloses a terminal, which comprises a memory and a processor, wherein the memory is stored with an application program, and the processor is used for realizing the method for repairing the Linux system in the embodiment 1 when executing the application program.
Example 4
The embodiment 4 of the invention also discloses a storage medium, wherein an application program is stored in the storage medium, and the method for repairing the Linux system in the embodiment 1 is realized when the application program is executed.
Therefore, the scheme of the invention provides a method, a device, a terminal and a storage medium for repairing a Linux system, wherein the method comprises the following steps: if a repair request is received, reading software installation data of the current system bottom layer software of the Linux system corresponding to the repair request; comparing the current software installation data with the initial software installation data; the initial software installation data is stored with data generated by first installing system bottom software on the Linux system; if the system bottom layer software with the fault and the fault type are determined based on the comparison, providing a repair option corresponding to the fault type for a user; different repair options correspond to different fault types; and if a user's instruction for confirming repair is received, performing repair on the system bottom layer software with the fault based on the repair option. According to the scheme, the system bottom layer software with the fault and the type of the fault are determined in a mode of comparing the initial software installation data with the software installation data of the current system bottom layer software, and therefore, corresponding repair options are provided for users based on the type of the fault, and the Linux system is repaired.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative and, for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, each functional module or unit in each embodiment of the present invention may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention or a part of the technical solution that contributes to the prior art in essence can be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a smart phone, a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention.
Claims (10)
1. A method for repairing a Linux system, comprising:
if a repair request is received, reading software installation data of the current system bottom layer software of the Linux system corresponding to the repair request;
comparing the current software installation data with the initial software installation data; the initial software installation data is stored with data generated by first installing system bottom software on the Linux system;
if the system bottom layer software with the fault and the fault type are determined based on the comparison, providing a repair option corresponding to the fault type for a user; different repair options correspond to different fault types;
and if a user's instruction for confirming repair is received, performing repair on the system bottom layer software with the fault based on the repair option.
2. The method of claim 1, wherein the software installation data comprises: the name of the system bottom layer software, the version information of the system bottom layer software, the name of each file generated after the system bottom layer software is installed and the level information of each file.
3. The method of claim 1 or 2, wherein the fault types include: the method comprises the following steps that system bottom layer software is unloaded, files of the system bottom layer software are lost, the system bottom layer software is upgraded and the system bottom layer software is degraded;
the repair options include: reinstalling system bottom software, degrading the system bottom software and upgrading the system bottom software.
4. The method of claim 1, further comprising:
if the system bottom layer software with the fault cannot be determined based on the comparison, providing all reinstallation options for the user; the full reinstallation option is used for reinstalling all system bottom layer software in the initial software installation data.
5. The method of claim 1, further comprising:
counting the number of faults of the bottom software of each system in the Linux system;
and backing up the files generated after the system bottom layer software with the number larger than the threshold value is installed, so that the system bottom layer software is operated based on the backed-up files after the files generated by the original installation are damaged.
6. An apparatus for repairing a Linux system, comprising:
the reading module is used for reading the software installation data of the current system bottom layer software of the Linux system corresponding to the repair request if the repair request is received;
the comparison module is used for comparing the current software installation data with the initial software installation data; the initial software installation data is stored with data generated by first installing system bottom software on the Linux system;
the option module is used for providing a repair option corresponding to the fault type for a user if the system bottom layer software with the fault and the fault type are determined based on the comparison; different repair options correspond to different fault types;
and the repair module is used for repairing the failed system bottom layer software based on the repair option if a repair confirmation instruction of the user is received.
7. The apparatus of claim 6, wherein the software installation data comprises: the name of the system bottom layer software, the version information of the system bottom layer software, the name of each file generated after the system bottom layer software is installed and the level information of each file.
8. The apparatus of claim 6 or 7, wherein the fault types include: the method comprises the following steps that system bottom layer software is unloaded, files of the system bottom layer software are lost, the system bottom layer software is upgraded and the system bottom layer software is degraded;
the repair options include: reinstalling system bottom software, degrading the system bottom software and upgrading the system bottom software.
9. A terminal, characterized by comprising a memory in which an application program is stored and a processor, said processor implementing the method of repairing a Linux system according to any one of claims 1-5 when executing said application program.
10. A storage medium, wherein an application program is stored in the storage medium, and the application program, when executed, implements the method for repairing the Linux system according to any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111449589.XA CN114090052A (en) | 2021-12-01 | 2021-12-01 | Method, device, terminal and storage medium for repairing Linux system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111449589.XA CN114090052A (en) | 2021-12-01 | 2021-12-01 | Method, device, terminal and storage medium for repairing Linux system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114090052A true CN114090052A (en) | 2022-02-25 |
Family
ID=80306125
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111449589.XA Pending CN114090052A (en) | 2021-12-01 | 2021-12-01 | Method, device, terminal and storage medium for repairing Linux system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114090052A (en) |
-
2021
- 2021-12-01 CN CN202111449589.XA patent/CN114090052A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8806476B2 (en) | Implementing a software installation process | |
| KR100758292B1 (en) | A method for renovating the computer operating system | |
| US7203865B2 (en) | Application level and BIOS level disaster recovery | |
| US20140310698A1 (en) | Apparatus and method for upgrading firmware of mobile terminal | |
| US7509544B2 (en) | Data repair and synchronization method of dual flash read only memory | |
| CN103677650A (en) | Drive letter drifting preventing and treating method and device | |
| CN111143132B (en) | BIOS recovery method, device, equipment and readable storage medium | |
| WO2012116637A1 (en) | System rescue method and device | |
| CN101930384A (en) | Fault tolerance method and device for file system | |
| US20100217751A1 (en) | Method and system for safely deleting information from a computer | |
| CN114780298B (en) | File data processing method and device, computer terminal and storage medium | |
| CN101196839A (en) | Data renovation and synchronization process of double-flash read-only memory | |
| CN105550071A (en) | System file upgrading and detecting method and communication device | |
| US20140156943A1 (en) | Information processing apparatus, information processing method, and program | |
| WO2014065803A1 (en) | Hard drive backup | |
| CN114090052A (en) | Method, device, terminal and storage medium for repairing Linux system | |
| CN110968456B (en) | Method and device for processing fault disk in distributed storage system | |
| KR100853941B1 (en) | Multimedia storage device and data recovering method of the device | |
| CN110795155B (en) | System starting method and device, electronic equipment and storage medium | |
| EP2490123A2 (en) | An embedded appliance | |
| CN111897583A (en) | Equipment starting method and embedded equipment | |
| CN111124729A (en) | Fault disk determination method, device, equipment and computer readable storage medium | |
| KR100792786B1 (en) | Method for os restoring of computer using backup image file | |
| KR20030062793A (en) | Apparatus and Method for operating recovery and backup of linux operting system | |
| US11714631B2 (en) | Method, electronic device, and computer program product for managing operating system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |