From 86f7487fb6a0b8dd9e3a699ad48d6e99504a67ff Mon Sep 17 00:00:00 2001 From: schweikh Date: Mon, 30 Dec 2002 21:18:15 +0000 Subject: Fix typos, mostly s/ an / a / where appropriate and a few s/an/and/ Add FreeBSD Id tag where missing. --- share/doc/papers/sysperf/5.t | 14 ++++++++------ share/doc/smm/06.nfs/1.t | 6 ++++-- 2 files changed, 12 insertions(+), 8 deletions(-) (limited to 'share/doc') diff --git a/share/doc/papers/sysperf/5.t b/share/doc/papers/sysperf/5.t index 5d70a9a..ff008c3 100644 --- a/share/doc/papers/sysperf/5.t +++ b/share/doc/papers/sysperf/5.t @@ -31,6 +31,8 @@ .\" .\" @(#)5.t 5.1 (Berkeley) 4/17/91 .\" +.\" $FreeBSD$ +.\" .ds RH Functional Extensions .NH Functional Extensions @@ -69,7 +71,7 @@ The organization of network interfaces has been reworked to more cleanly support multiple network protocols. Network interfaces no longer contain a host's address on that network; instead -each interface contains a pointer to a list of addresses +each interface contains a pointer to a list of addresses assigned to that interface. This permits a single interface to support, for example, Internet protocols at the same time as XNS protocols. @@ -80,7 +82,7 @@ for 10 megabyte/second Ethernet\(dg \(dg Ethernet is a trademark of Xerox. .FE has been made more flexible by allowing hosts to -act as an ``clearing house'' for hosts that do +act as a ``clearing house'' for hosts that do not support ARP. In addition, system managers have more control over the contents of the ARP translation cache and may interactively interrogate and modify @@ -100,7 +102,7 @@ Number of File Descriptors .PP To allow full use of the many descriptor based services available, the previous hard limit of 30 open files per process has been relaxed. -The changes entailed generalizing \fIselect\fP to handle arrays of +The changes entailed generalizing \fIselect\fP to handle arrays of 32-bit words, removing the dependency on file descriptors from the page table entries, and limiting most of the linear scans of a process's file table. @@ -169,7 +171,7 @@ Users could not write their own return from exceptions; Many existing programs depend on interrupted system calls. The restartable system call semantics of 4.2BSD signals caused many of these programs to break. -To simplify porting of programs from inferior versions of +To simplify porting of programs from inferior versions of .UX the \fIsigvec\fP system call has been extended so that programmers may specify that system calls are not to be @@ -179,14 +181,14 @@ System Logging .PP A system logging facility has been added that sends kernel messages to the -syslog daemon for logging in /usr/adm/messages and possibly for +syslog daemon for logging in /usr/adm/messages and possibly for printing on the system console. The revised scheme for logging messages eliminates the time lag in updating the messages file, unifies the format of kernel messages, provides a finer granularity of control over the messages that get printed on the console, -and eliminates the degradation in response during the printing of +and eliminates the degradation in response during the printing of low-priority kernel messages. Recoverable system errors and common resource limitations are logged using this facility. diff --git a/share/doc/smm/06.nfs/1.t b/share/doc/smm/06.nfs/1.t index f68a863..0806cad 100644 --- a/share/doc/smm/06.nfs/1.t +++ b/share/doc/smm/06.nfs/1.t @@ -34,6 +34,8 @@ .\" .\" @(#)1.t 8.1 (Berkeley) 6/8/93 .\" +.\" $FreeBSD$ +.\" .sh 1 "NFS Implementation" .pp The 4.4BSD implementation of NFS and the alternate protocol nicknamed @@ -213,7 +215,7 @@ request/reply message in a single UDP datagram. Since UDP does not guarantee datagram delivery, the Remote Procedure Call (RPC) layer times out and retransmits an RPC request if -no RPC reply has been received. Since this round trip timeout (RTO) value +no RPC reply has been received. Since this round trip timeout (RTO) value is for the entire RPC operation, including RPC message transmission to the server, queuing at the server for an nfsd, performing the RPC and sending the RPC reply message back to the client, it can be highly variable @@ -230,7 +232,7 @@ Also, with an 8Kbyte read/write data size that must normally be fragmented at the IP layer for transmission.\** .(f \**6 IP fragments for an Ethernet, -which has an maximum transmission unit of 1500bytes. +which has a maximum transmission unit of 1500bytes. .)f For IP fragments to be successfully reassembled into the IP datagram at the receive end, all -- cgit v1.1