/share/doc/smm/06.nfs/ref.t

  1.\" Copyright (c) 1993
  2.\"	The Regents of the University of California.  All rights reserved.
  3.\"
  4.\" This document is derived from software contributed to Berkeley by
  5.\" Rick Macklem at The University of Guelph.
  6.\"
  7.\" Redistribution and use in source and binary forms, with or without
  8.\" modification, are permitted provided that the following conditions
  9.\" are met:
 10.\" 1. Redistributions of source code must retain the above copyright
 11.\"    notice, this list of conditions and the following disclaimer.
 12.\" 2. Redistributions in binary form must reproduce the above copyright
 13.\"    notice, this list of conditions and the following disclaimer in the
 14.\"    documentation and/or other materials provided with the distribution.
 15.\" 3. All advertising materials mentioning features or use of this software
 16.\"    must display the following acknowledgement:
 17.\"	This product includes software developed by the University of
 18.\"	California, Berkeley and its contributors.
 19.\" 4. Neither the name of the University nor the names of its contributors
 20.\"    may be used to endorse or promote products derived from this software
 21.\"    without specific prior written permission.
 22.\"
 23.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 24.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 25.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 26.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 27.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 28.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 29.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 30.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 31.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 32.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 33.\" SUCH DAMAGE.
 34.\"
 35.\"	@(#)ref.t	8.1 (Berkeley) 6/8/93
 36.\"
 37.sh 1 "Bibliography"
 38.ip [Baker91] 16
 39Mary Baker and John Ousterhout, Availability in the Sprite Distributed
 40File System, In \fIOperating System Review\fR, (25)2, pg. 95-98,
 41April 1991.
 42.ip [Baker91a] 16
 43Mary Baker, Private Email Communication, May 1991.
 44.ip [Burrows88] 16
 45Michael Burrows, Efficient Data Sharing, Technical Report #153,
 46Computer Laboratory, University of Cambridge, Dec. 1988.
 47.ip [Gray89] 16
 48Cary G. Gray and David R. Cheriton, Leases: An Efficient Fault-Tolerant
 49Mechanism for Distributed File Cache Consistency, In \fIProc. of the
 50Twelfth ACM Symposium on Operating Systems Principals\fR, Litchfield Park,
 51AZ, Dec. 1989.
 52.ip [Howard88] 16
 53John H. Howard, Michael L. Kazar, Sherri G. Menees, David A. Nichols,
 54M. Satyanarayanan, Robert N. Sidebotham and Michael J. West,
 55Scale and Performance in a Distributed File System, \fIACM Trans. on
 56Computer Systems\fR, (6)1, pg 51-81, Feb. 1988.
 57.ip [Juszczak89] 16
 58Chet Juszczak, Improving the Performance and Correctness of an NFS Server,
 59In \fIProc. Winter 1989 USENIX Conference,\fR pg. 53-63, San Diego, CA, January 1989.
 60.ip [Keith90] 16
 61Bruce E. Keith, Perspectives on NFS File Server Performance Characterization,
 62In \fIProc. Summer 1990 USENIX Conference\fR, pg. 267-277, Anaheim, CA,
 63June 1990.
 64.ip [Kent87] 16
 65Christopher. A. Kent, \fICache Coherence in Distributed Systems\fR,
 66Research Report 87/4,
 67Digital Equipment Corporation Western Research Laboratory, April 1987.
 68.ip [Kent87a] 16
 69Christopher. A. Kent and Jeffrey C. Mogul,
 70\fIFragmentation Considered Harmful\fR, Research Report 87/3,
 71Digital Equipment Corporation Western Research Laboratory, Dec. 1987.
 72.ip [Macklem91] 16
 73Rick Macklem, Lessons Learned Tuning the 4.3BSD Reno Implementation of the
 74NFS Protocol, In \fIProc. Winter USENIX Conference\fR, pg. 53-64,
 75Dallas, TX, January 1991.
 76.ip [Nelson88] 16
 77Michael N. Nelson, Brent B. Welch, and John K. Ousterhout, Caching in the
 78Sprite Network File System, \fIACM Transactions on Computer Systems\fR (6)1
 79pg. 134-154, February 1988.
 80.ip [Nowicki89] 16
 81Bill Nowicki, Transport Issues in the Network File System, In
 82\fIComputer Communication Review\fR, pg. 16-20, Vol. 19, Number 2, April 1989.
 83.ip [Ousterhout90] 16
 84John K. Ousterhout, Why Aren't Operating Systems Getting Faster As Fast as
 85Hardware? In \fIProc. Summer 1990 USENIX Conference\fR, pg. 247-256, Anaheim,
 86CA, June 1990.
 87.ip [Pendry93] 16
 88Jan-Simon Pendry, 4.4 BSD Automounter Reference Manual, In
 89\fIsrc/usr.sbin/amd/doc directory of 4.4 BSD distribution tape\fR.
 90.ip [Reid90] 16
 91Jim Reid, N(e)FS: the Protocol is the Problem, In
 92\fIProc. Summer 1990 UKUUG Conference\fR,
 93London, England, July 1990.
 94.ip [Sandberg85] 16
 95Russel Sandberg, David Goldberg, Steve Kleiman, Dan Walsh, and Bob Lyon,
 96Design and Implementation of the Sun Network filesystem, In \fIProc. Summer
 971985 USENIX Conference\fR, pages 119-130, Portland, OR, June 1985.
 98.ip [Schroeder85] 16
 99Michael D. Schroeder, David K. Gifford and Roger M. Needham, A Caching
100File System For A Programmer's Workstation, In \fIProc. of the Tenth
101ACM Symposium on Operating Systems Principals\fR, pg. 25-34, Orcas Island,
102WA, Dec. 1985.
103.ip [Srinivasan89] 16
104V. Srinivasan and Jeffrey. C. Mogul, \fISpritely NFS: Implementation and
105Performance of Cache-Consistency Protocols\fR, Research Report 89/5,
106Digital Equipment Corporation Western Research Laboratory, May 1989.
107.ip [Steiner88] 16
108Jennifer G. Steiner, Clifford Neuman and Jeffrey I. Schiller,
109Kerberos: An Authentication Service for Open Network Systems, In
110\fIProc. Winter 1988 USENIX Conference\fR, Dallas, TX, February 1988.
111.ip [Stern] 16
112Hal Stern, \fIManaging NFS and NIS\fR, O'Reilly and Associates,
113ISBN 0-937175-75-7.
114.ip [Sun87] 16
115Sun Microsystems Inc., \fIXDR: External Data Representation Standard\fR,
116RFC1014, Network Information Center, SRI International, June 1987.
117.ip [Sun88] 16
118Sun Microsystems Inc., \fIRPC: Remote Procedure Call Protocol Specification Version 2\fR,
119RFC1057, Network Information Center, SRI International, June 1988.
120.ip [Sun89] 16
121Sun Microsystems Inc., \fINFS: Network File System Protocol Specification\fR,
122ARPANET Working Group Requests for Comment, DDN Network Information Center,
123SRI International, Menlo Park, CA, March 1989, RFC-1094.