Data processing: software development – installation – and managem – Software upgrading or updating
Reexamination Certificate
1999-06-29
2002-11-05
Khatri, Anil (Department: 2122)
Data processing: software development, installation, and managem
Software upgrading or updating
C717S168000, C717S174000, C717S175000
Reexamination Certificate
active
06477703
ABSTRACT:
FIELD OF THE INVENTION
The present invention relates to methods and apparatus for selecting software patches on a computer operating system, and, more particularly, for selecting software patches for installation on an HP-UX operating system.
BACKGROUND OF THE INVENTION
The software portion of most computer systems includes both an operating system and a broad array of application programs, both of which are subject to regular modification. The release of a new version of a Microsoft operating system always makes headlines as it typically impacts existing application programs running on the computer system and may necessitate modification to operate properly. Additionally, no software program is perfect and the release of numerous software patches to fix specific problems, and the release of new versions to fix or upgrade major problems are the norm.
Between the release of new versions of a software product, minor modifications and “bug fixes” are typically made by the software developer in the form of software patches which are accessible for installation by users. There exists patch installation products that provide for identifying known patches as part of the Customer Operation Profile function in most computer operating systems. These prior solutions have the disadvantage of being very time consuming to use as they list every possible patch that could apply to a given system (sometimes more than 300) and require a manual sort through the list of patches to determine which patches are most relevant. A complete patch analysis takes approximately two to four hours. Prior solutions, for example ProPatch, provide a rough capability to target patches strictly according to a product/file set combination, however, patches are often required on items that reside in different areas. For instance, patching Omniback requires more than just patching the product itself, patches are required for commands, kernel, and file systems.
There exists a need for a high quality patch analysis tool that takes extensive knowledge of products, patches, and system-level knowledge.
A need also exists to provide a capacity for true grouping of patches according to product.
A need also exists to provide for the automatic recognition of the product version on a customer's systems, such that a user is not forced to figure out the version of the product and choose the appropriate patches.
It would be desirable and of considerable advantage to provide a patching tool that solves the problem of irrelevant patches, employs extensive knowledge, and is a true product-based patching tool by having the tool's user select from a list of products which are backed by sets of patches that have been researched for relevance to the product being patched. Further, such a patch tool could be advantageous if version smart, in that it can understand the version of information passed back such that version specific patches may be chosen, especially if the new patch tool provided an improvement in any of the following areas: reduction in time required to complete a patch analysis, smaller list of patches to choose from, patching performed according to how customers view their system (at the true product level) and the ability to research potential patches such that less knowledge is needed by the person performing the patch analysis.
SUMMARY OF THE INVENTION
The present invention is a patch selection tool providing a method for identifying software patches for installation on a computer system. Current versions of desired operating systems, software applications and patches installed or to be installed on the computer system are identified. A script is run on the computer system to create a file (called a PSIfile) of the actual operating system, software applications and patches, including versions, that are properly installed on the system. The PSIfile is uploaded into the patch tool and any installed patches which are bad are identified. The patch tool then compares the list of desired operating systems, software applications and patches to those actually installed as identified in the PSIfile. An initial list of recommended patches is generated by identifying those patches associated with the combination of the installed products and the validated list of datasheet selected products.
The initial list of patches is checked for patches that are missing dependent patches; and dependencies are added as necessary. The initial list is also checked against itself and against the list of installed patches to remove patches that are anticipated by newer versions of software that have already been installed or recommended. The list is also checked to make sure the recommended patches will execute upon installation. If there are bad patches that have not been resolved, the user is presented with a list of the bad patches, and is forced to resolve them before continuing. If the patch tool was already going to recommend a newer version of a bad patch, the new patch is given.
A final check list is checked against itself for patches that cause structural conflicts. Structural conflicts are presented to the user for further, manual intervention.
The patch tool user reviews the final list and can deselect any of the recommendations or manually add patches and re-analyze, download the list of patches into the Xpatch patch ordering tool, or the user may load the list of patches into an ongoing patch analysis.
Other aspects and advantages of the present invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the invention.
REFERENCES:
patent: 5357629 (1994-10-01), Dinnis et al.
patent: 5481713 (1996-01-01), Wetmore et al.
patent: 5678039 (1997-10-01), Hinks et al.
patent: 5797016 (1998-08-01), Chen et al.
patent: 5966540 (1999-10-01), Lister et al.
patent: 6071317 (2000-06-01), Nagal
patent: 6073214 (2000-06-01), Fawcett
patent: 6115646 (2000-09-01), Fiszman et al.
patent: 6135651 (2000-10-01), Leinfelder et al.
patent: 6161218 (2000-12-01), Taylor
patent: 6202207 (2001-03-01), Donohue
patent: 6289509 (2001-09-01), Kryloff
patent: 6327706 (2001-12-01), Amberg et al.
patent: 6338149 (2002-01-01), Ciccone, Jr. et al.
patent: 6347398 (2002-02-01), Parthasarathy et al.
Lyu et al, “A procedure based dynamic software update”, IEEE, pp 271-280, 2001.*
Ali, “Software patching in the SPC environment and its impact on switching system relaibility”, IEEE, pp 626-631, 1991.*
Hollingsworth et al, “Uisng content derived names for configuartion management”, ACM SSR, pp 104-109, 1997.*
Hicks et al, “Dynamic software updating”, ACM PLDI, pp 13-23, 2001.
Chan Kay
Macias Abbey
Marakovits Eric
Richards Linda
Ritzer Janet
Hewlett--Packard Company
Khatri Anil
Schuette Richard F.
LandOfFree
Software patch selection tool does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Software patch selection tool, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Software patch selection tool will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2937217