MAINTAINING COMMONLY NAMED CLIENT-SPECIFIC FILE CONTENT IN HARD DISK DRIVE EMULATION

• US 20070266027A1
• Filed: 05/09/2006
• Published: 11/15/2007
• Est. Priority Date: 05/09/2006
• Status: Active Grant

• Current Assignee: Hewlett-Packard Development Co. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Co. (HP Inc.)
• Inventors: Rope, Julien, Gattegno, Yves
• Granted Patent: US 8,332,370 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 3/0605 by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/0637 Permissions
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G11B 2220/20 Disc-shaped record carriers
• CPC Class Codes: G11B 27/329 on a disc [VTOC]
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

A data processing network has a virtual hard drive emulator and client terminals that share a virtual disk image. Client-specific read-write versions of selected files or directories are supported. All clients access the client-specific versions using the same name and address identifiers (for example, the same file name for a given configuration file), but each client has an exclusive version. A file ID distinguishes respective clients. These files are maintained alongside other files of other types and attributes. The selection of files to be client-specific can be predetermined, or a client-specific version of a file can be generated if the client executes a write operation to a client-specific file or area, the written data containing data read by the client in any of memory area available to the clients (RAM, Virtual Disk Drive, Hard Disk drive etc.). The technique supports customization while maximizing administrative control of operating system versions and minimizing redundant storage. File access for client terminals can be made close to systems having local hard drives.

Claims

1. A method for operating a data processing system, comprising:

maintaining a data store accessible to a plurality of operational entities capable of processing contents of the data store;

denoting at least one part of the data store as a shareable part;

supporting read operations from the data store to the operational entities and supporting write operations attempted from the operational entities to the data store, wherein the operational entities use a predetermined method for selection of portions to be read and written from/to the data store, including said shareable part of the data store, said predetermined method including specifying an identification comprising at least one of a name and address for identifying the portions selected;

wherein a plurality of said operational entities use the same said identification according to the predetermined method to identify at least one selected part of the data store to be read and written ; and

,

further comprising establishing a version of said selected part of the data store, said version being specific to the given operational entity and subject to customization independently and exclusively of other versions that are established for and served to one or more other said operational entities that likewise use the same said identification.

2. The method of claim 1, comprising storing information in the entity specific version at least one of configuration, identification, preference, authorization and status data enabling independent and distinct computation by the given operational entity versus other said operational entities, and further comprising providing coding for said computation in the data store, wherein the coding is executed commonly by the operational entities and the information in a respective said entity-specific version for a plurality of the operational entities customizes said computation for respective said entities while commonly executing said coding.

3. The method of claim 1, comprising providing a shareable part and a read-write part in the data store, and maintaining said entity-specific versions in the read-write part.

4. The method of claim 3, wherein at least part of the read-write part of the data store is in volatile memory, and further comprising storing at least some data specific to each operational entity in a read-write part of the data store that is in non-volatile memory.

5. The method of claim 1, wherein the operational entities comprise at least one of client terminals, network terminals, processes operating on at least one of said client terminals and said network terminals, users of one of the client and network terminals, and processes invoked by said users.

6. The method of claim 1, comprising accessing the data store for at least said read and write operations through a driver process associated with a corresponding one of the operational entities.

7. The method of claim 1, comprising accessing the data store for at least said read and write operations through a driver process associated with a server responsive to one of the operational entities.

8. The method of claim 1, comprising accessing the data store for at least said read and write operations over a network communication path such that the data store is remote from a corresponding one of the operational entities.

9. The method of claim 1, wherein the convention for addressing said contents comprises at least one of sector identification, file names, directories, directory trees, mapped drives and volumes.

10. The method of claim 1, wherein said write operations in the operational entities specific storage area(s) and serving said read operations of data in the operational entities specific storage area(s) comprise establishing and employing a distinct file address for distinguishing data written by and thereafter potentially read by said one of the operational entities.

11. The method of claim 10, wherein the distinct file address contains an identifier associated with said one of the operational entities.

12. The method of claim 10, further comprising maintaining and referring to a cross reference table associating distinct file addresses with respective said operational entities.

13. The method of claim 1, wherein the write operations and the read operations of data previously written in one entity-specific part of the data store contain at least one of terminal identification values, terminal configuration information, user identifications, security authorizations, passwords, software licensing information, media licensing information, user preferences, and operational history values, which is applicable to one of said terminals or users of the terminals and is used in customizing operation according to an operating system or to a software application.

14. The method of claim 1, wherein the data store is associated with a terminal device.

15. The method of claim 14, wherein the terminal device has one of plural processes and plural users, constituting said operational entities.

16. The method of claim 1, wherein the data store is associated with a network server.

17. The method of claim 16, wherein the network server is in data communications with terminal devices having one of plural processes and plural users constituting said operational entities.

18. The method of claim 17, wherein the operational entities initiate at least one of an operating system and an applications program by downloading data from the data store associated with the network server.

19. The method of claim 1, wherein at least one of the operational entities initiates at least one of an operating system or an applications program by reading data from a storage medium coupled thereto.