Mounted Package File Systems for RAM-Constrained Software Installation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Installing software features on computing devices with limited memory, particularly those using RAM-based file systems, is impractical due to insufficient storage space, as conventional methods require copying all feature files into the file system, leaving some features unavailable.
Innovation Solution
A package file system is mounted onto a mount point in the target file system, with symbolic links created to feature files, allowing these files to remain in non-volatile memory without being physically stored on the target file system, thus reducing memory requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If software feature files are copied into the RAM-based file system, then the features become accessible to applications, but the limited RAM storage space is exhausted, preventing installation of additional features
Solution Approach 1:
The patent introduces a package manager as an intermediary component that manages software packages and their files. The package manager maintains a database of installed packages and coordinates file access between applications and the file system, enabling efficient space utilization in the RAM-based file system while maintaining feature accessibility.
Solution Approach 2:
The patent segments the file system into a RAM-based portion for actively used features and a non-volatile storage portion for storing package files. This segmentation allows the system to keep only necessary files in RAM while storing complete package archives on non-volatile storage, resolving the space constraint while maintaining accessibility.
2Adaptability or versatility
If all software feature files are stored in the RAM-based file system, then applications can access all features, but the computing device exceeds its memory capacity
Solution Approach 1:
The patent implements a dynamic file management system where files are moved between the RAM-based file system and non-volatile storage based on usage patterns. The package manager dynamically determines which package files to keep in RAM and which to store on non-volatile storage, optimizing the balance between feature availability and memory capacity utilization.
Solution Approach 2:
The patent changes the storage state parameter of package files from permanently resident in RAM to dynamically allocated between RAM and non-volatile storage. This parameter change allows the system to adapt memory allocation based on available capacity while maintaining the ability to access all features when needed.
3Speed
If the RAM-based file system is used to store package files, then fast access is achieved, but insufficient storage space prevents installation of complete software packages
Solution Approach 1:
The patent adds a spatial dimension to the storage architecture by introducing non-volatile storage as an additional layer beyond the RAM-based file system. This dimensional expansion provides abundant storage space for complete package files while maintaining fast access paths for actively used features through the RAM-based file system.
Solution Approach 2:
The patent creates a nested storage structure where the RAM-based file system is nested within a larger storage hierarchy that includes non-volatile storage. Package files are stored in the outer non-volatile storage layer, while actively accessed files are nested in the inner RAM-based file system layer, achieving both fast access and sufficient capacity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present disclosure describes a technique for installing extension packages on a target computing device. The extension package is downloaded onto the target device and stored on disk or other non-volatile storage (e.g., flash memory). The target device mounts a file system in the extension package onto a mount point on the file system of the target device. The target device runs an installation script for each feature in the extension package. The installation script generates information so that access to the feature file from non-volatile storage. Because the feature files that constitute a feature are not physically stored on the target file system, the feature files do not consume the storage space of the target file system.