Browse Prior Art Database

METHOD OF PROVIDING WILDCARDS WITHIN EXPORT ENTRIES IN THE EXPORT LIST

IP.com Disclosure Number: IPCOM000014332D
Original Publication Date: 2000-Feb-01
Included in the Prior Art Database: 2003-Jun-19
Document File: 1 page(s) / 40K

Publishing Venue

IBM

Abstract

Disclosed is a method to significantly reduce the administrative overhead of Network File System NFS) servers when the number of exported filesystems is large and dynamic. Current implementations of NFS servers require that the administrator define each exported filesystem individually. This can be time-consuming, confusing, and error-prone. The resulting list may be somewhat long and difficult to read, also. Clients receiving the list may not be able to determine which filesystems in the list are accessible by them. It is convenient to make the list shorter and more lucid. One way to make a shorter list is to allow an NFS server to export a generic filesystem name that multiple users can use to mount client-specific filesystems. The client-specific filesystem is derived from information received with each client mount request. An implementation of this idea might use different "Mount-Variables" which represent the client's authenticated user ID and his or her initial working directory as defined on the server system. Consider the case where a client's authenticated user ID is represented by the "Mount-Variable" %USERID and the initial working directory for the client is represented by the "Mount-Variable" %IWDIR. Figure 1 shows examples of these "Mount-Variables" as used by IBM's VM/ESA operation system. Figure 1. Example of export entries using "Mount-Variables"

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 60% of the total text.

Page 1 of 1

  METHOD OF PROVIDING WILDCARDS WITHIN EXPORT ENTRIES IN THE EXPORT LIST

    Disclosed is a method to significantly reduce the administrative overhead of Network File System NFS) servers when the number of exported filesystems is large and dynamic. Current implementations of NFS servers require that the administrator define each exported filesystem individually. This can be time-consuming, confusing, and error-prone. The resulting list may be somewhat long and difficult to read, also. Clients receiving the list may not be able to determine which filesystems in the list are accessible by them. It is convenient to make the list shorter and more lucid.

One way to make a shorter list is to allow an NFS server to export a generic filesystem name that multiple users can use to mount client-specific filesystems. The client-specific filesystem is derived from information received with each client mount request. An implementation of this idea might use different "Mount-Variables" which represent the client's authenticated user ID and his or her initial working directory as defined on the server system.

Consider the case where a client's authenticated user ID is represented by the "Mount-Variable" %USERID and the initial working directory for the client is represented by the "Mount-Variable" %IWDIR. Figure 1 shows examples of these "Mount-Variables" as used by IBM's VM/ESA operation system.

Figure 1. Example of export entries using "Mount-Variables"

As an example of how this wor...