JPH1049423A - Virtual file system access subsystem - Google Patents

Abstract

PROBLEM TO BE SOLVED: To automatically mount a remote file system and facilitate access by accessing a subsystem, used in relation with a computer system connected to a network, by a virtual system. SOLUTION: When the MS-DOS or Windows operating system 21 receives an access request ACC REQ from an application program 20, it sends a remote access REM ACC to a network file system client module 23 on deciding that the access request ACC REQ is to a virtual logical storage device. The module 23 handles message transfer on a communication link 14 and an automounter module 25 and a server control module 31 exchanges messages through their network interfaces 24 and 33. Thus, the automounter 25 automatically mount the remote file system and its part.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

FIELD OF THE INVENTION The present invention facilitates the automounting and access of remote mass storage subsystems for use with the Microsoft Windows operating system system in general, and in particular in the field of digital computer systems, in a networking environment. Related to systems and methods.

[0002]

2. Description of the Related Art In a modern "enterprise", digital data processing systems (i.e., computer systems used in office environments in a company) require a large number of personal computers, workstations and mass storage subsystems, network printers, and so on. Other devices, such as interfaces to public telephone communication systems, communicate over computer networks. Personal computers and workstations are used by individual users to accomplish processing in connection with data and programs that can be stored in the network mass storage subsystem. In such a configuration, the personal computer / workstation acting as a client downloads data and programs from the network mass storage subsystem for the process. In addition, personal computers and workstations can process the processed data,
Enables uploading to a network printer for printing, to a telephony interface of a public telephony system for transmission, to a network mass storage subsystem for storage, and to other devices. . In such a configuration, the network mass storage subsystem, network printer and telephony interface operate as a server because they are available to service requests from all clients in the network. By configuring the network in such a manner, the server is readily available to all personal computers and workstations in the network. Such networks can be spread over a fairly large area by connecting personal computers / workstations via communication links such as electrical wires or fiber optics.

[0003] When completing the processing of an operation,
Computer systems use application programs to accomplish operations such as database management, word processing, accounting, process control, and many other functions in office and industrial environments. Application programs typically use the operating system to provide system services, such as low-level control of various hardware components, and to store many mass storage subsystems accessible over the network. In order to provide access to the files stored on the devices, they provide a system environment in which they can be conveniently executed. A popular operating system, namely Microsoft Windows ("Windows")
Provides, in conjunction with Microsoft's MS-DOS ("MS-DOS") operating system, a system environment of operations that can execute application programs written for Windows. A window operating system provides a graphical user interface ("GUI"), as well as a multitasking operating system environment, among other things, that can execute multiple Windows programs simultaneously.

[0004] With special reference to accessing files on a mass storage subsystem, files are typically accessible through a "file system". The file system used by modern operating systems is typically organized into a number of directories, each file being accessible through a file system associated with a directory. The directory itself is generally organized in a tree structure. The directory tree structure for a file system includes a higher-level "root" directory, which typically has one or more child directories. Each of the child directories of the root directory can also have one or more child directories, and so on, further down the tree. Each directory is essentially a storage location in the mass storage subsystem for the files in that directory, a pointer to the directory file for its child directories, and a pointer to the directory file for the parent directory, that is, the directory to which it is a child. When,
("Directory file"). A directory containing files from the root directory to locate successive directory files along the path until a directory file is located for the directory containing the file to be accessed to access the files in the directory. Search along the path until When a directory file is located for the directory containing the file to be accessed, the location information in that directory file is used to find the location of the file to be accessed.

[0005] Before a file system or portion of a file system can be accessed (ie, before a file or portion of a file in the file system can be accessed), it must be "mounted." In particular, mounting conditions a pointer in the directory file so that it can follow a path through the directory structure of the file system. Some operating systems, such as Unix, provide a uniform file system for each particular computer user, without regard to the particular mass storage subsystem or device on which the file is stored. That is,
The file system available to the user can extend across many devices. When a storage device is added to the network, directories and files on the storage device are added to the file system by "mounting" the storage device making that directory on the storage device available to users in a seamless manner. be able to. Similarly, when storage devices are removed from the network, the directories and files on the storage device are deleted from the file system (although they can still exist on the storage device from which they were taken), in which case Is no longer available to users.

[0006]

[Problems to be solved by the invention] MS-DOS and Windows
The operating system also allows a file system having a tree-structured directory structure. However, unlike Unix, the file system in MS-DOS and windows is closely related to "devices", which can be logical devices that are, for example, special physical storage devices or a subset of physical devices. . MS-DOS
In and windows, accessing a file requires identifying a special device, so each device essentially defines at least one file system, and in order to access a file on the device's file system, Requires that the file specifier use a particular device, as well as a path along the directory structure on the device to the particular file to be accessed. (MS-DOS and windows allow for current or default device designations, which are used when no device specifier is explicitly provided.) ,
A single personal computer or workstation with only three devices is not a problem, but because a network can include a number of devices, including the file system that the user wants to access, the personal computer or workstation can be connected to the network. When connected, it can be a problem.

[0007]

SUMMARY OF THE INVENTION The present invention is directed to a Microsoft MS-DOS and Windows system in a networking environment.
A new and improved system and method for automounting and accessing a remote file system in a networking environment for use in connection with an operating system is provided.

Briefly summarized, in one aspect, the present invention provides a virtual file system for accessing subsystems for use in connection with a computer system connected to a computer network. The computer system runs a selected operating system, such as Microsoft's MS-DOS and window operating system. A virtual logical storage file system in which a virtual file system accessing a subsystem is identified by a virtual logical storage device identifier and includes at least a portion of a remote file system maintained by another device connected to the computer network. To facilitate access to the virtual logical storage device. The virtual file system accessing the subsystem is an operating system request to enable the operating system to direct access requests from application programs that identify virtual logical storage to remote access elements for processing. Includes redirector. The remote access element is associated with a portion of the remote file system included in the virtual logical storage file system in response to the access request, generated by an application program that identifies the virtual logical storage device identifier and transferred by the operating system. To start the access operation. If the part of the remote file system being accessed was not previously mounted,
The remote access element enables the automount element to initiate a mount operation to mount the portion in connection with the remote file system, and then the remote access element can accomplish the access operation. Since the logical storage device identified by one identifier can be used to identify many remote file system parts, the application program accesses many remote file systems using one device identifier. can do.

In another aspect, the present invention provides a virtual file system for accessing a subsystem for use in connection with a computer system connected to a computer network. The computer system is
Runs selected operating systems such as Microsoft's MS-DOS and Windows operating systems. A virtual file system accessing a subsystem facilitates accessing a plurality of virtual logical storage devices, each identified by a virtual logical storage device identifier. Each virtual logical storage device has a virtual logical storage file system that includes at least a portion of a remote file system maintained by other devices connected to the computer network, and at least some virtual logical storage file systems have , A hierarchical directory system defining a plurality of possible paths, each with a path identifier. At least one of the virtual logical storage file systems, including the hierarchical directory system, has an associated default path that includes one of the possible paths. A virtual file system accessing the subsystem is an operating system request redirector for enabling the operating system to direct an access request identifying a virtual logical storage device received from an application program to a remote access element. including. The operating system receives access requests from the application programs and provides those access requests, including the virtual logical storage device identifier, to the remote access element. Along with the access request, the operating system assigns a path identifier for a default path for the virtual logical storage identified by the virtual logical storage for an access request received from an application program that does not include the path identifier. Provides for remote access elements. The remote access element responds to the access request including the virtual logical storage device identifier and the path identifier received from the operating system, in association with the virtual logical storage device file system maintained by the virtual logical storage device.
Start operation. During an access operation, the remote access element accesses a portion of the remote file system included in the virtual logical storage file system along a path identified by the path identifier.

[0010] In yet another aspect, the present invention provides a file system for accessing a subsystem for use in connection with a computer system connected to a computer network. The computer system runs on selected operating systems such as Microsoft's MS-DOS and window operating systems.
Run the system. The virtual file system accessing the subsystem has a virtual logical storage file system including an identifier identifying at least a portion of a remote file system maintained by another device connected to the computer network, the logical storage device Facilitates access to a virtual logical storage device identified by an identifier. The virtual file system accessing the subsystem includes an operating system request redirector to enable the operating system to direct access requests that identify virtual logical storage to remote access elements. The remote access element responds to the access request including the virtual logical storage identifier received by the remote access element from the operating system and associates the access operation with the virtual logical storage file system maintained by the virtual logical storage. Start. During an access operation, the remote access element accesses a portion of the remote file system identified by the remote file system portion identifier.

The invention is pointed out with particularity in the appended claims. The above and further advantages of the present invention may be better understood with reference to the description set forth below in connection with the accompanying drawings.

[0012]

FIG. 1 is a schematic diagram of a computer network including a system made in accordance with the present invention for automounting mass storage subsystem storage at Microsoft Windows. With reference to FIG. 1, a computer network 10 comprises a plurality of computers 11
(1) through 11 (N) (commonly identified by reference numeral 11 (n)) and 12. As usual, at least some of the computers 11 (n) are personal computers, or computer workstations, each including a system unit, a video display unit, and operator input devices such as a keyboard and mouse. The computer 12 also includes a system unit, and may similarly include a video display unit and an operator input device. Computers 11 (n) and 12 are conventional internal program computer architectures, the system units of which are generally processing units, memories, mass storage devices such as disks and tape storage devices, and communication links 13 respectively. Includes other components (not separately shown), including network interface devices 14 (n), 15 for interfacing a computer. The video display device allows the computer to display the processing status and processed data to the user, and the operator's input device allows the user to enter data and controls processed by the computer. Computer 11
(n) and 12 transfer information in the form of messages to each other over the communication link 13 through the network interface devices 14 (n), 15.

In one embodiment, network 1
0 is configured in a "client-server" configuration, wherein at least one computer, namely computer 12, operates as a server and other computers 11
(n) operates as a client. Typically, servers include mass storage devices that can store copies of data and programs that can be retrieved via communication link 13 for use in processing them by client computers. Sometimes, client computers 11 (n) send data to a server that they (the client computer that stored the data) or data that can later be retrieved by other client computers for use in processing operations. -It can also be stored on the computer 12. The server computer is typically a client computer 11 including a system unit, a video display unit and operator input devices.
Similar to (n) and can be used by the operator for data processing operations in a manner similar to the client computer.

[0014] In contrast, at least some of the server computers receive and process retrieval and storage requests from client computers, and provide processing, memory, and mass storage for generating responses thereto. It may include only devices and network interface elements.

In the network 10, a client
Computer 11 (n) and server computer 12
The communication link 13 interconnecting the devices may include wires, fiber optics, or other media for carrying signals representing information between the computers 11 (n) and 12, as is conventional. As mentioned above, each of the computers 11 (n) typically comprises a network interface device (a respective arrow 14 (n)) connecting the respective computer to the communication link 13.
And 15).

In one particular embodiment, computer 11 (n) uses the Microsoft Windows operating system program ("Windows") and server computer 12 uses the Microsoft Windows NT operating system program. When they are started or reinitialized,
Windows provides a number of conventional operating system services in connection with computer 11 (n), including initializing the computer. In addition, for application programs that are processed by a computer, Windows provides a number of conventional operating system services, including providing a graphical user interface ("GUI").

MS-DOS and Windows also facilitate accessing files (ie, reading and storing data in files) in the file system maintained by the system 10. In particular, MS-DOS and Windows allow the computer 11 (n) to access the local file system provided by the computer system's local mass storage subsystem, while still allowing other computer systems 11 (n) ') (N' ≠ n)
And access to a remote file system maintained by the server computer 12. In particular, the present invention may be used, for example, in Microsoft MS-DOS or Microsoft Windows operating systems to provide for auto-mounting of virtual logical storage to facilitate quick access by computer 11 (n). Systems and methods for A virtual logical storage device can include one or more directories or directory subtrees that cooperate with a device specifier. As will be apparent from the description below, a virtual logical device can be formed from a directory located on one mass storage subsystem, or many mass storage subsystems, and all these directories. Form a virtual logical device generically referred to by one device identifier for reference. One or more of the directories may be located on a local mass storage subsystem, that is, a mass storage subsystem located above the computer system 11 (n). Other directories on the virtual logical storage are on top of mass storage subsystems maintained by other computer systems, including any computer system 11 (n ') (n' ≠ n) connected to the network. Other directories can be located on the mass storage subsystem maintained by the server computer 12. In such a configuration, for directories located on the local mass storage subsystem, MS-DOS and Windows use the computer system 11
(n) in the directory in the same way as accessing files in the file system on the device identified by the device identifier that identifies the real storage device in the mass storage subsystem maintained for You can access certain files.

On the other hand, a remote mass storage subsystem,
That is, for directories physically located in other computer systems 11 (n ') (n' ≠ n) or mass storage subsystems maintained by server computer 12, MS-DOS and Windows are Remote access
Access files in those directories by accomplishing operations. In such an operation, it is by transferring the message over the communication link 14 in a conventional manner. However, the use of virtual logical storage identifiers allows operators and application programs to use many Allowing access to the above file system simplifies file access by operators and application programs.

FIG. 2 is a detailed functional diagram of the computer system 11 (n) for use in connection with the present invention. As shown in FIG. 2, the computer system 11 (n) includes an MS-DOS and Windows operating system (hereinafter MS-DOS / Win), generally identified by the reference numeral 21.
(represented by dows) processes the application program generally identified by reference numeral 20. In a special reference to accessing a file of a file system maintained by any one of the local storage devices 22 of the computer system or virtual logical storage, the application program is executed by the MS-DOS / Windows operating system 21. Issues an access request "ACCREQ". The access request is generally represented in the format DEV-ID: <PATH><FILENAME>, where the DEV-ID identifies a special storage device (which may be a local device 22 or a virtual logical storage device) and <PAT
H> identifies a path through the directory structure of the device, and <FILENAME> is a file name identifying a file in the directory identified by the path identifier <PATH>. If the storage device is the currently selected default device, the access request will be sent to the device identifier DEV-
You do not need to include the ID. Similarly, if the storage device and path are the currently selected default device and path, the access request will explicitly specify the device identifier DEV-ID and the path identifier <PAT
It is not necessary to include H>.

The MS-DOS / Windows operating system 21 sends an access request ACC REQ from the application program 20.
First, it is determined whether the accessed device is a local device 22 or a virtual logical storage device. The MS-DOS / Windows operating system 21 sends the access request ACC REQ to the local device 2
If so, it initiates a local access operation LOC ACC associated with the local device 22. It can be appreciated that the particular operation to be accomplished depends on the type of operation specified by ACC REQ, including, for example, opening or closing a particular file <FILENAME>, reading and writing data to that file, and so on. Would.

On the other hand, MS-DOS / Windows operating system
If the system 21 determines that the access request ACC REQ is for a virtual logical storage device, it issues a remote access REM ACC to the network file system client module 23. Network file system client module 23
Handles the message transfer over the network communication link 14 and, with specific reference to the present invention, the portion of the virtual logical storage file system that includes the file <FILENAME> and path <PATH> identified in the access request ACC REQ. Initiate an access operation in connection with the actual physical device containing

Prior to starting an access operation, a network file system client
Module 23 contains the file to be accessed <FILEN
AME> determines if the device file system portion of the virtual logical storage device containing the AME> has been mounted.
If the network file system client module 23 determines that the portion of the virtual logical storage device containing the file <FILENAME> to be accessed has been mounted, it can initiate an access operation through the network interface 24. . In the operation, the network
A file system client module 23;
For example, if the file system has access request ACC REQ
The server control module 31 of the server computer 12 that maintains a physical storage device 32 that includes a portion of the virtual logical storage file system defined by the server control module 31 to enable access control operations to accomplish the access operation Exchange messages via their respective network interfaces 24 and 33.

On the other hand, a network file system
If the client module 23 determines that the portion of the virtual logical storage device containing the file <FILENANE> to be accessed is not mounted, it (the network file system client module 23) issues an automount request. Provide AUTOMNT REQ to the automounter module 25. In response to the automount request AUTOMNT REQ, the automounter module 25 (subsequent to the previous example) sets the physical storage device to contain the file system portion of the virtual logical storage device whose file system is defined by the access request ACC REQ. Initiate a mount operation in connection with the server control module 31 of the server computer 12 maintaining 32.

In the mount operation, the automounter module 25 and the server control module 3
1 exchange messages over the network 14 through their respective network interfaces 24 and 33. During the mount operation, the automounter module 25 updates various data structures as described below. The data structure contains information for each file system mounted by the automounter module 25, which are used to process access requests for access operations to the respective file system by the network file system client. Used by module 23; After receiving the updated data structure, the network file system client module 23 can use the new information to process the access request as described above. In this way, they are
From 0, the automounter 25 automatically mounts the remote file system and its parts as required by the access request ACC REQ to the virtual logical storage maintained by the computer system 11 (n).

The access request for the remote file system is processed, and the remote file system automounter 2
5, the network file system client 23 can track access requests to various mounted remote file systems, and for remote file systems that have not been accessed within a predetermined time, Unmount can be started. Network file system client
If module 23 unmounts the remote file system, it can later be remounted by automounter 25 in the same manner as described above.

The network file system client module 23 and the automounter 25
Some items of information in identifying a virtual logical storage device, described in connection with, and a remote file system that forms the respective file system of the logical storage device. Referring to FIG. 3, the computer system initialization file 40 includes a network file system including a virtual device identifier field 41, a maximum automount field 42, an automount timeout field 43, and a map file identifier field 44. -Includes a number of fields containing automount information used by client module 23 and automounter 25. Initial state setting file 40
Is MS-DOS / Wind to initialize the computer system 11 (n)
Used by the ows operating system module 21 and can include, for example, an ".INI" initialization file that contains initialization and system environment information for defining the processing system environment under Windows. (As usual, Windows files with the full file name of the format "XXX.INI" have a file name of "XXX" and a file extension of "INI. The" .INI "file extension is This file is identified as an initial state setting file.) The virtual device identifier field 41 of the initial state setting file 40 contains information for identifying a virtual logical storage device, and in particular, a specific device for the logical storage device. Identification name DEV
-Provide ID. If the device identifier field 41 is empty, the selected device identifier is used as the default virtual device identifier, and in particular, the device identifier selected as the "last device" identifier for the computer system 11 (n). First name is used. For the MS-DOS / Windows operating system 21, the "final device" identifier can be specified, for example, by a system configuration file identified by the file name "CONFIG.SYS". It can be appreciated that the virtual device identifier field 41 can include one device identifier or many device identifiers; virtual device identifier field 4
If one contains many device identifiers, each different device identifier can uniquely identify a virtual logical storage device.

Following the automount information field in the initialization file 40, a maximum automount field 42 contains a value identifying the maximum number of remote file systems that can be mounted. The automount timeout field 43 indicates an automount request AUTOMN by the automounter module 25.
Includes a timeout value that identifies the maximum time that the automounter module 25 will wait for a notification that the claimed remote file system has been mounted following the issuance of T REQ.

Map file identifier field 44
Contains a pointer to the file containing the automount master map identified by reference numeral 50 in FIG. The automount master map is automounted and the device identifier field 4
1 contains information identifying various file systems to be accessed using the logical storage device identifier. In one embodiment, device identifier field 41
Contains multiple device identifiers, the same automount master map 50 is used for all device identifiers, but a separate automount master map 5 is used.
It is recognized that 0 can be provided for each device identifier. As shown in FIG. 3, the auto mount master
Map 50 includes one or more entries 51 (1) through 51 (N) (generally identified by reference numeral 51 (n)), each of which maps to a high-level directory in a file system associated with a virtual logical storage device. Related. Each entry 51 (n) includes a number of fields, including a directory name field 52, an automount sub-directory name field 53, and an option field 54. Directory name field 52 (n)
Each include a directory name used as the name of a top-level directory in the directory tree. Pointers to the remote file system,
The subdirectories below the highest level directory, along with those parts forming the directory, are identified in the automount subdirectory map file identified by reference numeral 60 described below. . The automount subdirectory name field 53 (n) contains the automount directory to be associated with the directory identified in the field.
Identify the sub directory map file 60. The options field 54 contains values for a number of optional parameters that can control the mounting of the remote file system and the access of the file, and these include whether the file system can read or write the file. Yes, or both, whether the file can be locked, including mount timeout values and mount retry values.

As mentioned above, the auto-mount
Sub-directory map file 60 identifies the components of the file system under the top-level directory. In accordance with one aspect of the present invention, the automount sub-directory map file 60 is a sub-directory identifier or, alternatively, an explicit name for the remote computer system 11 (n ') (n' @ n) or the server computer 12. Unique identifier and the path above it.

The automount sub-directory map file 60 is stored in the remote computer system 11 (n ') (n'
≠ n) or when it contains an unambiguous identifier for the server computer 12 or a path thereabove,
Automount master map 50 that indicates that
Can be indicated by an optional field 54 of the entry 51 (n); in one particular embodiment,
The option "host" is used to identify such a map 60. For those automount subdirectory map files 60 that contain subdirectory names, for each subdirectory, a pointer to the remote file system or portion thereof that forms the respective subdirectory. Provided.

The automount sub-directory map file 60 has a number of entries 61 (1) to 61 (6).
1 (M) (commonly identified by reference numeral 61 (m)), each of which has its automount subdirectory name field 53 (n) pointing to the automount subdirectory map 60. Associated with sub-directories under the level directory. Each entry 61 (m) includes two fields, a subdirectory name field 62 and a remote file
This is the system pointer field 63.

Sub-directory name field 62
(m) is a sub-directory name identifying a sub-directory under the top-level directory, or an unambiguous identifier of the remote computer system 11 (n ') (n' @ n) or the server computer 12. Including the path above it. Next, the remote file system pointer field 63
Contains a pointer to the remote file system or portion mounted (identified by reference numeral 64) mounted for the sub-directory identified in the sub-directory name field 62 (m). Thus, the remote file system pointer field 63 contains, for example, the name of the remote computer system 11 (n ') (n' @ n) or the server computer 12. The automount sub-directory map file 60 pointed to by the automounter master map file 50 is:
Effectively defines mount points for virtual logical storage; that is, they define various sub-directories under each directory identified in the automount master map file 50, to which In addition, it identifies special elements of the remote file system, including the file system portion of the computer system 11 (n) mounted at those mount points.

In the embodiment described above in connection with FIG. 3, the computer system 11 (n) sets the map file identifier field 44 in the initialization file 40.
And has one automount master map 50 as indicated by In that case, if the device identifier field 41 contains identifiers for a number of logical storage devices, then all of the virtual logical storage devices will have the same top level described in the map automount master map 50. It has one or more directories and has the same sub-directories as identified in the automount sub-directory map file 60. However, it is recognized that different computer systems 11 (n) can have different sets of virtual logical storage because the map file identifier field 44 in their respective initialization files 40 can be different. .

In this context, the operations performed by the network file system client module 23 and the automounter 25 in connection with the present invention will be described in connection with FIGS. 4 to 6
Is a network file system client
Establishing a connection used by the automounter module 25 to communicate with the module 23 and the network file system client module 2
3 depicts the operations performed to initialize the automounter module 25, including the generation of an automount control block containing the information provided in 3; 7 and 8 show a network file system client client in connection with a remote access request REM ACC from the MS-DOS / Windows operating system 21.
7 depicts the operations performed by module 23, including determining whether a portion of the virtual logical storage file system referenced in the remote access request has been mounted, and, if not, the automounter module. Auto mount request AUTO to 25
Issue an MNT REQ and have it (automounter module 25) perform a mount operation. FIGS. 9 and 10 show an automount request AUTOMNT REM that the network file system client module 23 can issue if the portion of the remote file system to be accessed is not mounted.
In response to Q, the operation performed by automounter module 25 is depicted.

Generally, a socket is created during initialization of the automounter module 25 (FIGS. 4-6), which provides communication between the automounter module 25 and the network file system client module 23. The automounter module 25 binds itself to one port of the socket. (The socket is a common communication structure and is not described herein.) In addition, information can be obtained from the various structures described above in connection with FIG. 3 to generate the automount control block. And a pointer to the automount control block is passed to the network file system client module 23. Finally, the MS-DOS / Windows operating system 21 is notified of the virtual logical storage device identifier and enables the access request containing the virtual logical storage device identifier to be directed to the network file system client module 23. Is done. (MS
-Enabling the DOS / Windows operating system 21 to redirect access requests is a normal operation. In particular, referring initially to FIGS. 4-6, during initialization, the automounter module 25
First issues a request to the MS-DOS / Windows operating system 21 to request the establishment of a socket (step 100).

If the MS-DOS / Windows operating system 21 establishes a suitable socket, it is a socket identifier that the automounter module 25 can use when communicating with the network file system client module 23. Return it (MS
-The DOS / Windows operating system 21) provides. On the other hand, if the MS-DOS / Windows operating system 21 cannot establish a socket, it provides a return value corresponding to the error code. Hence,
Following step 100, the automounter module 25 examines the return value to determine whether it is a socket identifier or an error code (step 10).
1).

If, at step 101, the automounter module 25 determines that the return value is an error code, it ends with an appropriate message (step 102).

On the other hand, if in step 101 the automounter module 25 determines that the return value is a socket identifier, it retrieves selected information about the socket using the socket identifier and binds itself to the socket. (Step 103).

Following step 103, the automounter module 25 initializes the automount control block and passes the information therein to the network file system client module 23. In that operation, the automounter module 25 retrieves the contents of the automount master map 50 and loads it into the automount control block (step 104).

In addition, the automounter module 25 determines whether the initialization file 40 includes a virtual logical storage device identifier field 41 (step 10).
5) If so, copy the logical storage device identifier value from field 41 to the automount control block (step 106).

On the other hand, if the automounter module 25 determines in the step 105 that the initialization file 40 does not include the virtual logical storage device identifier field 41, the automounter module 25 sets the MS-D
The OS / Windows operating system 21 is called to determine the last drive identifier (step 107), and it is copied to the automount control block as a virtual logical storage device identifier (step 108).

Subsequent to step 106 or step 108, the automounter module 25 determines whether the initialization file 40 includes a maximum automount field 42 or an automount timeout field 43 (step 109). , If so, it copies the contents of each field to the automount control block (step 110).

On the other hand, if in step 109 the automounter module 25 determines that the initialization file 40 does not contain either or both fields 42 or 43, it proceeds to step 111 and sets a predetermined default value. Load to automount control block.

Subsequent to step 110 or step 111, the automounter module 25 includes the network file system client module 23
Then, a notification including a socket identifier for the socket established in steps 100-103 and a pointer to the automount control block is sent (step 113).

In addition, the automounter module 25 issues a request to the MS-DOS / Windows operating system 21 to redirect an access request for a virtual logical storage device to the network file system client module 23 (step 11).
4).

In step 114, the initialization is completed, and the automounter module 25 waits until receiving the automount request AUTOMNT REQ from the network file system client module 23. The operations performed by the automounter module 25 in response to the automount request AUTOMNT REQ from the network file system client module 23 will be described with reference to FIGS.

The operation performed by the network file system client module 23 is shown in FIG.
And FIG. 7 and 8, the network file system client module 23 generates the socket identifier generated by the automounter module 25 during initialization, as described above in connection with FIGS. And a pointer to the automount control block (step 130).

After receiving the pointer to the automount control block in step 130, the network
The file system client module 23
The information from the automount master map 50 loaded into the automount control block during initialization (FIGS. 4-6) by the automounter module 25 into the automount subdirectory map file 60. A directory tree for the virtual logical storage device is created using the listed sub directories (step 131).

An example of a tree 70 is shown in FIG. Referring to FIG. 11, the directory tree 70 includes a series of entries 71 (1) through 71 (N) (reference numeral 71 (n)).
Generally identified by). Route entry 7
The first entry identified as 1 (1) is indicated by the root pointer 72.

Each entry 71 (n) identifies the identity of the virtual logical storage directory identified in the correspondingly indexed entry 51 (n) in the automounter master map 50.
MS-DOS / Win with its children corresponding to the sub-directory identified in the auto-mount sub-directory map file 60 identified by (1)
Includes with two child pseudo-directories provided by dows operating system 21. . (Two child pseudo-directories are “.” And “..” sub-directories. In FIG. 11, real sub-directories are shown for root entry 71 (1) and entry 71 (2). Is not.)

In addition, each entry 71 (n) is:
Contains the "sibling" pointer to entry 71 (n + 1) for the directory listed in next entry 51 (n + 1) in automount master map 50.
(The "sibling" pointer to the last entry 71 (N) contains a null value indicating that it is the last entry 71 (N).) Mountable sub-directories (i.e., Entry 71 (n) provides information used by the network file system client module 23 in connection with the remote access described below. After creating the directory tree 70, the network file system client module 23 executes a remote access request REM ACC from the MS-DOS / Windows operating system 21.
(Step 132).

In step 132, a remote access request REM from the MS-DOS / Windows operating system
While waiting for the ACC, the network file system client module 23
A selected housekeeping module that enables the automounter module 25 to unmount the remote file system for which the file system client module 23) did not receive the remote access request REM ACC within a predetermined time period. Operations can be performed.

When the MS-DOS / Windows operating system 21 receives, from the application program 20, an access request ACC REQ that explicitly or implicitly identifies a virtual logical storage device, it receives it (MS-DOS / Windows operating system 21). ) Issues a remote access request REM ACC to the network file system client module 23.

When the network file system client module 23 receives the remote access request REM ACC (step 133), it first verifies that the device identified as the remote access request REM ACC is a virtual logical storage device, and The request is disassembled to verify that the directory path and file name specified in are valid (step 134).

When verifying that the device identified in the remote access request REM ACC is a virtual logical storage device, the network file system client module 23 automatically mounts the device identifier in the remote access request REM ACC. The remote access request RE is compared with the virtual logical storage device identifier in the control block.
Verify that the device identifier in MACC matches the virtual logical storage device identifier in the automount control block.

Similarly, in determining whether the remote host or directory path and file name specified in the request are valid, the network file system client module 23 may use a naming convention such as accepted naming conventions. The properties can be used to check that the directory or directory in each host name or path and the file name in the remote access request are valid.
The network file system client module 23 gets a negative decision in step 134 (i.e., if the device identifier in the remote access request REM ACC is not a virtual logical storage device identifier, or a host, subdirectory or file If the name is not valid), it is a remote response RE indicating an error
Provide the M RSP (step 135).

On the other hand, if the network file system client module 23 gets a positive decision in step 134 (ie, it determines that the device identifier in the remote access request REM ACC is a virtual logical storage device identifier). If it is determined that the remote access request RE
It is determined whether the high-level directory and the next-level subdirectory in the MACC have been mounted (step 136).

The high level directory and the next level sub
If the directory is mounted, directory tree 70 contains a mount pointer to the remote file system mount structure corresponding to the file system portion of the virtual logical storage device.

If the network file system client module 23 gets a positive decision in step 136, it uses the information in the mount structure to control the remote computer system 11 (n ') (n' ≠ n) or server. The remote access operation to the computer 12 is started (step 137).

The network file system client module 23 and the remote computer system 11 (n ')
The specific operation associated with the remote access operation, performed by (n '≠ n) or server computer 12, depends on the particular type of access operation. For example,
If the access operation is a file open or close operation, the network interface 24 will generate them on the communication link 14 when the network file system client module 23 generates one or more messages on the remote computer system 11 (n '). ) (N '
≠ n) or transfer to server computer 12
Allow them to open and close the specified file.

On the other hand, if the access operation is a read operation, when the network file system client module 23 generates one or more messages including the read request, the network interface 24 sends them to the remote computer system 11 (n '). (N '≠ n)
Alternatively, the data is transferred to the server computer 12. In response, the remote computer system 11 (n ') (n' ≠ n) or the server computer 12 reads the information from the file specified in the read request and, in one or more messages transmitted over the communication link 14, Transfer the information to the network file system client module 23. After receiving the information, the network file system client module 2
3 can provide up to an MS-DOS / Windows operating system 21 which in turn provides information to the application program 20 requesting it.

Finally, if the access operation is a write operation, the network file system client module 23 generates one or more messages containing the write request and the data to be written, and the network interface 24 It is transferred to the remote computer system 11 (n ') (n' ≠ n) or the server computer 12. In response, the remote computer system 11 (n ') (n' ≠ n) or the server computer 12 stores the data in the file specified in the write request. The network file system client module 23 is also generated to transfer a message to the remote computer system 1 (n ') (n' @ n) or the server computer 12, enabling the network interface 24. Thus, another access operation can be started.

After the remote access operation is completed, the network file system client module 23 returns to step 132 to wait for the next remote access request REM ACC. Returning to step 136, if the network file system client module 23 gets a negative decision in that step, i.e., determines that the high-level directory and the next level sub-directory in the remote access request REM ACC were not mounted. If so, proceed to step 138 to enable the automounter module 25 to mount the requested remote file system for access. Communication between the network file system client module 23 and the automounter module 25 is via the socket established in step 103 above. The operations performed by the automounter module 25 in connection with step 138 are illustrated in FIGS.
0 will be explained. Automounter module 25
Has completed the mount operation, it (automounter module 25) has a high-level directory and a next-level sub-directory that the network file system client module 23 can load into the directory tree 70. Provide mounting structure for Following step 138,
The network file system client module 23 proceeds to step 137, where it initiates remote access using the mount information just loaded into the directory tree 70.

The operations performed by the automounter module 25 in connection with mounting a remote file system, or portions thereof, are described in connection with FIGS. When the auto mount operation is started by the auto mounter module 25, the network file system client module 23
Provides a pointer to the directory tree 70.
Therefore, referring to FIG. 9 and FIG.
Module 25, as well as the identification of the mount point to be mounted (ie, sub-directory),
First, a directory tree pointer is received via the socket established in step 103 (FIGS. 4-6) (step 150).

After receiving this information from the network file system client module 23, the automounter module 25 first
Perform many steps to check the mount point given from 3. In operation, the automounter module 25 parses the mount point provided by the network file system client module 23 to verify that the structure of the mount point identifier is valid, and if valid, Over the network, a remote computer system 11 (n ') (n' ≠) that maintains a portion of the remote file system identified by the remote file system indicated by the mount point identifier to accomplish the mount.
n) or exchange one or more messages with the server computer 12.

In particular, in order to determine whether the sub-directory name field 62 (m) of the auto-mount sub-directory map file 60 contains a remote host identifier or a sub-directory name, the auto-mounter performs auto-mounting.・ Master map file 50
First, it is determined whether or not the option field 54 of the entry 51 (n) includes the option “host” (step 151).

As described above, if the entry includes the option "host", each of the subdirectories identified in the subdirectory name field 62 (m) of the automounter subdirectory map file 60 will be Host name, ie remote computer system (n ')
(N '≠ n) or the identification of the server computer 12 and the directory path. Since the structure of the computer system identifier does not have to follow the requirements of the directory and file name structure of the operating system, the automounter module 25 performs different operations to check the structure of the mount point identifier. . Therefore, automounter module 2
If 5 obtains a positive decision in step 151, it proceeds to step 152, where the directory name of the remote computer system 11 (n ') (n' @ n) or the file system on the server computer 12 to be mounted As with the remote path, the mount point identifier is analyzed to identify the specific remote computer system 11 (n ') (n) n') or server computer 12. The automounter module 25 then communicates with the communication link 1 via the network interface 24.
4 on the remote computer system 11 (n ') (n'
(N) or check that the remote path required to exchange with server computer 12 is valid (step 153).

If the automounter module 25 determines in step 153 that the path is invalid, it will
An error is returned to module 23.

Returning to step 151, if the automounter module 25 gets a negative decision in that step, the mount point identifier does not include the host name. In that case, the automounter module 25
Goes to step 156 and parses the mount point identifier to verify that it complies with the operating system path and filename structural requirements. If the automounter module 25 gets a negative decision in that step, it will go to step 15
7 and the entry 51 in the automount master map 50 using the mount point identifier.
(n) and automount subdirectory map
Identify the relevant entry 61 (m) in file 60 and determine the relevant remote file system identifier for the mount operation. Step 153
Following the step (if the automounter obtains a negative decision in that step) or step 157, the automounter module 25 proceeds to step 160, where the remote computer system 11 (n ') (n' ≠ n) or the server Performing the actual mount operation in connection with the computer 12 and then returning to the network file system client module 23; In operation, the automounter module 25 executes the remote computer system 1 to perform the mount in a conventional manner.
1 (n ') (n' ≠ n) or exchange messages via the communication link 14 using the network interface 24 to enable the server computer 12;
Update the mount structure pointed to by the directory tree 70. If the automount operation is successful, the automounter module 25 returns to the network file system client module 23 that performs the remote access operation as described above (step 161).

On the other hand, if the automount operation has not been successful within the time period established by the timeout value defined by the automount timeout field 43, the automounter module sends the appropriate message to the appropriate message. It provides up to a network file system client module 23 that can initiate a simple error recovery operation.

The present invention offers a number of advantages. For example, it requires an explicit identification of the storage device to identify the file system, automating a remote file system for use in conjunction with an operating system such as Microsoft MS-DOS or the Windows operating system. Provides a configuration for mounting. By defining that certain device names can be automounted remote devices, which access requests from the application program 20 are local requests, which are serviced by the network file system client module 23. Whether the request is remote is clear from the device identifier in the access request ACC REQ.

In addition, by providing the "host" option described above, the present invention allows, for example, the remote computer system 11 (n ') (n' @ n) and / or the An arrangement is provided in which the entire file system can be mounted and appear as a subdirectory of one or more top-level directories for the computer system 11 (n). In this way, all or a selected subset of the file system of the remote computer system 11 (n ') (n' ≠ n) and / or the server computer 12 can be mounted as a single automount drive. . Operating systems such as MS-DOS and Windows, which limit the number of devices that the computer system 11 (n) can access (for example, MS-DOS and Windows, each device has a single letter " a), "b", etc.), the remote device can be viewed as a sub-directory on one device rather than a separate device, i.e., virtual logical storage.

Further, the present invention provides an arrangement in which many virtual logical storage units, each having a unique identifier, can be used to identify the same plurality or singular physical mass storage subsystems. Since each virtual logical storage device can have a different current default path and directory, different parts of the same physical file system can easily use the default directory simply by choosing the appropriate virtual logical storage device. Can be accessed.

Further, the remote computer system 11 (n ')
Although the invention has been described in one embodiment in connection with (n '記憶 n) or a virtual logical storage file system including a remote file system maintained on a server computer 12, the virtual logical storage file system may be a computer. It will be appreciated that some or all of the local file systems maintained by system 11 (n) may be included.

The preceding description has been limited to a specific embodiment of this invention. However, it will be apparent that various changes and modifications can be made to the invention while achieving some or all of the advantages of the invention. It is the object of the appended claims to cover these changes and modifications within the spirit and scope of the invention.

[Brief description of the drawings]

FIG. 1 is a schematic diagram of a computer network including a system made in accordance with the present invention for automounting mass storage subsystem storage at Microsoft Windows.

FIG. 2 is a functional block diagram of a computer system including a network file system client module and an automounter module according to the present invention;

FIG. 3 is a diagram depicting various data structures used by the network file system client module and the automounter module depicted in FIG.

FIG. 4 is a flow chart that helps to understand the operation of the network file system client module and the automounter module depicted in FIG.

FIG. 5 is a flow chart that helps to understand the operation of the network file system client module and the automounter module depicted in FIG.

FIG. 6 is a flow chart that helps to understand the operation of the network file system client module and the automounter module depicted in FIG.

FIG. 7 is a flowchart useful in understanding the operation of the network file system client module and the automounter module depicted in FIG.

FIG. 8 is a flowchart useful in understanding the operation of the network file system client module and the automounter module depicted in FIG.

FIG. 9 is a flowchart useful in understanding the operation of the network file system client module and the automounter module depicted in FIG.

FIG. 10 is a flow chart useful for understanding the operation of the network file system client module and the automounter module depicted in FIG.

FIG. 11 depicts a data structure useful for understanding the operation of the network file system client module and the automounter module depicted in FIG.

[Explanation of symbols]

10 Computer Network, 11 Client Computer, 12 Server Computer, 13 Communication Link, 14, 15 Network Interface Device, 70 Directory Tree, 71 Entry, 72 Root Pointer

 ──────────────────────────────────────────────────の Continuation of the front page (71) Applicant 597004720 2550 Garcia Avenue, MS PAL1-521, Mountain View, California 94043-1100, United States of America (72) Inventor Josef E. Szanovs, United States of America Wendell Street, Cambridge, 29 (72) Inventor Philip M. Rosenzweig, Kinsley Road, Acton, Massachusetts, USA 01720, 12

Claims (111)

[Claims] A virtual file system access subsystem for use in connection with a computer system connected to a computer network, said computer system running a selected operating system; The virtual file system access subsystem facilitates access to a virtual logical storage device identified by a virtual logical storage device identifier, the virtual logical storage device being maintained by other devices connected to the computer network. A virtual logical storage file system that includes at least a portion of a remote file system, wherein the virtual file system access subsystem includes: A. virtual logical storage that the remote access element receives from the operating system apparatus In response to the access request including the identifier, an access operation is started in association with the virtual logical storage file system held in the virtual logical storage device, and during the access operation, the remote storage device included in the virtual logical storage file system is started. A remote access element that accesses a portion of the file system; and B. an operating system request redirector to enable the operating system to direct the remote access element to access requests that identify a virtual logical storage device. 2. The virtual file system according to claim 1,
In the access subsystem, the virtual logical storage file system comprises a plurality of portions of the remote file system held by the other device, each access request further identifying one of the remote file system portions. A virtual file system comprising a remote file system portion identifier, wherein the remote access element initiates an access operation in response to the access request in association with the remote file system portion identified in the access request. Access subsystem. 3. The virtual file system according to claim 1,
In the access subsystem, the virtual logical storage file system includes at least one portion of a remote file system each held by one of a plurality of other devices connected to the network;
Each access request further includes a remote file system portion identifier identifying one of the remote file system portions, wherein the remote access element is responsive to the access request to identify the remote file system identified in the access request. A virtual file system access subsystem for initiating an access operation in association with one of the other devices holding a file system portion. 4. The virtual file system according to claim 1,
In the access subsystem, the operating system
A virtual file system access subsystem, wherein the system comprises an MS-DOS and a Windows operating system. 5. The virtual file system according to claim 1,
In the access subsystem, the network is configured according to a client / server network architecture model, the other device includes a server device, and the computer system includes a client device.
A virtual file system access subsystem including a device, wherein the remote access element comprises a network file system client element. 6. The virtual file system according to claim 1,
In the access subsystem, the operating system
The system request redirector includes: A. a virtual logical storage information store for storing virtual logical storage information including at least one virtual logical storage identifier; B. virtual logical storage from the virtual logical storage information store. Retrieve a storage device identifier and provide the virtual logical device identifier to an operating system, thereby enabling the operating system to redirect an access request identifying the virtual logical device identifier to a remote access element. Operating system redirection enabler for 7. The virtual file system according to claim 6,
In an access subsystem, a virtual logical storage device store stores a plurality of virtual logical storage device identifiers, and an operating system redirection enabler stores the virtual logical storage device information from the virtual logical storage device store for providing to the operating system. Retrieving a plurality of virtual logical storage device identifiers, thereby enabling an operating system to redirect an access request identifying any virtual logical storage device identifier to a remote access element. File system access subsystem. 8. The virtual file system according to claim 6,
In the access subsystem, the virtual logical storage device information store further stores directory information including at least one directory identifier and an associated remote file system identifier, wherein the remote file system identifier is the remote file system identifier. A virtual file system access subsystem identifying a portion of the system, wherein the remote access element identifies the other device using the remote file system identifier when initiating an access operation. 9. The virtual file system according to claim 8,
In an access subsystem, the access request includes path information identifying a path through a hierarchical directory system, and wherein the remote access element is to be accessed using the path information in response to the access request. And a directory to be accessed and a remote file system associated with the remote access element, wherein the remote access element responds to the access request and performs an access operation on the network in association with the identified remote file system. A virtual file system access subsystem, characterized in that it initiates. 10. The virtual file system access subsystem according to claim 8, wherein the directory information stored in said virtual logical storage device information store includes a plurality of directory identifiers, and some of said directory identifiers are fewer. Each having one sub-directory identifier, each sub-directory identifier having an associated remote file system identifier, and
A file system identifier identifies the portion of the remote file system and the remote access element uses the remote file system identifier to identify other devices connected to the network when initiating an access operation. A featured virtual file system access subsystem. 11. The virtual file system access subsystem according to claim 10, wherein said access request includes path information identifying a path through a hierarchical directory system, and wherein said remote access element includes said access request. And the directory and sub-directory to be accessed in response to the access request using the path information in response to
A virtual file system for identifying a remote file system associated with a directory, wherein the remote access element initiates an access operation on a network in association with the identified remote file system in response to the access request. File system access subsystem. 12. The virtual file system access subsystem according to claim 11, wherein at least some of the access requests do not include path information, and said virtual logical storage device information store includes a plurality of virtual logical storage device identifiers. And enabling the operating system redirection enabler to redirect an access request identifying any virtual logical storage device identifier to a remote access element to the operating system, the operating system further comprising: Providing a default directory associated with a virtual logical storage device identifier, wherein the remote access element uses the default directory in response to an access request that does not include path information. System. 13. The virtual file system access subsystem according to claim 12, wherein the default directory is selectable by an application program. 14. The virtual file system access subsystem according to claim 10, wherein for at least one directory, each sub-directory identifier is provided by the other device connected to the network. A virtual file system access sub-system, corresponding to a remote file system identifier for the remote file system, thereby enabling the remote file system to be accessed to use the virtual logical storage device identifier. system. 15. The virtual file system access subsystem according to claim 1, wherein said remote file system portion has an associated mount state, and said remote access element initiates said access operation. Prior to determining whether the mount state indicates that the remote file system portion is mounted on the virtual logical storage device file system, (i) if mounted, start an access operation;
(ii) A virtual file system access subsystem characterized by enabling the automounter element to perform a mount operation if not mounted. 16. The virtual file system access subsystem of claim 15, wherein the automounter element indicates that the mount operation was successful.
A virtual file system access subsystem, wherein the remote access element initiates the access operation associated with the mounted remote file system portion. 17. A method for accessing a virtual file system in a computer system connected to a computer network, said computer system running a selected operating system, said method comprising: Facilitating access to a virtual logical storage device identified by an identifier, the virtual logical storage device including at least a portion of a remote file system maintained by another device connected to a computer network In those having a file system, the method includes the steps of: A. enabling the operating system to direct an access request identifying a virtual logical storage device to a remote access element;・ Remote from system Responsive to an access request received by the access element, the access request including the virtual logical storage identifier, enabling the remote access element to initiate an access operation in association with the virtual logical storage file system held by the virtual logical storage. Accessing the portion of the remote file system included in the virtual logical storage device file system during the access operation. 18. The method of claim 17, wherein the virtual logical storage file system comprises a plurality of portions of a remote file system held by the other device, each access request further comprising the remote file system. A remote file system part identifier identifying one of the parts, wherein the remote access element is responsive to the access request and associated with the remote file system part identified in the access request;
A method for accessing a virtual file system, comprising the step of initiating an access operation. 19. The method of claim 17, wherein the virtual logical storage file system is at least one of the remote file systems each maintained by one of a plurality of other devices connected to the network. And each access request further includes a remote file system portion identifier identifying one of the remote file system portions, wherein the remote access element is responsive to the access request and identified in the access request. Initiating an access operation in association with one of the other devices holding the remote file system portion created. 20. The method for accessing a virtual file system according to claim 17, wherein the operating system includes MS-DOS and a window operating system. 21. The method of claim 17, wherein the network is configured according to a client / server network architecture model, the other device includes a server device, and the computer system includes a client device. Accessing the virtual file system, wherein the remote access element comprises a network file system client element. 22. The method of claim 17, wherein the operating system request redirection step comprises the following steps: A. Store virtual logical storage device information including at least one virtual logical storage device identifier. Providing a virtual logical storage information store for the B. retrieving the virtual logical storage identifier from the virtual logical storage information store and providing the virtual logical storage identifier to the operating system, whereby the operating system Redirecting an access request identifying a virtual logical storage device identifier to a remote access element. 23. The method of claim 22, wherein the virtual logical storage information store stores a plurality of virtual logical storage identifiers, and wherein the operating system redirection includes the following steps: Retrieving the plurality of virtual logical storage device identifiers from a logical storage device information store; and B. providing the retrieved plurality of virtual logical storage device identifiers to an operating system, thereby providing the operating system with an optional Enabling the access request identifying the virtual logical storage device identifier to be redirected to a remote access element. 24. The method according to claim 23, wherein said virtual logical storage device information store further stores directory information including at least one directory identifier and an associated remote file system identifier. If the file system identifier is
Accessing a virtual file system identifying a portion of a file system, wherein the remote access element identifies the other device using the remote file system identifier when initiating an access operation. how to. 25. The method of claim 24, wherein the access request includes path information identifying a path through a hierarchical directory system, and wherein the remote access element responds to the access request with the path information. Identifying the directory to be accessed and the remote file system associated with the directory to be accessed, wherein the remote access element is associated with the identified remote file system in response to the access request. Initiating an access operation over a network by accessing the virtual file system. 26. The method of claim 24, wherein the directory information stored in the virtual logical storage device information store includes a plurality of directory identifiers, and wherein some of the directory identifiers are at least one sub-directory identifier. And each sub-directory identifier has an associated remote file system identifier,
Each remote file system identifier is
Identifying the portion of the file system and initiating an access operation wherein the remote access element uses a remote file system identifier to identify other devices connected to the network. How to access the file system. 27. The method of claim 26, wherein the access request includes path information identifying a path through a hierarchical directory system, and wherein the remote access element responds to the access request with the path information. Identifying a directory and sub-directory to be accessed in response to the access request, and a remote file system associated with the sub-directory to be accessed, the remote access element responding to the access request. And initiating an access operation on the network in association with the identified remote file system. 28. The method of claim 27, wherein at least some access requests do not include path information, and wherein said virtual logical storage device information store stores a plurality of virtual logical storage device identifiers. The operating system redirection enabler enables the operating system to redirect an access request identifying any virtual logical storage device identifier to a remote access element, wherein the operating system further includes a respective virtual logical storage device identifier. Providing a default directory associated with the virtual file system, the remote access element using the default directory in response to an access request that does not include path information. 29. A method according to claim 28, wherein said default directory is selectable by an application program. 30. The method according to claim 26, wherein for at least one directory, each sub-directory identifier is a remote directory for a remote file system provided by the other device connected to the network. A method for accessing a virtual file system, the method comprising: using a virtual logical storage device identifier, wherein the remote file system to be accessed corresponds to the file system identifier. 31. The method of claim 17, wherein said remote file system portion has an associated mount state, and wherein said remote access element has said mount state prior to initiating said access operation. Indicates whether the remote file system portion is mounted on the virtual logical storage device file system, and if (i) mounted, starts an access operation; (ii) must be mounted. A method of accessing a virtual file system, for example, enabling an automounter element to perform a mount operation. 32. The method of claim 31, wherein if the automounter element indicates a successful mount operation, the remote access element initiates the access operation associated with the mounted remote file system portion. A method for accessing a virtual file system, comprising the steps of: 33. A virtual file system access subsystem for use in connection with a computer connected to a computer network, said computer system running a selected operating system, The file system access subsystem facilitates access to a virtual logical storage device identified by a virtual logical storage device identifier, the virtual logical storage device being maintained by another device connected to the computer network. A virtual file system access subsystem computer program product having a virtual logical storage file system including at least a part of a remote file system, and a medium on which the virtual file system access subsystem computer program product is recorded. The access subsystem computer program product is recorded on a computer usable medium having a computer system readable code, said computer system readable code comprising: A. The remote access element comprises an operating system. In response to an access request including a virtual logical storage device identifier received from the system, an access operation is started in connection with the virtual logical storage device file system held in the virtual logical storage device, and during the access operation, the virtual logical storage device file is accessed. A remote access element code for accessing a portion of said remote file system included in the system; and B. an operating system for enabling the operating system to direct the remote access element to access requests identifying a virtual logical storage device.・ Shi Temu request redirector code. 34. The virtual file system access subsystem computer program product of claim 33, wherein a plurality of portions of the remote file system wherein a virtual logical storage file system is maintained by said other device. Wherein each access request further comprises one of the remote file system portions.
The remote access element in response to the access request and initiating an access operation in association with the remote file system portion identified in the access request. Recording a virtual file system access subsystem computer program product to be used. 35. The virtual file system access subsystem computer program product of claim 33, wherein the virtual logical storage file system is one of a plurality of other devices each connected to the network. Wherein each access request further comprises a remote file system part identifier identifying one of said remote file system parts, said remote access element comprising: Responding to the access request and initiating an access operation in association with one of the other devices holding the remote file system portion identified in the access request. Computer·
The medium that recorded the program product. 36. The virtual file system access subsystem computer program product of claim 33, wherein the operating system comprises an MS-DOS and a Windows operating system. A medium in which an access subsystem computer program product is recorded. 37. The virtual file system access subsystem computer program product of claim 33, wherein the network is configured according to a client / server network architecture model and the other device is a server of the server. A virtual file system access subsystem comprising a device, wherein the computer system comprises a client device, and wherein the remote access element comprises a network file system client element;
A medium that records computer program products. 38. The virtual file system access subsystem computer program product of claim 33, wherein said operating system request redirector code device comprises: access·
Medium storing subsystem computer program product: A. Virtual logical storage information store code for storing virtual logical storage information including at least one virtual logical storage identifier; B. Virtual logical storage Retrieves a virtual logical storage device identifier from the device information store and provides the virtual logical storage device identifier to the operating system, whereby the operating system sends an access request identifying the virtual logical storage device identifier to the remote access element. Operating system redirection enabler code to enable redirection. 39. The virtual file system access subsystem computer program product of claim 38, wherein the virtual logical storage device information store stores a plurality of virtual logical storage device identifiers, and the operating system redirection.・ Enabler is
Retrieving the plurality of virtual logical storage device identifiers from the virtual logical storage device information store for provision to an operating system;
Recording a virtual file system access subsystem computer program product characterized by allowing the system to redirect an access request identifying any virtual logical storage device identifier to a remote access element Medium. 40. The virtual file system access subsystem computer program product of claim 38, wherein said virtual logical storage device information store further comprises at least one directory identifier and an associated remote file system. An identifier, wherein the remote file system identifier identifies a portion of the remote file system, and the remote access element uses the remote file system identifier when initiating an access operation. A medium recording a virtual file system access subsystem computer program product, characterized by identifying the other device. 41. The virtual file system access subsystem computer program product of claim 40, wherein said access request includes path information identifying a path through a hierarchical directory system, and An access element identifies a directory to be accessed using the path information and a remote file system associated with the directory to be accessed in response to the access request, the remote access element responding to the access request with A medium recording a virtual file system access subsystem computer program product, in response to initiating an access operation over a network in association with an identified remote file system. 42. The virtual file system access subsystem computer program product according to claim 40, wherein the directory information stored in the virtual logical storage device information store includes a plurality of directory identifiers, and Has at least one sub-directory identifier, each sub-directory identifier has an associated remote file system identifier, and each remote file system identifier is the remote file system identifier of the remote file system. A virtual file system access subsystem, wherein the remote access element uses a remote file system identifier to identify a portion and to identify other devices connected to the network when initiating an access operation. Medium recording a computer product. 43. The virtual file system access subsystem computer program product of claim 42, wherein said access request includes path information identifying a path through a hierarchical directory system, and An access element uses the path information in response to the access request to identify a directory and sub-directory to be accessed in response to the access request and a remote file system associated with the sub-directory to be accessed. A virtual file system access subsystem computer, wherein the remote access element identifies and initiates an access operation on a network in association with the identified remote file system in response to the access request. ·program· Medium recording Rodakuto. 44. The virtual file system access subsystem computer program product of claim 43, wherein at least some of the access requests do not include path information, and wherein the plurality of virtual logical storage device information stores are provided. Enabling the operating system redirection enabler to redirect an operating system-identified access request identifying a virtual logical storage device identifier to a remote access element; The operating system further provides a default directory associated with each virtual logical storage device identifier, wherein the remote access element uses the default directory in response to an access request that does not include path information. Virtual file system accessing subsystem computer program recorded medium product that. 45. A virtual file system access subsystem according to claim 44, wherein said default directory is selectable by an application program. -A medium on which a computer program product is recorded. 46. The virtual file system access subsystem computer program product of claim 44, wherein for at least one directory, each sub-directory identifier is associated with the other one connected to the network. Virtual remote storage system identifier corresponding to the remote file system identifier provided by the device, thereby allowing the remote file system to be accessed to use the virtual logical storage device identifier. A medium on which a file system access subsystem computer program product is recorded. 47. The virtual file system access subsystem computer program product of claim 33, wherein said remote file system portion has an associated mounted state, and said remote access element comprises: Prior to initiating the access operation, it is determined whether the mount status indicates that the remote file system portion is mounted on the virtual logical storage device file system, and (i) if it is mounted, Recording the virtual file system access subsystem computer program product, characterized in that it initiates the access operation and (ii) enables the automounter element to perform the mount operation if not mounted. Medium. 48. The virtual file system access subsystem computer program product of claim 47, wherein the remote access element is mounted if the automounter element indicates a successful mount operation. A medium recording a virtual file system access subsystem computer program product characterized by initiating the access operation associated with a remote file system portion. 49. A virtual file system access subsystem for use in connection with a computer system connected to a computer network, said computer system running a selected operating system; The virtual file system access
The subsystem facilitates access to a plurality of virtual logical storage devices each identified by a virtual logical storage device identifier, each virtual logical storage device being a remote file maintained by another device connected to the computer network. A hierarchical directory system having a virtual logical storage file system including at least a portion of the system, wherein at least some virtual logical storage file systems define a plurality of possible paths each having a path identifier. And hierarchical directories
At least one of the virtual logical storage file systems including a system has an associated default path consisting of one of the possible paths, and the virtual file system access subsystem includes: A. In response to an access request containing a virtual logical storage identifier and the path identifier received by the remote access element from the operating system, the remote access element performs an access operation in association with the virtual logical storage file system held in the virtual logical storage. Initially, during an access operation, a remote access element for accessing a portion of said remote file system contained in said virtual logical storage file system along a path identified by said path identifier; and B. an operating system Is received from the application program An operating system request redirector for enabling an access request identifying a virtual logical storage device to be directed to a remote access element, wherein the operating system receives an access request from the application program and performs remote access. Provided to the element, these access requests are for the access request not including the path identifier received from the application program, together with the path identifier of the default path to the virtual logical storage device identified by the virtual logical storage device. Contains the storage device identifier. 50. The virtual file system access subsystem according to claim 49, wherein said virtual logical storage device file systems for each of said virtual logical storage devices each comprise the same portion of said remote file system portion. Virtual file system access subsystem, which facilitates associating at least a plurality of default paths associated with each virtual logical storage device file system with the same path in a remote file system portion. . 51. The virtual file system access subsystem defined in claim 49, wherein the virtual logical storage device file system associated with at least one of the virtual logical storage device identifiers is held in the other device. A plurality of remote file systems, each access request further comprising
The remote identifying one of the file system parts
The remote access element includes an at least one virtual logical storage device identifier including a file system portion identifier, the remote access element responding to the access request to perform an access operation in association with the remote file system portion identified in the access request. Virtual file system characterized by starting
Access subsystem. 52. The virtual file system access subsystem according to claim 49, wherein each virtual logical storage device file system associated with at least one of said virtual logical storage device identifiers is connected to said network. Each access request including at least one portion of a remote file system held by one of a plurality of other devices, and including at least one virtual logical storage device identifier, further comprises: A remote file system portion identifier identifying one of the remote file system portions, wherein the remote access element responds to the access request in association with another device holding the remote file system portion identified in the access request. Virtual file system characterized by starting operation Access subsystem. 53. The virtual file system access subsystem according to claim 49, wherein the operating system comprises an MS-DOS and a Windows operating system. 54. The virtual file system access subsystem according to claim 49, wherein the network is configured according to a client / server network architecture model, and wherein the other device includes a server device. A virtual file system access subsystem, wherein the system includes a client device and the remote access element comprises a network file system client element. 55. The virtual file system access subsystem of claim 49, wherein the operating system request redirector comprises: A. storing virtual logical storage device information including the respective virtual logical storage device identifiers. B. fetching the virtual logical storage device identifier from the virtual logical storage device information store and providing the virtual logical storage device identifier to the operating system so that the operating system An operating system redirection enabler for enabling access requests identifying the storage device identifier to be redirected to the remote access element. 56. The virtual file system access subsystem according to claim 55, wherein said virtual logical storage device information store further comprises at least one directory identifier and an associated remote file system identifier. Wherein the directory identifier identifies a directory in the virtual logical storage device file system, the remote file system identifier identifies a portion of the remote file system, and an access operation identifying the directory. A virtual file system access subsystem, wherein the remote access element identifies the other device using the remote file system identifier when initiating. 57. The virtual file system access subsystem according to claim 55, wherein said virtual logical storage device information store includes a plurality of directory identifiers,
At least some of the directory identifiers have at least one sub-directory identifier, each sub-directory identifier has an associated remote file system identifier, and each remote file system identifier is associated with the remote file system. Virtual file system access identifying the portion, wherein the remote access element uses a remote file system identifier to identify another device connected to the network when initiating an access operation. ·sub-system. 58. The virtual file system access subsystem according to claim 49, wherein said remote
A file system portion having an associated mount state, wherein the remote access element mounts the remote file system portion on the virtual logical storage file system prior to initiating the access operation; (I) If mounted, start an access operation,
(ii) A virtual file system access subsystem characterized by enabling the automounter element to perform a mount operation if not mounted. 59. The virtual file system access subsystem of claim 58, wherein the automounter element indicates that the mount operation was successful.
A virtual file system access subsystem, wherein the remote access element initiates the access operation associated with the mounted remote file system portion. 60. A method for accessing a virtual file system in a computer system connected to a computer network, said computer system running a selected operating system, said virtual file system access sub-system. The system facilitates access to a plurality of virtual logical storage devices each identified by a virtual logical storage device identifier, each virtual logical storage device being a remote file system maintained by another device connected to a computer network. A virtual logical storage file system that includes at least a portion of the at least some virtual logical storage file systems, wherein at least some of the virtual logical storage file systems have a hierarchical directory system that defines a plurality of possible paths each having a path identifier. Includes hierarchical data At least one of the virtual logical storage file systems including a directory system has an associated default path consisting of one of the possible paths, and the method of accessing the virtual file system comprises the following steps: Including: A. enabling the operating system to direct an access request received from an application program identifying a virtual logical storage device to a remote access element, wherein the operating system receives a request from the application program. An access request is received and provided to a remote access element, the access request comprising a default path to a virtual logical storage device identified by virtual logical storage for an access request that does not include a path identifier received from an application program. B. the virtual logical storage device identifier included with the virtual logical storage device in response to an access request received from the operating system that includes the virtual logical storage device identifier and the path identifier; In connection with a storage device file system, enabling a remote access element to initiate an access operation, wherein the remote access element is configured to access the virtual logical storage device file along a path identified by the path identifier during the access operation. Accessing a portion of the remote file system included in the system. 61. The method of claim 60, wherein the virtual logical storage file systems for each of the virtual logical storage devices each include the same portion of the remote file system portion, thereby at least each virtual logical storage device. A method for accessing a virtual file system, which facilitates matching a plurality of default paths associated with a device file system to the same path in a remote file system portion. 62. The method according to claim 60, wherein the virtual logical storage device file system associated with at least one of the virtual logical storage device identifiers comprises a remote file system of a remote file system held on the other device. A plurality of parts, each access request further including the at least one virtual logical storage device identifier including a remote file system portion identifier identifying one of the remote file system portions; Responding to the access request and initiating an access operation in association with the remote file system portion identified in the access request. 63. The method according to claim 60, wherein a virtual logical storage device file system associated with at least one of said virtual logical storage device identifiers is one of a plurality of other devices connected to said network. Each access request including at least one portion of a remote file system held by the remote file system, wherein each access request including the at least one virtual logical storage device identifier further identifies a remote file system portion.
Including a file system portion identifier, wherein the remote access element initiates an access operation in response to the access request in association with another device holding the remote file system portion identified in the access request. A method for accessing a virtual file system, characterized in that: 64. The method according to claim 60, wherein the operating system comprises an MS-DOS and Windows operating system. 65. The method of claim 60, wherein the network is configured according to a client / server network architecture model, said other device comprises a server device, and said computing system comprises a client device. Accessing the virtual file system, wherein the remote access element comprises a network file system client element. 66. The method of claim 60, wherein the operating system request redirection step comprises the following steps: A. For storing virtual logical storage device information including the respective virtual logical storage device identifiers. B. retrieving the virtual logical storage device identifier from the virtual logical storage device information store and providing the virtual logical storage device identifier to the operating system, whereby the operating system An operating system redirection enabler step for enabling an access request identifying the device identifier to be redirected to a remote access element. 67. The method according to claim 66, wherein said virtual logical storage device information store further stores directory information including at least one directory identifier and an associated remote file system identifier. Identifies a directory within the virtual logical storage file system, the remote file system identifier identifies a portion of the remote file system, and the remote access A method for accessing a virtual file system, wherein an element identifies the other device using the remote file system identifier. 68. The method of claim 66, wherein the virtual logical storage device information store includes a plurality of directory identifiers, at least some of the directory identifiers have at least one sub-directory identifier, The sub-directory identifier has an associated remote file system identifier, each remote file system identifier identifying the portion of the remote file system, and the remote access element using the remote file system identifier. And identifying another device connected to the network when starting an access operation. 69. The method of claim 60, wherein said remote file system portion has an associated mount state, and wherein said remote access element has said mount state prior to initiating said access operation. Indicates whether the remote file system part is mounted on the virtual logical storage device file system, and if (i) mounted, starts an access operation; (ii) must be mounted. A method of accessing a virtual file system, for example, enabling an automounter element to perform a mount operation. 70. The method of claim 69, wherein if the automounter element indicates a successful mount operation, the remote access element initiates the access operation associated with the mounted remote file system portion. A method for accessing a virtual file system. 71. A virtual file system access subsystem computer program product for use in connection with a computer system connected to a computer network, and a medium having recorded thereon, said computer system comprising: Running a selected operating system, the virtual file system access subsystem facilitates access to a plurality of virtual logical storage devices each identified by a virtual logical storage device identifier, The storage device has a virtual logical storage file system that includes at least a portion of a remote file system maintained by another device connected to the computer network, wherein at least some of the virtual logical storage file systems are each Path identifier 1 comprises a hierarchical directory system that defines a plurality of possible paths, one at least of the virtual logical storage device file system including a hierarchical directory system of the possible paths with
An associated default path consisting of a virtual file system access subsystem computer program product recorded on a computer usable medium having computer system readable code; The computer system readable code includes: A. Virtual logical storage held in virtual logical storage in response to an access request including a virtual logical storage identifier received by the remote access element from the operating system and the path identifier. A remote access that initiates an access operation in connection with a device file system, and accesses a portion of the remote file system included in the virtual logical storage file system along the path identified by the path identifier during the access operation. Access element code;
B. Operating system request redirector code for enabling the operating system to direct an access request identifying a virtual logical storage device received from an application program to a remote access element, the operating system request redirector code comprising: The system receives the access requests from the application program and provides them to the remote access element, wherein the access requests are identified by the virtual logical storage device for an access request that does not include the path identifier received from the application program. A virtual logical storage device identifier is included along with the path identifier of the default path for the storage device. 72. The virtual file system access subsystem computer program product of claim 71, wherein said virtual logical storage device file systems for each of said virtual logical storage devices are respectively associated with said remote file system portion. A virtual file comprising the same portion, thereby facilitating at least a plurality of default paths associated with each virtual logical storage file system to correspond to the same path in the remote file system portion. A medium that records a system access subsystem computer program product. 73. The virtual file system access subsystem computer program product of claim 71, wherein the virtual logical storage device file system associated with at least one of the virtual logical storage device identifiers comprises: The at least one portion of the remote file system comprises a plurality of portions of the remote file system held on the other device, each access request further including a remote file system portion identifier identifying one of the remote file system portions. A virtual file system identifier comprising: a virtual logical storage device identifier; and wherein the remote access element initiates an access operation in response to the access request in association with a remote file system portion identified in the access request. Access subsystem computer Medium recording the program product. 74. The virtual file system access subsystem computer program product of claim 71, wherein each of the virtual logical storage device file systems associated with at least one of the virtual logical storage device identifiers. Each access request including at least one portion of a remote file system held by one of a plurality of other devices connected to the network, and including at least one virtual logical storage device identifier, further comprises: A remote file system portion identifier identifying one of the remote file system portions, wherein the remote access element is responsive to the access request and holds the remote file system portion identified in the access request. Start access operation in connection with the device. Virtual file system accessing subsystem computer program medium recording a product characterized by Rukoto. 75. The virtual file system access subsystem computer program product of claim 71, wherein said operating system comprises an MS-DOS and a Windows operating system. A medium that records a system access subsystem computer program product. 76. The virtual file system access subsystem computer program product of claim 71, wherein the network is configured according to a client / server network architecture model, and wherein the other device is a server. A virtual file system access subsystem comprising a device, wherein the computer system comprises a client device, and wherein the remote access element comprises a network file system client element.
A medium that records computer program products. 77. The virtual file system access subsystem computer program product of claim 71, wherein the operating system request redirector code comprises: A. identifying each of the virtual logical storage device identifiers. B. fetching a virtual logical storage device identifier from the virtual logical storage device information store, and providing the virtual logical storage device identifier to the operating system; Operating system redirection enabler code to enable the operating system to redirect access requests identifying the virtual logical storage device identifier to the remote access element. 78. The virtual file system access subsystem computer program product of claim 77, wherein said virtual logical storage device information store further comprises at least one directory identifier and an associated remote file system. Storing directory information including an identifier, wherein the directory identifier identifies a directory in the virtual logical storage device file system, the remote file system identifier identifies a portion of the remote file system, A virtual file system access subsystem computer wherein the remote access element identifies the other device using the remote file system identifier when initiating an access operation to identify a directory. Medium recording data program product. 79. The virtual file system access subsystem computer program product of claim 77, wherein the virtual logical storage device information store includes a plurality of directory identifiers, at least some of the directory identifiers. Is at least one sub-
A directory identifier, each sub-directory identifier having an associated remote file system identifier, each remote file system identifier identifying the portion of the remote file system, and the remote access element being remote A medium recording a virtual file system access subsystem computer program product characterized by using a file system identifier to identify another device connected to the network when starting an access operation. 80. The virtual file system access subsystem computer program product of claim 71, wherein said remote file system portion has an associated mounted state, and said remote access element comprises: Prior to initiating the access operation, it is determined whether the mount status indicates that the remote file system portion is mounted on the virtual logical storage device file system, and (i) if it is mounted, Recording a virtual file system access subsystem computer program product characterized by enabling an automounter element to initiate an access operation, and (ii) perform a mount operation if not mounted, Medium. 81. The virtual file system access subsystem computer program product of claim 80, wherein the remote access element is mounted if the automounter element indicates that the mount operation was successful. A medium recording a virtual file system access subsystem computer program product characterized by initiating the access operation associated with a remote file system portion. 82. A virtual file system access subsystem for use in connection with a computer system connected to a computer network, said computer system running a selected operating system; The virtual file system access
The subsystem facilitates access to a virtual logical storage device identified by a virtual logical storage device identifier, the virtual logical storage device being at least a remote file system maintained by another device connected to the computer network. In those having a virtual logical storage device file system including an identifier for identifying a part, the virtual file system access subsystem includes
Including: A. Initiating an access operation in connection with the virtual logical storage file system held in the virtual logical storage in response to the access request including the virtual logical storage identifier received by the remote access element from the operating system. A remote access element accessing a portion of said remote file system identified by said remote file system portion identifier during an access operation; and B. an access by said operating system to identify a virtual logical storage device to said remote access element. An operating system request redirector to enable request directing. 83. The virtual file system access subsystem according to claim 82, wherein the virtual logical storage file system includes an identifier identifying a plurality of portions of the remote file system held by the other device. Wherein each access request further includes a remote file system portion identifier identifying one of said remote file system portions, wherein said remote access element responds to said access request in response to the remote file identified in said access request. A virtual file system access subsystem characterized by initiating an access operation in association with a system part. 84. The virtual file system access subsystem according to claim 82, wherein the virtual logical storage file system is held by one of a plurality of other devices connected to the network. The access request further comprises an identifier identifying at least each part of the file system, each access request further comprising a remote file system part identifier identifying one of the remote file system parts; A virtual file system access subsystem, in response to an access request, initiating an access operation in association with one of the other devices holding the remote file system portion identified in the access request. 85. The virtual file system access subsystem according to claim 82, wherein the operating system comprises an MS-DOS and a Windows operating system. 86. The virtual file system access subsystem according to claim 82, wherein the network is configured according to a client / server network architecture model, and wherein the other device includes a server device. A virtual file system access subsystem, wherein the system includes a client device and the remote access element comprises a network file system client element. 87. The virtual file system access subsystem according to claim 82, wherein the operating system request redirector includes: A. Virtual logical storage device information including at least one virtual logical storage device identifier. B. retrieve a virtual logical storage device identifier from the virtual logical storage device information store and provide the virtual logical storage device identifier to the operating system so that the operating system An operating system redirection enabler for enabling an access request identifying a logical storage device identifier to be redirected to a remote access element. 88. The virtual file system access subsystem according to claim 87, wherein the virtual logical storage device information store stores a plurality of virtual logical storage device identifiers, and the operating system redirection storage device stores the plurality of virtual logical storage device identifiers.
An accessor for retrieving the plurality of virtual logical storage device identifiers from the virtual logical storage device information store for provision to an operating system, thereby identifying to the operating system any virtual logical storage device identifiers; A virtual file system access subsystem, which enables requests to be redirected to a remote access element. 89. The virtual file system access subsystem according to claim 87, wherein said virtual logical storage device information store further stores remote file system partial identifier information including at least one remote file system identifier. A virtual file system access subsystem, wherein the remote access element identifies the other device using the remote file system identifier when initiating an access operation. 90. The virtual file system access subsystem according to claim 82, wherein said remote
A file system portion having an associated mount state, wherein the remote access element mounts the remote file system portion on the virtual logical storage file system prior to initiating the access operation; (I) If mounted, start an access operation,
(ii) A virtual file system access subsystem characterized by enabling the automounter element to perform a mount operation if not mounted. 91. The virtual file system access subsystem of claim 90, wherein the automounter element indicates that the mount operation was successful.
A virtual file system access subsystem, wherein the remote access element initiates the access operation associated with the mounted remote file system portion. 92. A method for accessing a virtual file system in a computer system connected to a computer network, said computer system running a selected operating system, said virtual file system access sub-system. The system facilitates access to a virtual logical storage device identified by a virtual logical storage device identifier, the virtual logical storage device comprising at least one of a remote file system maintained by another device connected to the computer network. In a method having a virtual logical storage file system including an identifier for identifying a virtual logical storage device, the method for accessing the virtual file system includes the steps of: A Enabling access to the virtual logical storage device in response to an access request received by the remote access element from the operating system, the virtual logical storage device identifier including the virtual logical storage device identifier. In connection with a storage device file system, enabling a remote access element to initiate an access operation, wherein the remote access
Accessing a portion of the remote file system identified by a file system portion identifier. 93. The method according to claim 92, wherein the virtual logical storage file system includes an identifier identifying a plurality of portions of the remote file system held by the other device, each access request further comprising: A remote file system portion identifier identifying one of the remote file system portions, wherein the remote access element is responsive to the access request and associated with the remote file system portion identified in the access request; A method for accessing a virtual file system, comprising the step of initiating an access operation. 94. The method of claim 92, wherein the virtual logical storage file system is at least one of a plurality of remote file systems held by one of a plurality of other devices connected to the network. Wherein each access request further includes a remote file system portion identifier identifying one of the remote file system portions, and wherein the remote access element is responsive to the access request.
A method for accessing a virtual file system, comprising initiating an access operation in association with one of the other devices holding a remote file system portion identified in the access request. 95. The method for accessing a virtual file system according to claim 92, wherein the operating system includes MS-DOS and a window operating system. 96. The method according to claim 92, wherein the network is configured according to a client / server network architecture model, said other device comprises a server device, and said computing system comprises a client device. Accessing the virtual file system, wherein the remote access element comprises a network file system client element. 97. The method of claim 92, wherein the operating system request redirection step includes the following steps: A. Store virtual logical storage device information including at least one virtual logical storage device identifier. B. fetching a virtual logical storage device identifier from the virtual logical storage device information store and providing the virtual logical storage device identifier to the operating system so that the operating system An operating system redirection enabler step for enabling access requests identifying the storage device identifier to be redirected to the remote access element. 98. The method of claim 97, wherein the virtual logical storage information store stores a plurality of virtual logical storage identifiers, and wherein an operating system redirection enabler is provided for providing to the operating system. Retrieving the plurality of virtual logical storage device identifiers from a virtual logical storage device information store, thereby enabling an operating system to redirect an access request identifying any virtual logical storage device identifier to a remote access element Accessing a virtual file system. 99. The method according to claim 97, wherein said virtual logical storage device information store further comprises at least one remote file system identifier.
The remote access element stores file system part identifier information and initiates an access operation.
A method for accessing a virtual file system, comprising identifying the other device using a file system identifier. 100. The method of claim 92, wherein said remote file system portion has an associated mount state, and wherein said remote access element has said mount state prior to initiating said access operation. Indicates whether the remote file system part is mounted on the virtual logical storage device file system, and if (i) mounted, starts an access operation; (ii) must be mounted. A method of accessing a virtual file system, for example, enabling an automounter element to perform a mount operation. 101. The method according to claim 100, wherein
If the automounter element indicates that the mount operation was successful, the remote access element accesses the virtual file system initiating the access operation associated with the mounted remote file system portion. Method. 102. A virtual file system access subsystem computer program product for use in connection with a computer system connected to a computer network, and a medium having recorded thereon, said computer system comprising: Running a selected operating system, the virtual file system access subsystem facilitates access to a virtual logical storage device identified by a virtual logical storage device identifier, the virtual logical storage device Having a virtual logical storage file system including an identifier identifying at least a portion of a remote file system maintained by another device connected to a computer network, wherein the virtual file system access
The subsystem computer program product is recorded on a computer usable medium having a computer system readable code, said computer system readable code including: A. The remote access element is provided by the operating system. In response to the access request including the received virtual logical storage device identifier, an access operation is initiated in connection with the virtual logical storage device file system held in the virtual logical storage device, and identified by the remote file system partial identifier during the access operation. A remote access element code for accessing a portion of said remote file system that is executed; and B. an operating system for enabling the operating system to direct the remote access element to access requests that identify a virtual logical storage device. The stem request redirector code. 103. The virtual file system access subsystem computer program product of claim 102, wherein a plurality of portions of the remote file system wherein a virtual logical storage file system is maintained by said other device. And each access request further includes a remote file system portion identifier identifying one of the remote file system portions, wherein the remote access element is responsive to the access request in the access request. A medium recording a virtual file system access subsystem computer program product characterized by initiating an access operation in association with an identified remote file system portion. 104. The virtual file system access subsystem computer program product of claim 102, wherein the virtual logical storage file system is provided by one of a plurality of other devices connected to the network. Multiple remote
Each access request further includes a remote file system portion identifier identifying one of the remote file system portions, the remote access element including an identifier identifying at least each portion of the file system; Responding to the request, initiating an access operation in association with one of the other devices holding the remote file system portion identified in the access request. The medium that recorded the program product. 105. The virtual file system access subsystem computer program product of claim 102, wherein the operating system comprises an MS-DOS and a Windows operating system. A medium in which an access subsystem computer program product is recorded. 106. The virtual file system access subsystem computer program product of claim 102, wherein the network is configured by a client / server network architecture model and the other device is a server of the computer.・
A virtual file system access subsystem computer program product characterized in that the computer system includes a client device and the remote access element comprises a network file system client element. Medium. 107. The virtual file system access subsystem computer program product of claim 102, wherein said operating system
A medium recording a virtual file system access subsystem computer program product, wherein the system request redirector code device comprises: A. Virtual logic including at least one virtual logical storage device identifier B. fetching a virtual logical storage device identifier from the virtual logical storage device information store, and providing the virtual logical storage device identifier to the operating system; Operating system redirection enabler code to enable the operating system to redirect access requests identifying the virtual logical storage device identifier to a remote access element. 108. The virtual file system access subsystem computer program product of claim 107, wherein the virtual logical storage device information store stores a plurality of virtual logical storage device identifiers, and the operating system redirection. An enabler retrieves the plurality of virtual logical storage device identifiers from the virtual logical storage device information store for provision to an operating system, thereby identifying any virtual logical storage device identifier to the operating system; A medium recording a virtual file system access subsystem computer program product, wherein the access request can be redirected to a remote access element. 109. The virtual file system access subsystem computer program product of claim 107, wherein said virtual logical storage device information store further comprises at least one remote file system identifier. A virtual file system access subsystem, storing system part identifier information, wherein the remote access element identifies the other device using the remote file system identifier when initiating an access operation.
A medium that records computer program products. 110. The virtual file system access subsystem computer program product of claim 102, wherein said remote file system portion has an associated mounted state, and said remote access element comprises: Prior to initiating the access operation, determining whether the mount status indicates that the remote file system portion is mounted on the virtual logical storage device file system;
A virtual file system access subsystem computer characterized by enabling an automounter element to perform an access operation if mounted, and (ii) perform a mount operation if not mounted. The medium that recorded the program product. 111. The virtual file system access subsystem computer program product of claim 110, wherein the remote access element is mounted if the automounter element indicates that the mount operation was successful. A virtual file system access subsystem for initiating the access operation associated with a remote file system portion.
A medium that records computer program products.