OS Component Management via Symbolic Links for Storage Efficiency

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current operating systems lack efficient methods for managing multiple versions and components, leading to storage inefficiencies and difficulties in testing and rolling back to stable versions without duplicating files.

Innovation Solution

The system utilizes links (hard and symbolic) to shared storage locations for OS components, allowing multiple boot locations to access the same files, reducing storage needs and enabling easy switching between versions by setting the OS root directory.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple versions of OS components are stored in separate locations, then version testing and rollback capability are improved, but storage space consumption increases

Engineering Contradiction:

Improveversion testing and rollback capabilityVSAvoidstorage space consumption

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent uses symbolic links (a form of copying reference) to create multiple boot locations that point to the same OS component files. Instead of duplicating actual files, the system creates reference copies that allow multiple boot locations to access identical files, thereby enabling version testing and rollback without increasing actual storage consumption

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent merges multiple boot locations to share common OS component files through symbolic links. Multiple boot locations are combined at the file level, allowing them to share the same physical storage space while maintaining separate logical identities for testing different versions

Inventive Principle:

Principle #5Merging (Combining)

2Reliability

If OS components are updated to fix errors or add functionality, then system reliability and features are improved, but the complexity of managing multiple versions increases

Engineering Contradiction:

Improveerror fixing and functionality additionVSAvoidOS component version management

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the OS into multiple independent boot locations, each containing specific versions of OS components. This segmentation allows individual versions to be managed separately through symbolic links, reducing the complexity of managing multiple versions by organizing them into discrete, manageable units

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces symbolic links as intermediaries between boot locations and OS component files. These symbolic links act as mediators that simplify version management by providing a uniform interface to access different versions without exposing the underlying complexity of file duplication or management

Inventive Principle:

Principle #24Intermediary (Mediator)

3Quantity of substance

If file duplication is avoided by using shared storage locations, then storage efficiency is improved, but the ability to test different versions independently is worsened

Engineering Contradiction:

Improvestorage efficiencyVSAvoidindependent version testing

Core Design Contradiction:

Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The patent uses symbolic links to create reference copies that enable independent version testing without actual file duplication. Each boot location has its own symbolic link configuration that points to specific file versions, allowing independent testing while sharing underlying files to maintain storage efficiency

Inventive Principle:

Principle #26Copying

Data Source

PatentUS9141385B2Managing operating system components

Publication Date: 2015.09.22 RED HAT INC

AI summary

A plurality of operating system (OS) components is stored in a storage location on a computing device. A user may selected a set of OS components to use when the computing device boots. A boot location is created and links to the set of OS components are stored in the boot location. The computing device may boot using any one of a plurality of boot locations.