Attachment 18747 Details for Bug 33559 – file.diff

[patch] file.diff

file.diff (text/plain), 12.97 KB, created by marcolz on 2002-01-05 01:40:01 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: marcolz

Created: 2002-01-05 01:40:01 UTC

Size: 12.97 KB

patch

obsolete

>--- /usr/src/share/doc/IPv6/IMPLEMENTATION	Sat Jan  5 00:57:11 2002
>+++ /usr/src/share/doc/IPv6/IMPLEMENTATION	Sat Jan  5 01:15:06 2002
>@@ -187,7 +187,7 @@
> In such cases DAD may fail, because DAD engine sees inbound NS packet
> (actually from the node itself) and considers it as a sign of duplicate.
> In this case, drivers should be corrected to honor IFF_SIMPLEX behavior.
>-For example, you may need to check source MAC address on a inbound packet,
>+For example, you may need to check source MAC address on an inbound packet,
> and reject it if it is from the node itself.
> You may also want to look at #if condition marked "heuristics" in
> sys/netinet6/nd6_nbr.c:nd6_dad_timer() as workaround (note that the code
>@@ -1188,7 +1188,7 @@
> based on RFC2553bis discussion.
> 
> If you look at multiple IPv6 implementations, you will be able to see
>-both definitions.  As an userland programmer, the most portable way of
>+both definitions.  As a userland programmer, the most portable way of
> dealing with it is to:
> (1) ensure ss_family and/or ss_len are available on the platform, by using
>     GNU autoconf,
>--- /usr/src/share/doc/papers/diskperf/tests.ms	Sat Jan  5 01:07:48 2002
>+++ /usr/src/share/doc/papers/diskperf/tests.ms	Sat Jan  5 01:07:51 2002
>@@ -71,7 +71,7 @@
> I/O support routines is commonly used and these routines buffer
> data in similar block sizes.
> .PP
>-For each test run, a empty eight Kilobyte block
>+For each test run, an empty eight Kilobyte block
> file system was created in the target
> storage system.
> Then each of the four tests was run and timed.
>--- /usr/src/share/doc/papers/diskperf/motivation.ms	Sat Jan  5 01:15:41 2002
>+++ /usr/src/share/doc/papers/diskperf/motivation.ms	Sat Jan  5 01:16:19 2002
>@@ -45,7 +45,7 @@
> cost competitive
> in the area of disk storage for the first time.
> Emulex's entry into the VAX 11/780 SBI controller
>-field, the SC780, represented a important choice for us to examine, given
>+field, the SC780, represented an important choice for us to examine, given
> our previous success with their VAX 11/750 SC750 controller and
> their UNIBUS controllers.
> The Fujitsu 2351A
>--- /usr/src/share/doc/papers/malloc/intro.ms	Sat Jan  5 01:16:46 2002
>+++ /usr/src/share/doc/papers/malloc/intro.ms	Sat Jan  5 01:17:16 2002
>@@ -42,7 +42,7 @@
> In the C language, there exists a little used interface to the stack,
> .B alloca(3) ,
> which will explicitly allocate space on the stack.
>-This is not a interface to the kernel, but merely an adjustment
>+This is not an interface to the kernel, but merely an adjustment
> done to the stack-pointer such that space will be available and
> unharmed by any subroutine calls yet to be made while the context
> of the current subroutine is intact.
>@@ -58,7 +58,7 @@
> .B brk(2) .
> The argument to brk(2) is a pointer to where the process wants the
> heap to end.
>-There is also a interface called
>+There is also an interface called
> .B sbrk(2)
> taking an increment to the current end of the heap, but this is merely a
> .B libc
>--- /usr/src/share/doc/papers/sysperf/4.t	Sat Jan  5 01:21:12 2002
>+++ /usr/src/share/doc/papers/sysperf/4.t	Sat Jan  5 01:21:26 2002
>@@ -670,7 +670,7 @@
> message recipient causing almost a continuous sequence of sync operations).
> .PP
> The hashed data base files were
>-installed in all mail programs, resulting in a order of magnitude
>+installed in all mail programs, resulting in an order of magnitude
> speedup on large distribution lists.  The code in \fI/bin/mail\fP
> that notifies the \fIcomsat\fP program when mail has been delivered to
> a user was changed to cache host table lookups, resulting in a similar
>--- /usr/src/share/doc/psd/21.ipc/3.t	Sat Jan  5 01:17:54 2002
>+++ /usr/src/share/doc/psd/21.ipc/3.t	Sat Jan  5 01:18:14 2002
>@@ -245,7 +245,7 @@
> .DE
> .PP
> In the NS domain, protocols are indicated by the "client type"
>-field of a IDP header.  No protocol database exists; see section
>+field of an IDP header.  No protocol database exists; see section
> 5 for more information.
> .NH 2
> Service names
>--- /usr/src/share/doc/smm/01.setup/3.t	Sat Jan  5 01:18:37 2002
>+++ /usr/src/share/doc/smm/01.setup/3.t	Sat Jan  5 01:19:09 2002
>@@ -1318,7 +1318,7 @@
> and
> .Xr lfs_cleanerd (8)
> for more information.
>-For a in-depth description of the implementation and performance
>+For an in-depth description of the implementation and performance
> characteristics of log-structured filesystems in general,
> and this one in particular, see Dr. Margo Seltzer's doctoral thesis,
> available from the University of California Computer Science Department.
>--- /usr/src/share/doc/smm/06.nfs/1.t	Sat Jan  5 00:59:37 2002
>+++ /usr/src/share/doc/smm/06.nfs/1.t	Sat Jan  5 01:28:51 2002
>@@ -83,7 +83,7 @@
> .sh 1 "Mount Problems"
> .pp
> There are several problems that can be encountered at the time of an NFS
>-mount, ranging from a unresponsive NFS server (crashed, network partitioned
>+mount, ranging from an unresponsive NFS server (crashed, network partitioned
> from client, etc.) to various interoperability problems between different
> NFS implementations.
> .pp
>@@ -230,7 +230,7 @@
> 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
>--- /usr/src/share/doc/smm/06.nfs/2.t	Sat Jan  5 01:00:45 2002
>+++ /usr/src/share/doc/smm/06.nfs/2.t	Sat Jan  5 01:01:42 2002
>@@ -127,7 +127,7 @@
> an expired write caching lease to push dirty writes.
> .pp
> The server maintains a \fBmodify_revision\fR number for each file. It is
>-defined as a unsigned quadword integer that is never zero and that must
>+defined as an unsigned quadword integer that is never zero and that must
> increase whenever the corresponding file is modified on the server.
> It is used
> by the client to determine whether or not cached data for the file is
>@@ -400,7 +400,7 @@
> .(l
>         typedef unsigned hyper modifyrev;
> .)l
>-The "modifyrev" is a unsigned quadword integer value that is never zero
>+The "modifyrev" is an unsigned quadword integer value that is never zero
> and increases every time the corresponding file is modified on the server.
> .ip \(bu
> nqnfs_time
>--- /usr/src/share/doc/smm/18.net/7.t	Sat Jan  5 01:08:14 2002
>+++ /usr/src/share/doc/smm/18.net/7.t	Sat Jan  5 01:08:30 2002
>@@ -115,7 +115,7 @@
> always precedes a request to accept a connection.
> .IP PRU_CONNECT
> .br
>-The ``connect'' request indicates the user wants to a establish
>+The ``connect'' request indicates the user wants to establish
> an association.  The \fIaddr\fP parameter supplied describes
> the peer to be connected to.  The effect of a connect request
> may vary depending on the protocol.  Virtual circuit protocols,
>--- /usr/src/share/doc/usd/18.msdiffs/ms.diffs	Sat Jan  5 01:09:02 2002
>+++ /usr/src/share/doc/usd/18.msdiffs/ms.diffs	Sat Jan  5 01:09:18 2002
>@@ -268,7 +268,7 @@
> \&.OH  \'\ef\^IThe  -mx  Macros\'\'Page  %\ef\^P\'
> \&.EH  \'\ef\^IPage  %\'\'The  -mx  Macros\ef\^P\'
> .DE
>-Note that it would be a error to have an apostrophe in the header text;
>+Note that it would be an error to have an apostrophe in the header text;
> if you need one, you will have to use a different delimiter
> around the left, center, and right portions of the title.
> You can use any character as a delimiter, provided it doesn't appear
>--- /usr/src/share/examples/IPv6/USAGE	Sat Jan  5 01:19:33 2002
>+++ /usr/src/share/examples/IPv6/USAGE	Sat Jan  5 01:19:52 2002
>@@ -3,7 +3,7 @@
> 	$KAME: USAGE,v 1.33 2000/11/22 10:22:57 itojun Exp $
> 	$FreeBSD: src/share/examples/IPv6/USAGE,v 1.1.2.2 2001/07/03 11:01:24 ume Exp $
> 
>-This is a introduction of how to use the commands provided in the KAME
>+This is an introduction of how to use the commands provided in the KAME
> kit.  For more information, please refer to each man page.
> 
> 
>--- /usr/src/share/examples/isdn/FAQ	Sat Jan  5 01:10:05 2002
>+++ /usr/src/share/examples/isdn/FAQ	Sat Jan  5 01:29:38 2002
>@@ -312,7 +312,7 @@
> since I have to wait for ppp negotiation to complete (I don't get a message
> from isdnd for that). If I'm lucky I have my connection after 3 seconds,
> but 8 seconds should suffice for worst case (the first HUP without a sleep
>-sometimes even succeeded on an slow 486/33 with 8MB RAM, more HUPs don't hurt).
>+sometimes even succeeded on a slow 486/33 with 8MB RAM, more HUPs don't hurt).
> 
> I'm really interested in some more elegant method.
> 
>@@ -1016,7 +1016,7 @@
> 
> Q: Hi,
> 
>-   I am trying to set up an ELSA QuickStep 1000pro PCI ISDN adaptor in a FreeBSD
>+   I am trying to set up a ELSA QuickStep 1000pro PCI ISDN adaptor in a FreeBSD
>    3.3 box. I configured the kernel according to the i4b.ps documentation. At
>    boottime, these messages are displayed:
> 
>@@ -1070,7 +1070,7 @@
>    isdn_fsdev="NO"
>    isdn_flags=""
> 
>-   had to do that if i want to run isdnd as an daemon service, 'cause the
>+   had to do that if i want to run isdnd as a daemon service, 'cause the
>    defaults in /etc/defaults/rc.conf are:
> 
>    isdn_fsdev="/dev/ttyv4"         # Output device for fullscreen mode (or NO for daemon mode).
>--- /usr/src/share/examples/isdn/Overview	Sat Jan  5 01:12:05 2002
>+++ /usr/src/share/examples/isdn/Overview	Sat Jan  5 01:13:57 2002
>@@ -111,7 +111,7 @@
>    routines. These routines handle the card/manufacturer specific stuff
>    required to talk to a particular card.
> 
>-   This addresses of the read/write routines are put into a arrays found
>+   These addresses of the read/write routines are put into arrays found
>    in struct isic_softc and they are later called by the macros:
> 
>    ISAC_READ(r), ISAC_WRITE(r,v), ISAC_RDFIFO(b,s), ISAC_WRFIFO(b,s),
>--- /usr/src/share/examples/meteor/test-n.c	Sat Jan  5 00:57:58 2002
>+++ /usr/src/share/examples/meteor/test-n.c	Sat Jan  5 00:57:41 2002
>@@ -1,5 +1,5 @@
> /* A simple program to test the communication between the matrox meteor
>- * driver and an user application in the continous sync capture mode.
>+ * driver and a user application in the continous sync capture mode.
>  * 
>  * First the driver clears the mask and decrements the counter like it
>  * would in a normal application. Then it purpose does not handle these
>--- /usr/src/share/man/man0/title.urm	Sat Jan  5 01:26:59 2002
>+++ /usr/src/share/man/man0/title.urm	Sat Jan  5 01:27:25 2002
>@@ -1227,7 +1227,7 @@
> In particular, for an overview see ``The \s-1UNIX\s+1 Time-Sharing System'' (PSD:1)
> by Ritchie and Thompson; for a tutorial see
> ``\s8\s-1UNIX\s+1\s10 for Beginners'' (USD:1) by Kernighan,
>-and for an guide to the new features of this latest version, see
>+and for a guide to the new features of this latest version, see
> ``Berkeley Software Architecture Manual (4.4 Edition)'' (PSD:5).
> .LP
> Within the area it surveys, this volume attempts to be timely, complete
>--- /usr/src/share/man/man4/man4.i386/wl.4	Sat Jan  5 01:06:23 2002
>+++ /usr/src/share/man/man4/man4.i386/wl.4	Sat Jan  5 01:06:34 2002
>@@ -49,7 +49,7 @@
> .Pp
> The card has three fundamental hardware
> units, a so-called PSA or programmable storage area, a radio modem,
>-and a ethernet lan controller.  The latter component is the
>+and an ethernet lan controller.  The latter component is the
> ancient (and not very honorable) Intel 82586 ethernet chip.
> Fundamentally it appears to the operating system as an ethernet system,
> and speaks IEEE MAC addresses.  The radio modem simply translates
>--- /usr/src/share/man/man4/keyboard.4	Sat Jan  5 01:10:31 2002
>+++ /usr/src/share/man/man4/keyboard.4	Sat Jan  5 01:10:41 2002
>@@ -117,7 +117,7 @@
> .Pp
> The function keys can be programmed using the SETFKEY ioctl call.
> .Pp
>-This ioctl takes a argument of the type fkeyarg_t:
>+This ioctl takes an argument of the type fkeyarg_t:
> .Bd -literal -offset indent
> 		struct fkeyarg {
> 			u_short	keynum;
>--- /usr/src/share/man/man9/kernacc.9	Sat Jan  5 00:55:49 2002
>+++ /usr/src/share/man/man9/kernacc.9	Sat Jan  5 00:56:04 2002
>@@ -74,7 +74,7 @@
> .Fn useracc
> considers
> .Fa addr
>-to represent an user space address.
>+to represent a user space address.
> The process context to use for this
> operation is taken from the global variable
> .Va curproc .
>--- /usr/src/share/man/man9/inittodr.9	Sat Jan  5 01:11:14 2002
>+++ /usr/src/share/man/man9/inittodr.9	Sat Jan  5 01:11:23 2002
>@@ -69,7 +69,7 @@
> .\" If the battery-backed clock appears invalid, and
> .\" .Fa base
> .\" appears non-sensical or was not provided (was given as zero),
>-.\" a arbitrary base (typically some time in the late 1970s)
>+.\" an arbitrary base (typically some time in the late 1970s)
> .\" will be used.
> .It
> If the battery-backed clock does not have a valid time,
>--- /usr/src/share/termcap/map3270	Sat Jan  5 01:30:10 2002
>+++ /usr/src/share/termcap/map3270	Sat Jan  5 01:30:28 2002
>@@ -925,7 +925,7 @@
> #
> # MAP3270 for the IBM PC
> # Nearly identical to the MS-Kermit UCB 227.14 keyboard which in turn was
>-# an modest improvement of the BIJOU Yterm keyboard.
>+# a modest improvement of the BIJOU Yterm keyboard.
> # Includes underlying ADM3A keystrokes for full S/1 compatibiliy.
> # Adds some Ctrl-keypad keys to compensate for TN3270 ROMBIOS dependency
> # which prevents separate use of the keypad plus and minus keys, and adds

Actions: View | Diff

Attachments on bug 33559: 18746 | 18747 | 18748