Looking for breakthrough ideas for innovation challenges? Try Patsnap Eureka!

Shared file system management between independent operating systems

a file system and independent technology, applied in the field of file system management, can solve the problems of not being able to access the same file system and share, and the operating system that accesses the shared file system has to be the same, so as to reduce or eliminate conflict

Active Publication Date: 2012-06-05
INSYDE SOFTWARE CORP
View PDF12 Cites 27 Cited by
  • Summary
  • Abstract
  • Description
  • Claims
  • Application Information

AI Technical Summary

Benefits of technology

[0005]A method for managing the sharing and updating of information contained within a shared file system that is accessible by two or more independent operating systems includes first creating a change file. This is performed, for example, by the operating system having principal control over the file system reserving an area of non-volatile memory for the writing and storage of information. This reserve area may be a portion of the file system itself, or a separate portion of non-volatile memory. Next, updated information, including the file name, location offset information, and updated data is written to the change file. The updated information may be provided, for example, by an application running on an operating system that does not have principal control over the shared file system. For example, in a system or platform executing both the Linux and Windows operating systems, Windows is typically the operating system that has principal control over the file system; whereas, Linux does not have control over the file system. Then, the updated information present in the change file is written to the shared file system. This may be accomplished, for example, by placing the secondary operating system (e.g. the operating system that does not have principal control over the shared file system) into a suspend or hibernate mode, activating the operating system having principal control over the shared file system, and having the principal operating system retrieve the file identified by the file name and offset information and modifying the contents of such file as provided in the data portion of the updated information and storing the updated file information in the shared file system In this manner, the principal and non-principal or secondary operating systems operate both concurrently and independently of one another; thereby, preventing conflicts during file system updating.
[0008]An advantage provided by the present invention is that is allows for two or more independent operating systems to share the management of a shared file system transparently without having to reset the file system data structure or rebooting either of the concurrently running operating systems.
[0009]Another advantage provided by the present invention is that substantially reduces or eliminates conflict between two or more operating systems that write information to a shared file system.

Problems solved by technology

One drawback associated with typical shared file system implementations is that the operating systems that access the shared file system have to be the same.
As such, it is currently not possible for a first operating system to access the same file system and share or otherwise update files contained within a memory managed by a second operating system, if the first and second operating systems are different, as it will be the file system of the second operating system that controls the access and organization of the underlying memory.

Method used

the structure of the environmentally friendly knitted fabric provided by the present invention; figure 2 Flow chart of the yarn wrapping machine for environmentally friendly knitted fabrics and storage devices; image 3 Is the parameter map of the yarn covering machine
View more

Image

Smart Image Click on the blue labels to locate them in the text.
Viewing Examples
Smart Image
  • Shared file system management between independent operating systems
  • Shared file system management between independent operating systems
  • Shared file system management between independent operating systems

Examples

Experimental program
Comparison scheme
Effect test

Embodiment Construction

[0015]An exemplary embodiment of the present invention will now be described with reference to FIGS. 1-4. FIG. 1 is a schematic block diagram of an exemplary electronic device 100, for example, a desktop computer, a laptop computer, a palm top computer, a router or set-top box, a server, a personal digital assistant (PDA), a communication device, for example, a cellular telephone or other suitable device and combination thereof, configured to implement the shared file system management functionality of the present invention. For purposes of illustration, and not limitation, the electronic device 100 is implemented as a laptop computer.

[0016]The laptop computer 100 includes a processor 102 configured to control the overall operation of the device. The processor 102 may include an arithmetic logic unit (ALU) for performing computations, one or more registers for temporary storage of data and instructions, and a controller for controlling the operations of the laptop computer 100. In o...

the structure of the environmentally friendly knitted fabric provided by the present invention; figure 2 Flow chart of the yarn wrapping machine for environmentally friendly knitted fabrics and storage devices; image 3 Is the parameter map of the yarn covering machine
Login to View More

PUM

No PUM Login to View More

Abstract

A shared file system may be updated by a non-native operating system writing information to a change file, while a native operating system is in a suspend or hibernation mode; after writing, the non-native operating system is placed in a suspend or hibernation mode and the native system activates and then retrieves the updated information from the change file and writes the updated information to a shared file system. The native operating system returns to a suspend or hibernate state before the non-native operating resumes operation. The updated information may be written as provided by the non-native operating system, or further updated by the native operating system before being written to the shared file system. The change file is created by the native operating system, and may be a reserved portion of the shared file system or may be a separate portion of non-volatile memory. The native and non-native operating systems operate both concurrently and independent of one another; thereby, preventing conflicts during file system updating.

Description

[0001]This application claims the benefit of U.S. Provisional Application Ser. No. 60 / 695,930, filed Jun. 30, 2005.FIELD OF THE INVENTION[0002]The present invention generally relates to file system management and, more particularly, to managing a shared file system between two or more independent operating systems.BACKGROUND OF THE INVENTION[0003]File systems are employed by operating systems to define, organize and maintain the contents of a particular file or series of files present in a corresponding memory. A hierarchical file system is an exemplary file system type that employs directories to organize files in a tree structure. A shared file system, in corresponding fashion, defines, organizes and manages the contents of files that are to be accessed and / or modified by two or more operating systems, for example, Linux and Windows.[0004]One drawback associated with typical shared file system implementations is that the operating systems that access the shared file system have to...

Claims

the structure of the environmentally friendly knitted fabric provided by the present invention; figure 2 Flow chart of the yarn wrapping machine for environmentally friendly knitted fabrics and storage devices; image 3 Is the parameter map of the yarn covering machine
Login to View More

Application Information

Patent Timeline
no application Login to View More
Patent Type & Authority Patents(United States)
IPC IPC(8): G06F7/00G06F17/00
CPCG06F17/30168G06F16/1767
Inventor YANG, CHIANG HAN
Owner INSYDE SOFTWARE CORP
Who we serve
  • R&D Engineer
  • R&D Manager
  • IP Professional
Why Patsnap Eureka
  • Industry Leading Data Capabilities
  • Powerful AI technology
  • Patent DNA Extraction
Social media
Patsnap Eureka Blog
Learn More
PatSnap group products