Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method comprising: receiving, at a host device, configuration data that corresponds to a configuration of a first instance of an operating system executed by a client device, the configuration data including at least one modification to the first instance of the operating system introduced by the client device during execution of the first instance of the operating system by the client device; storing the configuration data in a datastore that is located outside of a file system of the host device; receiving, at a second instance of the operating system executing on the host device, a request to load a file system from nonvolatile storage of the host device into volatile memory of the client device; in response to receiving the request, retrieving information corresponding to one or more instances of the operating system that have been checked out; determining, using the information and by the second instance of the operating system, that an instance of the operating system of the one or more instances of the operating system is not executing on the client device; in response to determining that an instance of the operating system of the one or more instances of the operating system is not executing on the client device: retrieving, by the host device, the configuration data from a datastore, the configuration data including the at least one modification; and configuring, by the host device, a particular instance of the operating system of the one or more instances of the operating system in accordance with the configuration data; and facilitating, by the host device, loading of the file system into the volatile memory of the client device, wherein the particular instance of the operating system of the one or more instances of the operating system is executing while the file system is loaded on the client device.
2. The method of claim 1 , further comprising: receiving, by the host device, an update request to update the configuration data for the particular instance of the operating system; and updating, by the host device, the configuration data for the particular instance of the operating system in the datastore located outside of the file system.
This invention relates to managing configuration data for operating system instances in a computing environment. The problem addressed is the need to efficiently update and maintain configuration data for operating system instances without disrupting the file system or requiring system reboots. The solution involves a host device that manages configuration data for multiple operating system instances, where the configuration data is stored in a datastore separate from the file system. This allows for centralized management and updates without affecting the file system's integrity or performance. The method includes receiving an update request to modify the configuration data for a specific operating system instance. Upon receiving the request, the host device updates the configuration data in the external datastore. This approach ensures that configuration changes are applied dynamically without requiring the operating system instance to be restarted or the file system to be modified. The external datastore provides a persistent and isolated storage location for configuration data, enabling efficient updates and reducing the risk of conflicts or corruption within the file system. This method is particularly useful in environments where multiple operating system instances need to be managed with minimal downtime and maximum reliability.
3. The method of claim 2 , further comprising: facilitating, by the host device, termination of the particular instance of the operating system and the file system on the client device, wherein the configuration data is maintained in the datastore during termination of the particular instance of the operating system and the file system on the client device.
This invention relates to a system for managing operating system instances and file systems on client devices, particularly in environments where multiple instances may be dynamically created, used, and terminated. The problem addressed is ensuring data persistence and system integrity when operating system instances and associated file systems are terminated, while maintaining configuration data in a centralized datastore. The system involves a host device that manages the lifecycle of operating system instances on client devices. When a particular instance of an operating system and its associated file system is terminated on a client device, the host device facilitates this termination process. During termination, the configuration data associated with the instance is preserved in a datastore, ensuring that the data remains available for future use or reference. This allows for seamless transitions between different operating system instances without losing critical configuration settings. The host device may also handle the creation and management of these instances, ensuring that each instance operates independently while maintaining access to shared resources. The datastore serves as a persistent storage location for configuration data, allowing the system to maintain consistency across multiple instances and client devices. This approach is particularly useful in environments where multiple users or applications require isolated operating environments, such as virtualization or cloud computing scenarios. The invention ensures that configuration data remains intact even when individual instances are terminated, improving system reliability and user experience.
4. The method of claim 3 , further comprising: receiving, at the second instance of the operating system of the host device, a reload request to reload the file system into the volatile memory of the client device; in response to receiving the reload request, retrieving, by the host device, the configuration data from the datastore located outside of the file system; configuring, by the host device, a new instance of the operating system in accordance with the configuration data; and facilitating, by the host device, reloading of the file system into the volatile memory of the client device, wherein the new instance of the operating system is executing while the file system is reloaded on the client device.
This invention relates to a system for managing file system reloading in a computing environment where a host device controls a client device. The problem addressed is ensuring continuous operation of an operating system while reloading a file system into the volatile memory of a client device, avoiding downtime or disruptions. The solution involves a host device running multiple instances of an operating system, where one instance manages the client device while another handles file system reloading. When a reload request is received, the host device retrieves configuration data from an external datastore, configures a new operating system instance using this data, and facilitates the file system reload into the client device's volatile memory. The new operating system instance remains active during the reload process, maintaining system functionality. The configuration data ensures the new instance is properly set up, while the external datastore prevents data loss or corruption during the reload. This approach allows seamless file system updates without interrupting ongoing operations.
5. The method of claim 1 , wherein the datastore is nonvolatile.
A system and method for data storage and retrieval involves a datastore that retains data even when power is removed, ensuring persistence across system reboots or power failures. The datastore is designed to store and manage data in a way that maintains integrity and availability, addressing challenges in systems where data loss or corruption can occur during power interruptions. The method includes writing data to the datastore, where the data is stored in a nonvolatile manner, meaning it is not lost when power is disconnected. This ensures that critical information remains accessible and reliable over time. The system may also include mechanisms for error detection and correction to further enhance data reliability. The nonvolatile datastore can be implemented using technologies such as flash memory, solid-state drives, or other persistent storage media. The method ensures that data written to the datastore remains intact and retrievable, even in the event of unexpected power loss or system shutdowns. This approach is particularly useful in applications where data integrity and persistence are critical, such as financial systems, medical devices, or industrial control systems. The system may also include additional features for optimizing storage efficiency, such as compression or deduplication, while maintaining the nonvolatile nature of the datastore.
6. The method of claim 1 , wherein the datastore is located in the nonvolatile storage of the host device.
A system and method for managing data storage in a host device involves storing data in a nonvolatile storage medium of the host device. The method includes receiving data from a client device, processing the data to determine storage requirements, and storing the data in a datastore located within the nonvolatile storage of the host device. The datastore is configured to persistently retain the data even when the host device is powered off. The method further includes managing access to the datastore, ensuring data integrity, and optimizing storage efficiency. The system may include a host device with nonvolatile storage, a client device for transmitting data, and a communication interface for data transfer. The datastore may be structured to support fast retrieval and secure storage, with mechanisms to prevent data corruption and unauthorized access. The method may also include monitoring storage capacity and performing maintenance operations to maintain optimal performance. This approach ensures reliable data storage and retrieval while leveraging the host device's existing nonvolatile storage capabilities.
7. The method of claim 1 , wherein the client device is a diskless system.
A diskless client device system is disclosed for managing and executing applications in a networked computing environment. The system addresses the challenge of efficiently running applications on devices without local storage, ensuring seamless performance and data accessibility. The diskless client device operates by connecting to a remote server or storage system to access necessary software and data, eliminating the need for local storage hardware. This approach reduces hardware costs, simplifies maintenance, and enhances security by centralizing data storage. The system includes a client device configured to communicate with a remote server, where the server hosts the operating system, applications, and user data. The client device retrieves and executes these resources dynamically, ensuring real-time access without local storage dependencies. The method involves initializing the client device, establishing a connection to the remote server, and loading the required software and data from the server. The system may also include mechanisms for caching frequently accessed data locally to improve performance while maintaining the diskless architecture. This solution is particularly useful in environments where multiple users require access to the same applications and data, such as in enterprise or educational settings. The diskless design ensures consistent software versions, simplifies updates, and reduces the risk of data loss or corruption.
8. A computer-program product tangibly embodied in a non-transitory machine-readable storage medium of a host device, including instructions that, when executed by one or more processors, cause the one or more processors to: receive configuration data that corresponds to a configuration of a first instance of an operating system executed by a client device, the configuration data including at least one modification to the first instance of the operating system introduced by the client device during execution of the first instance of the operating system by the client device; store the configuration data in a datastore that is located outside of a file system of the host device; receive, at a second instance of the operating system executing on the host device, a request to load a file system from nonvolatile storage of the host device into volatile memory of the client device; in response to receiving the request, retrieving information corresponding to one or more instances of the operating system that have been checked out; determine, by the second instance of the operating system and using the information, that an instance of the operating system of the one or more instances of the operating system is not executing on the client device; in response to determining that an instance of the operating system of the one or more instances of the operating system is not executing on the client device: retrieve, by the host device, the configuration data from the datastore, the configuration data including the at least one modification; and configure, by the host device, a particular instance of the operating system of the one or more instances of the operating system in accordance with the configuration data; and facilitate, by the host device, loading of the file system into the volatile memory of the client device, wherein the particular instance of the operating system of the one or more instances of the operating system is executing while the file system is loaded on the client device.
This invention relates to a system for managing operating system configurations in a host device to ensure consistent user environments across multiple instances. The problem addressed is maintaining user-specific modifications to an operating system when loading file systems into different client devices, ensuring that customizations persist without manual reconfiguration. The system involves a host device that stores configuration data for an operating system instance executed by a client device. This data includes user-introduced modifications, such as settings, installed applications, or other customizations. The configuration data is stored externally, outside the host device's file system, to prevent loss or corruption during file system operations. When a client device requests to load a file system from the host device's nonvolatile storage into its volatile memory, the host device checks if any operating system instances are already running on the client. If none are active, the host retrieves the stored configuration data and applies it to a new instance of the operating system. This ensures the new instance reflects the user's previous modifications. The file system is then loaded into the client device's memory while the configured operating system instance executes, maintaining consistency with prior configurations. This approach automates the preservation of user-specific operating system states, reducing setup time and ensuring a seamless experience across multiple sessions or devices.
9. The computer-program product of claim 8 , wherein the instructions further cause the one or more processors to: receive, by the host device, an update request to update the configuration data for the particular instance of the operating system; and update, by the host device, the configuration data for the particular instance of the operating system in the datastore located outside of the file system.
This invention relates to a computer-program product for managing configuration data of an operating system instance in a virtualized or containerized environment. The problem addressed is the inefficiency and complexity of updating configuration data stored within a file system, which can lead to inconsistencies, performance overhead, and difficulties in maintaining version control. The invention provides a solution by storing configuration data for an instance of an operating system in a datastore located outside the file system. This external datastore allows for centralized management, easier updates, and improved performance. The host device receives an update request to modify the configuration data for a specific instance of the operating system. Upon receiving the request, the host device updates the configuration data in the external datastore, ensuring that changes are applied without altering the file system structure. This approach simplifies configuration management, reduces the risk of corruption, and enables faster updates by avoiding file system operations. The system may also include mechanisms to validate the configuration data before applying updates, ensuring system stability. The invention is particularly useful in environments where multiple instances of operating systems need to be managed efficiently, such as cloud computing or virtualized server environments.
10. The computer-program product of claim 9 , wherein the instructions further cause the one or more processors to: facilitate, by the host device, termination of the particular instance of the operating system and the file system on the client device, wherein the configuration data is maintained in the datastore during termination of the particular instance of the operating system and the file system on the client device.
This invention relates to a computer-program product for managing operating system (OS) and file system instances on a client device, particularly in scenarios where the OS and file system are terminated while preserving configuration data. The technology addresses the challenge of maintaining system configuration data when an OS or file system instance is shut down, ensuring that the data remains intact for future use. The system involves a host device that interacts with a client device running an OS and file system instance. When termination of the OS and file system instance is initiated, the host device ensures that configuration data stored in a datastore is preserved. This allows the client device to later restart the OS and file system with the same configuration, avoiding data loss or manual reconfiguration. The datastore acts as a persistent storage location, independent of the OS and file system lifecycle, ensuring configuration data remains accessible even after termination. The solution is particularly useful in environments where OS and file system instances are frequently created, modified, or terminated, such as in virtualized or cloud computing scenarios. By maintaining configuration data in a separate datastore, the system enables seamless transitions between different OS and file system instances while preserving critical settings and configurations. This approach enhances system reliability and reduces administrative overhead.
11. The computer-program product of claim 10 , further comprising: receiving, at the second instance of the operating system of the host device, a reload request to reload the file system into the volatile memory of the client device; in response to receiving the reload request, retrieving, by the host device, the configuration data from the datastore located outside of the file system; configuring, by the host device, a new instance of the operating system in accordance with the configuration data; and facilitating, by the host device, reloading of the file system into the volatile memory of the client device, wherein the a new instance of the operating system is executing while the file system is reloaded on the client device.
This invention relates to a system for managing file systems in a computing environment where a host device controls the operation of a client device. The problem addressed is the need to reload a file system into the volatile memory of a client device while ensuring continuous operation of the operating system. The solution involves a host device that receives a reload request to reload the file system into the client device's volatile memory. In response, the host device retrieves configuration data from a datastore external to the file system. Using this data, the host device configures a new instance of the operating system. While this new instance is executing, the host device facilitates the reloading of the file system into the client device's volatile memory. This ensures that the operating system remains functional during the file system reload process, preventing downtime or disruptions. The system leverages a secondary instance of the operating system on the host device to maintain operations while the primary file system is being updated or restored. The configuration data allows the new operating system instance to be set up correctly, ensuring compatibility and proper functionality. This approach is particularly useful in environments where uninterrupted operation is critical, such as in servers or embedded systems.
12. The computer-program product of claim 8 , wherein the datastore is nonvolatile.
This invention relates to computer-program products for managing data storage, specifically addressing the need for reliable and persistent data retention in computing systems. The invention involves a computer-program product that includes a datastore designed to store data in a nonvolatile manner, ensuring that the data remains intact even in the event of power loss or system shutdown. The datastore is integrated into a system that processes data, such as a computer or a networked device, and is configured to handle data operations like reading, writing, and updating information. The nonvolatile nature of the datastore prevents data loss, which is critical for applications requiring high reliability, such as financial transactions, medical records, or industrial control systems. The invention may also include additional features, such as data encryption or redundancy mechanisms, to further enhance data security and integrity. The overall system ensures that data remains accessible and uncorrupted over time, addressing the problem of data volatility in traditional storage solutions.
13. The computer-program product of claim 8 , wherein the datastore is located in the nonvolatile storage of the host device.
A system and method for managing data storage in a host device involves a computer-program product that includes instructions for storing and retrieving data in a datastore located in the nonvolatile storage of the host device. The datastore is configured to store data in a structured format, allowing for efficient organization and retrieval. The system may include a host device with a processor and nonvolatile storage, where the processor executes instructions to manage the datastore. The datastore may be used to store various types of data, such as configuration settings, user preferences, or application data, ensuring persistence across device reboots or power cycles. The system may also include mechanisms for data validation, error correction, and integrity checks to maintain data reliability. The datastore may be accessed by different applications or system components, enabling shared data access while maintaining consistency and security. The system may further include features for optimizing storage usage, such as compression, deduplication, or tiered storage management, to improve performance and efficiency. The datastore may also support encryption to protect sensitive data, ensuring that only authorized users or processes can access the stored information. The system may be implemented in various computing environments, including mobile devices, embedded systems, or cloud-based platforms, to provide reliable and secure data storage solutions.
14. The computer-program product of claim 8 , wherein the client device is a diskless system.
A diskless client device system involves a computing device that operates without a local storage disk, relying instead on network-based storage and processing resources. The system includes a client device configured to execute applications and a server system that provides storage and computational services. The client device communicates with the server system over a network to access stored data and perform processing tasks. The server system manages storage resources and distributes computational workloads to optimize performance. The client device may include a lightweight operating system that minimizes local storage requirements while maintaining functionality. The system ensures data integrity and security through encryption and access control mechanisms. This approach reduces hardware costs, simplifies maintenance, and enhances scalability by centralizing storage and processing resources. The diskless architecture is particularly useful in environments where multiple client devices share common resources, such as enterprise networks or cloud computing environments. The system may also include mechanisms for caching frequently accessed data locally on the client device to improve performance while still relying primarily on network-based storage. The server system dynamically allocates resources based on demand, ensuring efficient utilization of available hardware. This configuration allows for flexible deployment and management of client devices without the need for local storage infrastructure.
15. A system comprising: one or more processors; a non-transitory machine-readable storage medium, including instructions that, when executed by the one or more processors, cause the one or more processors to perform operations including: receive configuration data that corresponds to a configuration of a first instance of an operating system executed by a client device, the configuration data including at least one modification to the first instance of the operating system introduced by the client device during execution of the first instance of the operating system by the client device; store the configuration data in a datastore that is located outside of a file system; receiving, at a second instance of the operating system, a request to load a file system from nonvolatile storage into volatile memory of the client device; in response to receiving the request, retrieving information corresponding to one or more instances of the operating system that have been checked out; determining, by the second instance of the operating system and using the information, that an instance of the operating system of the one or more instances of the operating system is not executing on the client device; in response to determining that the an instance of the operating system of the one or more instances of the operating system is not executing on the client device: retrieving the configuration data from the datastore, the configuration data including the at least one modification; and configuring a particular instance of the operating system of the one or more instances of the operating system in accordance with the configuration data; and facilitating loading of the file system into the volatile memory of the client device, wherein the particular instance of the operating system of the one or more instances of the operating system is executing while the file system is loaded on the client device.
This system addresses the challenge of maintaining and restoring user-specific operating system configurations across multiple instances of an operating system on a client device. The system includes one or more processors and a non-transitory storage medium containing instructions for managing operating system configurations. The system receives configuration data representing modifications made by a user to a first operating system instance, such as custom settings or installed applications, and stores this data in an external datastore outside the file system. When a second operating system instance requests to load a file system into the device's volatile memory, the system checks whether any operating system instances are currently executing. If no instances are active, the system retrieves the stored configuration data and applies the saved modifications to a new operating system instance. This ensures that the new instance is configured identically to the previous one, including all user-specific changes. The system then facilitates the loading of the file system into memory while the configured operating system instance runs. This approach allows seamless restoration of user preferences and settings across different operating system instances, improving consistency and user experience.
16. The system of claim 15 , further comprising: receiving an update request to update the configuration data for the particular instance of the operating system; and updating the configuration data for the particular instance of the operating system in the datastore located outside of the file system.
This invention relates to a system for managing configuration data of operating system instances, particularly in environments where multiple instances share a common base image but require unique configurations. The problem addressed is the inefficiency and complexity of storing and updating configuration data within the file system of each operating system instance, which can lead to redundancy, inconsistency, and difficulties in maintaining and updating configurations across multiple instances. The system includes a datastore located outside the file system of the operating system instances, where configuration data for each instance is stored separately. This external datastore allows configuration data to be managed independently of the file system, reducing redundancy and simplifying updates. The system also includes a configuration manager that retrieves and applies the appropriate configuration data to a particular operating system instance when it is initialized or when a configuration change is requested. Additionally, the system supports updating configuration data in response to an update request. When an update request is received, the configuration manager updates the configuration data for the specified operating system instance in the external datastore. This ensures that the latest configuration is applied the next time the instance is initialized or when a configuration refresh is triggered. By storing and managing configuration data externally, the system improves efficiency, consistency, and maintainability of operating system configurations in environments with multiple instances.
17. The system of claim 16 , further comprising: facilitating termination of the particular instance of the operating system and the file system on the client device, wherein the configuration data is maintained in the datastore during termination of the particular instance of the operating system and the file system on the client device.
A system for managing operating system and file system instances on client devices includes a datastore that stores configuration data for multiple instances of an operating system and a file system. The system allows a client device to request a particular instance of the operating system and the file system, which is then provided to the client device for execution. The system also enables the client device to modify the configuration data of the particular instance during execution. When the client device terminates the particular instance, the modified configuration data is maintained in the datastore, preserving changes for future use. This approach allows multiple client devices to share and manage instances of operating systems and file systems while maintaining consistent configuration data across sessions. The system ensures that configuration changes made by one client device are retained and available to other devices accessing the same instance. This is particularly useful in environments where multiple users or devices need access to the same operating system and file system configurations, such as in cloud computing or virtualized environments. The system simplifies configuration management by centralizing configuration data in a datastore, reducing the need for redundant storage and ensuring consistency across different client devices.
18. The system of claim 15 , further comprising: receiving, at the second instance of the operating system, a reload request to reload the file system into the volatile memory of the client device; in response to receiving the reload request, retrieving the configuration data from the datastore located outside of the file system; configuring a new instance of the operating system in accordance with the configuration data; and facilitating reloading of the file system into the volatile memory of the client device, wherein the new instance of the operating system is executing while the file system is reloaded on the client device.
A system for managing file system reloading in a computing environment involves a client device with an operating system and volatile memory. The system addresses the challenge of maintaining system availability during file system updates or reloading operations. The primary system includes a file system stored in volatile memory, a datastore external to the file system containing configuration data, and an operating system instance that manages the file system. The system further includes a mechanism to receive a reload request for the file system. Upon receiving this request, the system retrieves configuration data from the external datastore and uses it to configure a new instance of the operating system. While this new instance is executing, the original file system is reloaded into the volatile memory. This ensures continuous operation of the operating system during the file system reloading process, minimizing downtime and maintaining system functionality. The system is particularly useful in environments where uninterrupted access to the file system is critical, such as in servers or high-availability computing systems. The configuration data allows the new operating system instance to be set up correctly, ensuring compatibility and proper functionality after the file system reload.
19. The method of claim 1 , wherein the information indicates a count of the one or more instances of the operating system that have been checked out.
A system and method for managing operating system deployments in a virtualized or cloud computing environment addresses the challenge of tracking and controlling the distribution of operating system instances. The invention provides a mechanism to monitor and record the number of operating system instances that have been deployed or "checked out" from a central repository or management system. This allows administrators to enforce licensing compliance, optimize resource allocation, and maintain visibility into the deployment status of operating system instances across a computing infrastructure. The method involves tracking the checkout process, where each instance of the operating system is recorded as it is deployed to a virtual machine or physical host. The system maintains a count of these instances, which can be used for auditing, reporting, or triggering automated actions when predefined thresholds are reached. This ensures that the deployment of operating system instances remains within authorized limits and supports efficient management of computing resources. The solution is particularly useful in environments where multiple instances of an operating system may be deployed dynamically, such as in cloud-based or virtualized data centers.
20. The computer-program product of claim 8 , wherein the information indicates a count of the one or more instances of the operating system that have been checked out.
A system for managing operating system deployments in a computing environment involves tracking and controlling the distribution of operating system instances. The system includes a central repository storing one or more operating system images and a management module that monitors the checkout and usage of these images across multiple computing devices. The management module records metadata associated with each operating system instance, including a count of how many instances have been checked out from the repository. This count helps administrators track deployment status, enforce licensing compliance, and manage resource allocation. The system may also include a user interface for querying the metadata, allowing administrators to view which devices have active instances, their usage history, and other relevant details. The solution addresses challenges in maintaining visibility and control over operating system deployments in large-scale or distributed computing environments, ensuring efficient resource management and compliance with licensing agreements. The system may further include automated alerts or restrictions to prevent unauthorized or excessive checkouts, enhancing security and operational efficiency.
Unknown
August 25, 2020
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.