CN105389187B - System updating method - Google Patents
System updating method Download PDFInfo
- Publication number
- CN105389187B CN105389187B CN201510844668.9A CN201510844668A CN105389187B CN 105389187 B CN105389187 B CN 105389187B CN 201510844668 A CN201510844668 A CN 201510844668A CN 105389187 B CN105389187 B CN 105389187B
- Authority
- CN
- China
- Prior art keywords
- update
- client
- package
- system update
- update package
- 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.)
- Active
Links
Images
Abstract
The invention discloses a system updating method, belonging to the technical field of operating system maintenance; the method comprises the following steps: step S1, the client monitors whether the server issues a new system update package, and goes to step S2 when the server issues the new system update package; step S2, the client downloads the system update package from the server; step S3, the client detects the application software and isolates the application software; step S4, the client uses the system update package to update the operation system; step S5, the client releases the isolation of the application software, and determines whether the application software can normally run: if the operation can be normally carried out, the operation is quitted; if the software can not run normally, the application software is marked to prompt the user to pay attention, and then the software exits. The beneficial effects of the above technical scheme are: the problem that the software defined by a user is upgraded together when the operating system is upgraded integrally is avoided, the transparency of the upgrading process of the operating system is realized, and the use experience of the user is improved.
Description
Technical Field
The invention relates to the technical field of operating system maintenance, in particular to a system updating method.
Background
With the rapid development of the Linux operating system and the continuous update of the application software carried by the Linux operating system, people have more and more frequent requirements on the Linux operating system for system update. However, the existing version updating method for the Linux operating system generally has the following problems:
1) for certain versions of the Linux operating system, some user-defined application software in the operating system is generally subjected to update operations suitable for the updated version at the same time, and the update operations may not be desired by the user;
2) in the version updating process of the Linux operating system, the up-down dependency relationship of an installation package is often encountered, and the updating process may be adversely affected;
3) the user cannot know the specific content of the version update of the Linux operating system and the update information such as the update mode once, so that the use experience of the user is reduced.
Disclosure of Invention
According to the problems in the prior art, a technical scheme of a system updating method is provided, which aims to solve the problem that the software defined by a user is updated together when the operating system is updated integrally, realize the transparency of the updating process of the operating system and improve the use experience of the user.
The technical scheme specifically comprises the following steps:
a system updating method comprises a server and a client, wherein the server is remotely connected with the client;
the server is used for storing the system update package, and the client is provided with user-defined application software, and the method further comprises the following steps:
step S1, the client monitors whether the server issues the new system update package, and goes to step S2 when the server issues the new system update package;
step S2, the client downloads the system update package from the server;
step S3, the client detects the application software and isolates the application software;
step S4, the client updates the operating system by adopting the system update package;
step S5, the client releases the isolation of the application software, and determines whether the application software can normally run:
if the operation can be normally carried out, the operation is quitted;
and if the application software cannot normally run, marking the application software to prompt the user to pay attention, and then quitting.
Preferably, the method for updating the system, wherein the system update package includes:
a system update file for performing a system update; and
a system update description file for describing the system update.
Preferably, the system updating method includes:
sequence information indicating an update order of the system update package;
type information indicating an update type of the system update package;
architecture information for representing an operating system architecture for which the system update package is intended;
release information indicating a release date of the system update package;
attribute information for representing an attribute description of the system update package;
the early-stage script information is used for indicating whether the system updating package contains the script which needs to be executed before the system updating;
the later-stage script information is used for indicating whether the script which needs to be executed after the system updating exists in the system updating package; and
re-information indicating whether a reboot is required after the system update made for the system update package.
Preferably, the system updating method, wherein the type information includes:
first update information representing the update type that the system update package is associated with a bug fix; and/or
Second update information for indicating the update type that the system update package is associated with a system upgrade; and/or
Third update information for indicating that the system update package is associated with the update type of a secure update.
Preferably, in the method for updating a system, before the step S4 is executed, when the client updates the operating system by using the system update package, the system update description file is displayed on a display screen of the client for a user to view.
Preferably, before executing step S4, the client displays the type information on a display screen of the client for a user to view.
Preferably, in the method for updating a system, before executing the step S1, it is first determined whether the client starts an automatic update function:
if the automatic update function is activated, continuing to execute the step S1;
if the automatic update function is not started, the client performs the step S2 by turning to the execution according to an instruction input from the outside.
Preferably, the method for updating the system includes setting a monitoring unit in the client to monitor the progress of downloading the system update package by the client and/or the progress of updating the system by the client.
Preferably, the method for updating the system is characterized in that the client runs based on a Linux operating system.
The beneficial effects of the above technical scheme are: the method for updating the system can solve the problem that the software defined by a user is updated together when the operating system is integrally updated, realizes the transparency of the updating process of the operating system and improves the use experience of the user.
Drawings
FIG. 1 is a flow chart illustrating a method for system update according to a preferred embodiment of the present invention.
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. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict.
The invention is further described with reference to the following drawings and specific examples, which are not intended to be limiting.
In the prior art, there are various versions of an operating system, taking a Linux operating system as an example, a more common update method is to use a software Package management tool to update and upgrade the system, wherein RPM (RPM Package Manager) and DPKG (Debian Package Manager) are the two most common types of software Package management tools.
RPM was originally named as Redhat Package Manager, originally implemented by Redhat corporation, and was subsequently accepted by the GNU (GNU is Not Unix, the leather project) open source operating system and is known as a well-established software standard for many Linux systems. Since this software management approach is very convenient, its package management mode is similar to "add/delete program" under windows. Each RPM file (software package file ending with RPM) contains a compiled binary executable file, namely a software source code file is compiled, installed and then packaged, and the software source code file is similar to the 'exe' file in a windows program installation package, and finally the installation can be completed by executing the file.
The drawback of the RPM software package management method is that it is highly dependent on the operating system environment, which requires that the installation environment of the RPM package must be consistent or equivalent to the environment when the RPM package is packaged, and also needs to satisfy the dependency relationship with some software packages of the system when installed.
In contrast, DPKG software package management tools are not responsible for checking the dependencies of software packages, and thus DPKG is typically used to install a single software package.
However, DPKG also has some drawbacks, in particular: firstly, the software package can not be actively acquired from the mirror image site; secondly, when the software package is installed, the dependency relationship of the software package cannot be checked.
In summary, the software updating methods for the Linux operating system in the prior art all have some drawbacks.
In the preferred embodiment of the present invention, based on the above problems in the prior art, a method for updating a system is provided, which is suitable for a Linux operating system and includes a server and a client, wherein the server is remotely connected to the client; the server side is used for storing the system update package, and the client side is provided with user-defined application software.
Specifically, in the method, the server and the client both run based on the Linux operating system, and a system update package is stored in the server, and is usually guaranteed to be the latest system version associated with the Linux operating system, and then the client also has application software which is customized by a user and is suitable for the Linux operating system.
In a preferred embodiment of the present invention, as shown in fig. 1, the method for updating the system specifically includes:
step S1, the client monitors whether the server issues a new system update package, and goes to step S2 when the server issues the new system update package;
step S2, the client downloads the system update package from the server;
step S3, the client detects the application software and isolates the application software;
step S4, the client uses the system update package to update the operation system;
step S5, the client releases the isolation of the application software, and determines whether the application software can normally run:
if the operation can be normally carried out, the operation is quitted;
if the software can not run normally, the application software is marked to prompt the user to pay attention, and then the software exits.
In one embodiment, the client first monitors whether the server issues a new system update package: if yes, the step is shifted to step S2, if not, the monitoring is continued until the server side is monitored to issue a new system update package, and the step is shifted to step S2;
subsequently, in this embodiment, the client downloads the system update package from the server, and detects whether the application software defined by the user exists in the Linux operating system of the client according to the setting of the system: if the detected application software exists, the client performs isolation processing on the detected application software, for example, the running files and the registry files related to the software are placed in a preset isolation area for storage, so as to avoid the next system updating process from updating or changing the application software; if not, the client side continues to update the system.
Finally, in this embodiment, after the client updates the Linux operating system with the system update package, the client releases the application software from the isolation area, that is, the application software is isolated, and the previously isolated application software is respectively verified in the updated Linux operating system to verify whether the application software can normally run in the updated Linux operating system:
if the version can normally run, the version updating is finished, and the operation is quitted;
if the software cannot normally run, the application software is marked to prompt the user to pay attention, and then the software exits. For example, a list of applications that cannot function properly (i.e., applications with markers) is displayed on the display screen of the client.
In a preferred embodiment of the present invention, a detecting unit may be disposed in the client, and the detecting unit may be configured to provide dbus service of the system, that is, responsible for polling in the background to check whether there is a newly issued system update package at the server, for example, to monitor whether there is a signal indicating a change in the network service status, and to check and download the newly issued system update package when the network service status changes.
In a preferred embodiment of the present invention, the system update package includes:
a system update file for performing a system update; and
and the system update description file is used for describing the system update.
Specifically, in a preferred embodiment of the present invention, the system update file may be automatically generated according to the update. The system update file is composed of a series of software management files (e.g., RPM files), a system update description xml file, and pre-update and post-update scripts. In this embodiment, the system update package may be in a tar.
The following items may be defined in the system update file:
sequence information for indicating an update order of the system update package, for example, ID information of the update package, a unique ID for indicating each update package, and IDs of different update packages are sequentially increased to indicate continuous update of the system version;
type information for indicating an update type of the system update package, for example, the type information may be set as a first update type of bug (bug) repair, a second update type of system upgrade, and a third update type of security update;
the architecture information is used for representing the operating system architecture for which the system update package is specific, namely the system update package, for example, the system update package supports one or more of x86_64/x 86/loongson/sw/mips/alpha/ppc/ppcle/arm;
release information for indicating a release date of the system update package, that is, a release date of the system update package, may be in a format of "< year > - < month > - < day >" or other format suitable for an application;
the attribute information used for representing the attribute description of the system update package, that is, the simple description associated with the system update package of this time, may be implemented in english, and may also include some simple descriptions associated with the system update package of this time, such as "what problem is repaired", each of which is described as an item. If the information has a multi-language support requirement, a node attribute xml is required to be used, wherein lang is ═ Locale >;
the early-stage script information is used for indicating whether a script which needs to be executed before the system updating exists in the system updating package;
the later-stage script information is used for indicating whether the system updating package contains the script which needs to be executed after the system updating; and
a restart information indicating whether or not a restart is required after a system update performed with respect to the system update package;
package file information: which is used to represent all software management files (e.g., RPM files) contained in the update package of the present system. Each node is used to describe a software management file, and generally consists of two parts, namely a filename and md5 sum.
Accordingly, in a preferred embodiment of the present invention, the system update description file is mainly provided for the update client to obtain the description file of the update information, and the content of the system update description file may be composed of an update.
In a preferred embodiment of the present invention, the system update package may be downloaded by the client through the web server.
In a preferred embodiment of the present invention, before the step S4 is executed, when the client updates the operating system by using the system update package, the system update description file is displayed on the display screen of the client for the user to view. That is, when the client performs a system update, some update information associated with the system update package is displayed on the display screen of the client and provided for the user to view.
Accordingly, in a preferred embodiment of the present invention, before the step S4 is executed, the client may further display the type information on a display screen of the client for a user to view. Specifically, the user may view the update type of the system update, such as bug repair, system upgrade, or security update, and complete update information associated with the update type on the display screen, so as to grasp specific information of the system update.
Accordingly, in a preferred embodiment of the present invention, a monitoring unit is disposed in the client to monitor the progress of downloading the system update package and/or the progress of performing the system update by the client. Specifically, the monitoring unit may start monitoring from the start of downloading the system update package by the client until the client completes the system update, and the monitored content may include the following:
downloading progress of the update package of the downloading system;
the installation system updates the installation progress of the package;
the final result of the system updating (updating success or updating failure) at this time;
whether the system needs to be restarted after being updated or not is provided for a user to select a manual restarting scheme or an automatic restarting scheme.
In other embodiments of the present invention, the monitoring unit may also be used to monitor other information in the system updating process, which is not described herein again.
In a preferred embodiment of the present invention, before executing the step S1, it is first determined whether the client starts the automatic update function:
if the automatic update function is activated, continue to execute step S1;
if the automatic update function is not started, the client performs the step S2 by turning to the execution according to an instruction input from the outside.
Specifically, in a preferred embodiment of the present invention, the user can control the update mode by setting the update switch unit:
if the update mode of the client is automatic update under the control of the update switch unit, the client directly executes the step S1;
if the update mode of the client is not automatic update, for example, manual update, according to the control of the update switch unit, the client does not automatically monitor whether the server issues a new system update package, but directly downloads a corresponding system update package from the server according to an instruction issued by the user, that is, the user controls the time for updating the system.
In summary, in the technical solution of the present invention, after the client downloads the system update package from the server, the client isolates the user-defined application software in the client, then performs system update according to the downloaded system update package, and after the update is finished, removes the isolation of the application software, and verifies whether the application software can normally work in the updated new operating system: if yes, quitting; if not, the applications are marked to alert the user and then exited.
In a preferred embodiment of the present invention, the server may generate and verify the system update package according to the following manner:
the server firstly judges which of the following processes is executed according to the input of the command line:
1) if the command line input is used for creating a system updating template, the server side creates an update folder and a packages folder, and further creates an update. ini template;
2) if the command line input is to create a system update package, the server side firstly reads a user configuration file and scans a software package, then core data related to the system update package is generated, and a description file of update. Subsequently, the system files the files to form a system update package and compresses and paints them to package into a special format; finally, calculating the MD5 value of the system update package and generating a final system update package with a verification function;
3) if the command line input is a verification system update package, the server side firstly reads the system update package to be verified and decompresses the system update package, then reads a software management file (such as an RPM file) and an MD5 value in the system update package, and finally completes verification according to the MD5 value.
While the invention has been described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention.
Claims (9)
1. The system updating method is characterized by comprising a server and a client, wherein the server is remotely connected with the client;
the server is used for storing the system update package, and the client is provided with user-defined application software, and the method further comprises the following steps:
step S1, the client monitors whether the server issues the new system update package, and goes to step S2 when the server issues the new system update package;
step S2, the client downloads the system update package from the server;
step S3, the client detects the application software and isolates the application software;
step S4, the client updates the operating system by adopting the system update package;
step S5, the client releases the isolation of the application software, and determines whether the application software can normally run:
if the operation can be normally carried out, the operation is quitted;
if the application software can not normally run, marking the application software to prompt a user to pay attention, and then quitting;
the method for generating and verifying the system update package by the server specifically comprises the following steps:
the server firstly judges which process is executed according to the input of the command line:
if the input of the command line is to create a system update template, the server creates an update folder and a packages folder, and further creates an update.ini template, wherein a system update file for updating the system in the system update package is configured according to the update.ini template so as to automatically generate the system update file;
if the input of the command line is to create a system update package, the server side firstly reads a user configuration file and scans a software package corresponding to the system update package, then core data associated with the system update package is generated, and a description file of update. Subsequently, the files are filed to form the system update package and compressed and smeared to be packaged into a special format; finally, calculating the MD5 value of the system update package and generating a final system update package with a verification function;
if the input of the command line is to verify the system update package, the server side firstly reads the system update package to be verified and decompresses the system update package, then reads the software management file and the MD5 value in the system update package, and finally completes verification according to the MD5 value.
2. The method of system updating of claim 1, wherein the system update package comprises:
a system update file for performing a system update; and
a system update description file for describing the system update.
3. The method of system updating according to claim 2, wherein the system update file comprises:
sequence information indicating an update order of the system update package;
type information indicating an update type of the system update package;
architecture information for representing an operating system architecture for which the system update package is intended;
release information indicating a release date of the system update package;
attribute information for representing an attribute description of the system update package;
the early-stage script information is used for indicating whether the system updating package contains the script which needs to be executed before the system updating;
the later-stage script information is used for indicating whether the script which needs to be executed after the system updating exists in the system updating package; and
re-information indicating whether a reboot is required after the system update made for the system update package.
4. The method of system updating of claim 3, wherein the type information comprises:
first update information representing the update type that the system update package is associated with a bug fix; and/or
Second update information for indicating the update type that the system update package is associated with a system upgrade; and/or
Third update information for indicating that the system update package is associated with the update type of a secure update.
5. The method for updating a system according to claim 2, wherein before the step S4, when the client updates an operating system using the system update package, the system update description file is displayed on a display screen of the client for a user to view.
6. The method for updating a system according to claim 3, wherein before the step S4, the client displays the type information on a display screen of the client for a user to view.
7. The method for updating a system according to claim 1, wherein before executing the step S1, it is first determined whether the client starts an automatic update function:
if the automatic update function is activated, continuing to execute the step S1;
if the automatic update function is not started, the client performs the step S2 by turning to the execution according to an instruction input from the outside.
8. The method for updating a system according to claim 1, wherein a monitoring unit is disposed in the client for monitoring a progress of the client in downloading the system update package and/or a progress of the client in performing the system update.
9. The method of system updating of claim 1, wherein the client runs based on a Linux operating system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510844668.9A CN105389187B (en) | 2015-11-26 | 2015-11-26 | System updating method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510844668.9A CN105389187B (en) | 2015-11-26 | 2015-11-26 | System updating method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105389187A CN105389187A (en) | 2016-03-09 |
| CN105389187B true CN105389187B (en) | 2021-10-26 |
Family
ID=55421494
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510844668.9A Active CN105389187B (en) | 2015-11-26 | 2015-11-26 | System updating method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105389187B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106648678B (en) * | 2016-12-28 | 2020-08-18 | 北京奇虎科技有限公司 | System update control method and device |
| CN108021427A (en) * | 2017-11-23 | 2018-05-11 | 国家电网公司 | Information system deployment and updating management method based on Docker |
| CN109976794B (en) * | 2019-03-31 | 2021-02-19 | 联想(北京)有限公司 | Updating method, updating system and electronic equipment |
| CN111625257B (en) * | 2020-05-25 | 2023-05-23 | 泰康保险集团股份有限公司 | Service platform upgrading method, system, equipment and storage medium |
| CN114003264B (en) * | 2021-12-31 | 2022-05-10 | 麒麟软件有限公司 | Linux operating system upgrading method |
| CN114398065B (en) * | 2022-03-24 | 2022-07-08 | Tcl通讯科技（成都）有限公司 | Micro front-end system updating method and device, electronic equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101945135A (en) * | 2010-09-20 | 2011-01-12 | 中兴通讯股份有限公司 | Method and system for upgrading widget system |
| CN102184111A (en) * | 2011-04-29 | 2011-09-14 | 杭州海康威视数字技术股份有限公司 | Online upgrade method for operating system and device with operating system |
| CN102662647A (en) * | 2012-03-01 | 2012-09-12 | 中标软件有限公司 | Lunix operating system and security update method of same |
| CN103164232A (en) * | 2011-12-08 | 2013-06-19 | 腾讯科技（深圳）有限公司 | Method and system of updating intelligent terminal operating system and computer |
| CN103957244A (en) * | 2014-04-21 | 2014-07-30 | 惠州市新思为电子科技有限公司 | Remote program upgrading method and server |
| CN104484194A (en) * | 2014-11-24 | 2015-04-01 | 东软集团股份有限公司 | Method and device for system updating of vehicle-mounted intelligent terminal |
| CN104572229A (en) * | 2015-02-12 | 2015-04-29 | 西安诺瓦电子科技有限公司 | Firmware upgrade method and firmware upgrade device for embedded system |
-
2015
- 2015-11-26 CN CN201510844668.9A patent/CN105389187B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101945135A (en) * | 2010-09-20 | 2011-01-12 | 中兴通讯股份有限公司 | Method and system for upgrading widget system |
| CN102184111A (en) * | 2011-04-29 | 2011-09-14 | 杭州海康威视数字技术股份有限公司 | Online upgrade method for operating system and device with operating system |
| CN103164232A (en) * | 2011-12-08 | 2013-06-19 | 腾讯科技（深圳）有限公司 | Method and system of updating intelligent terminal operating system and computer |
| CN102662647A (en) * | 2012-03-01 | 2012-09-12 | 中标软件有限公司 | Lunix operating system and security update method of same |
| CN103957244A (en) * | 2014-04-21 | 2014-07-30 | 惠州市新思为电子科技有限公司 | Remote program upgrading method and server |
| CN104484194A (en) * | 2014-11-24 | 2015-04-01 | 东软集团股份有限公司 | Method and device for system updating of vehicle-mounted intelligent terminal |
| CN104572229A (en) * | 2015-02-12 | 2015-04-29 | 西安诺瓦电子科技有限公司 | Firmware upgrade method and firmware upgrade device for embedded system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105389187A (en) | 2016-03-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105389187B (en) | System updating method | |
| US8261253B2 (en) | Method for restoring software applications on desktop computers | |
| US10114637B1 (en) | Automatically updating a shared project build platform | |
| US10579966B1 (en) | Adapting a shared project build platform to a developer plugin | |
| US9146727B2 (en) | Automatic upgrade of virtual appliances | |
| US20040181790A1 (en) | System and method for maintaining installed software compliance with build standards | |
| CN108399083B (en) | System deployment method, device, electronic equipment and storage medium | |
| US8938735B2 (en) | Bootstrapper and software download manager | |
| US9063819B2 (en) | Extensible patch management | |
| US20140201726A1 (en) | Updating firmware compatibility data | |
| WO2005020089A1 (en) | Servicing a component-base software product | |
| US10747523B2 (en) | Methods of updating firmware components, computer systems and memory apparatus | |
| JP2001356912A (en) | Install/update/uninstall system of software | |
| CN110597544A (en) | Software system upgrading method and device | |
| US10761830B2 (en) | Method for installing and updating software programs, corresponding server and software package | |
| CN112256283A (en) | Application version control method and device for Android equipment | |
| CN116643761A (en) | Customized mirror image manufacturing and deploying method, device, terminal and medium | |
| CN110647343B (en) | OpenPower server and system deployment method thereof | |
| CN107315602B (en) | Application program upgrading method and terminal | |
| WO2001093021A2 (en) | A virtual system configurator for client systems | |
| CN115544521B (en) | Method and device for generating checksum of offline installation file | |
| US20100153942A1 (en) | Method and a system for delivering latest hotfixes with a support package stack | |
| US9477447B1 (en) | Semantic representations of software extensions | |
| CN117891478A (en) | Application program upgrading method, device, equipment and storage medium | |
| CN115291925A (en) | BMC upgrading method, system, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |