Auxiliary Disk Image Patching Without Reboot
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for updating computer program code often require rebooting the computing device, disrupting its operation and causing inconvenience to users, especially for important patches like security updates.
Innovation Solution
The implementation of an auxiliary disk image that allows code aligned with the base operating system to be patched without rebooting, by applying updates to the auxiliary disk image while the base operating system continues to execute, using a virtual disk image for patching and reverse patching capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If code is patched by replacing existing code with updated code, then security updates and bug fixes are provided, but the computing device requires rebooting which interrupts operation
Solution Approach 1:
The patent divides the code storage into two separate locations: a base operating system volume containing the base code and an auxiliary disk image containing the updatable code. This segmentation allows the auxiliary code to be patched independently without affecting the base system, eliminating the need for reboots while maintaining security updates and bug fixes.
Solution Approach 2:
The auxiliary disk image acts as an intermediary layer between the base operating system and the updated code. It receives patches, processes them, and provides the updated code to the executing applications without requiring the base system to be restarted, thus mediating between update requirements and operational continuity.
2Productivity
If code is patched by replacing existing code, then updates are applied, but the device must be rebooted causing time loss
Solution Approach 1:
By separating the code into base system volume and auxiliary disk image, the patent enables independent patching of the auxiliary code. This eliminates the need to reboot the entire system for updates, thereby eliminating reboot time loss while maintaining continuous code updates and productivity.
Solution Approach 2:
The auxiliary disk image is prepared in advance with the capability to receive and store updated code. When updates are needed, the auxiliary image is patched before the next execution phase, allowing updates to be applied proactively without interrupting current operations or requiring future reboots.
3Adaptability or versatility
If the base operating system code is updated, then new features and fixes are provided, but the entire system must be rebooted
Solution Approach 1:
The patent segments the code base into immutable base operating system code and mutable auxiliary code. This allows the auxiliary code to be updated frequently with new features and fixes while the base system remains stable and running, providing adaptability without requiring system reboots or interrupting operations.
Data Source
AI summary
Aspects and features include maintaining at least one auxiliary disk image on a computing device. Certain code that is aligned with the base operating system of the computing device resides in and is executed from the auxiliary disk image. In one example, a computing device receives an update asset and uses it to patch the auxiliary disk image. The computing device executes the updated code from the patched disk image without rebooting or otherwise restarting the base operating system. The existing auxiliary disk image may be replaced with the patched disk image in response to a reboot or some other event, or while executing the code in the patched disk image from memory.