RPM Patch Packaging With File Mapping for Targeted Linux Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing RPM-based Linux systems require full application replacement for updates and patches, which is resource-intensive, especially in low-power environments, and lack traceability and record-keeping of changes.
Innovation Solution
Generate a diff of files to be patched and install it using an altered RPM mechanism with mapping, creating a patch RPM that applies patches to specific locations without rebuilding the entire RPM, enabling traceable and targeted patching.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full RPM packages are installed for updates, then system reliability is improved, but resource consumption increases
Solution Approach 1:
The patent segments the RPM package into two parts: a base package containing only the binary files and a separate patch package containing the mapping file and diff data. This allows the system to install only the necessary changes rather than the entire package, reducing resource consumption while maintaining the ability to reliably update the system.
Solution Approach 2:
The patent extracts the mapping file and patch data from the full RPM package to create a separate, lightweight patch package. This extraction enables targeted installation of only the changes needed, eliminating the need to transfer and process the entire base package again, thus reducing resource consumption while preserving system reliability.
2Reliability
If full RPM packages are installed for updates, then completeness of updates is improved, but installation time increases
Solution Approach 1:
By segmenting the update process into base package installation (done once) and subsequent patch applications, the patent enables rapid incremental updates. The mapping file efficiently directs the patch application process to only the necessary files, reducing installation time while ensuring completeness through the structured diff-based approach.
Solution Approach 2:
The mapping file is generated in advance during the patch creation process, containing pre-calculated information about where patches should be applied. This preliminary preparation eliminates the need for time-consuming analysis during installation, allowing the system to quickly apply only the necessary changes while maintaining update completeness.
3Ease of operation
If traditional RPM patching is used, then ease of operation is maintained, but traceability of changes is lost
Solution Approach 1:
The mapping file serves as an intermediary that bridges the traditional RPM installation process with traceability requirements. It contains structured information about which files are patched and where, enabling automatic generation of change logs and audit trails without complicating the installation process for users.
Solution Approach 2:
The patent implements feedback mechanisms where the mapping file and patch metadata are used to automatically record and report changes. This provides traceability information back to system administrators without requiring manual intervention, maintaining ease of operation while preventing loss of change information.
4Reliability
If full RPM packages are distributed, then availability of complete applications is improved, but distribution bandwidth consumption increases
Solution Approach 1:
The patent extracts only the essential patch data and mapping information from the full RPM package to create a compact patch package for distribution. This extraction dramatically reduces distribution bandwidth consumption while the base package remains available on the target system, ensuring availability of complete applications without repeated full-package distribution.
Solution Approach 2:
Instead of distributing full RPM packages again, the patent creates lightweight copies containing only the changes (diff data) and installation instructions (mapping file). These compact copies consume minimal bandwidth while the actual application files are copied from the existing installation on the target system, eliminating redundant data transfer.
Data Source
AI summary
Systems and methods for automated targeted patching of a target system. In one embodiment the present disclosure includes a method for compiling binary files from a source code package; running a diff tool to determine differences between the binary files and an application already installed on a target system; generating, based on the determined differences, a patch that includes at least one file to be installed on the target system; generating, a mapping file, the mapping file including information on where the at least one file will be installed on the target system; combining, the mapping file and the patch into a patch package; and installing the patch package on the target system.