Spector A., and M. Kazar, "Uniting File Systems", UNIX Review, 7(3), pp. 61-69, March 1989.  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... now uses as a transmission backbone the National Science Foundation Network (NSFNET) Extensive monitoring and capacity planning are being done for the NSFNET backbone; still, as the demand for this capacity grows, and as resource intensive applications such as wide area file system management [Sp89] increasingly use the backbone, effective congestion control policies will be a critical requirement. Only a few mechanisms currently exist in Internet hosts and gateways to avoid or control congestion. The mechanisms for handling congestion set forth in the specifications for the DoD Internet ....

A. Spector, M. Kazar, Uniting File Systems. Unix Review, Vol. 7, No. 3, March, 1989.

....and directory service is based upon the use of system name for access to the contents of files. The directory service can be better described by introducing its operations. Based on our requirements and motivated with the result of an analysis of the [Braban and Schlenk 1989] Sandberg 1986] and [Spector and Kazar 1989] our proposed operations of a directory service are as follows: create dir, open dir, read dir, insert dir, un name, change, get names, close, delete and ch dir. 8.2 Access Control Each RHODOS file has an owner and the signature of the owner, i.e. the userID is recorded in the system name of ....

Spector, A.Z. and Kazar, M.L. Uniting File Systems. Unix Review 7, No. 3 pp. 61-70

....to further extend AFS so that it provided wide area file service. The underlying AFS communication component was adapted to better handle the widely varying channel characteristics encountered by intra site and inter site operations. A more detailed history of AFS evolution may be found in [3] and [18] 3.2 System Goals At a high level, the AFS designers chose to extend the single machine unix computing environment into a WADFS service. The unix system, in all of its numerous incarnations, AFS 3 Design Goals 6 September 3, 1991 5:08 AFS 3 Architectural Overview is an important ....

....time. AFS 3 Design Goals 10 September 3, 1991 5:08 AFS 3 Architectural Overview Chapter 4 AFS High Level Design 4.1 Introduction This chapter presents an overview of the system architecture for the AFS 3 WADFS. Different treatments of the AFS system may be found in several documents, including [3], 4] 5] and [2] Certain system features discussed here are examined in more detail in the set of accompanying AFS programmer specification documents. After the archtectural overview, the system goals enumerated in Chapter 3 are revisited, and the contribution of the various AFS design ....

Alfred Z. Spector, Michael L. Kazar, Uniting File Systems, Unix Review, March 1989,

....services provide detailed user models that capture and retain information about user classes and user usage histories. Current effort within the RLF project is directed to accomplishing this advanced library system. For example, activities are underway to employ the Andrew File System (AFS) SK89] to provide truly distributed libraries. Additional experiments in the area of library asset interchange are planned so that assets may be freely distributed among cooperating libraries. The RLF already supports all three of the interaction paradigms shown in the figure. SLIDE 17 indicates some ....

A. Z. Spector and M. L. Kazar. Uniting File Systems. Unix Review, 7(3), March 1989.

....years, a number of projects have been initiated with the goal of building some type of wide area distributed application. Some efforts focus on extending older paradigms into wider distribution, most commonly in the realm of mail, news, and file service [Gifford et al. 1985, Quarterman 1990, Spector Kazar 1989] Other efforts focus on interconnecting information repositories to provide easy access to libraries and other information from any point in the Internet [Evans et al. 1989, Kahle Medlar 1991, Kahn Cerf 1988, Lynch 1990] Physical scientists are exploring the possibilities for supporting ....

A. Z. Spector and M. L. Kazar. Uniting File Systems. Unix Review, pp. 61-71, Mar. 1989.

....protocol and a security model that recognizes the existence of many administrative domains. Large scale file systems include AFS [6] and its spinoffs, Decorum [10] and IFS (Institutional File System) 5] Experiments involving AFS as a nation wide file service have been going on for years [23]. This effort has focused on stitching together distinct administrative domains so as to provide a single unified naming and protection space. However, some changes are needed to the present authentication model in order to support the possibility of a mobile client relocating in a new domain. In ....

A. Z. Spector and M. L. Kazar. Uniting File Systems. UNIX Review, 7(3):61--71, March 1989.

....the client caches the whole file, usually in its local disk, and accesses its local copy thereafter, thus freeing the file server from serving every file read write. With this policy, AFS is able to scale gracefully and supports more clients. The last policy is large trunk transfer. AFS 3. 0 [4] is said to have incorporated this policy. However, since detail description of this policy could not be found in the literature, we created our own interpretation, which may or may not be the same as what is in AFS 3.0. With our approach, when a client opens a file, it informs the file server to ....

Spector, Alfred Z. and Michael L. Kazar. Uniting File Systems. Unix Review, 7(3):61-70, Mar 1989.

No context found.

Spector A., and M. Kazar, "Uniting File Systems", UNIX Review, 7(3), pp. 61-69, March 1989.

No context found.

, pp. 60-71

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC