Attachment #18747 for bug #33559

Lines 71-77 Link Here

(-)/usr/src/share/doc/papers/diskperf/tests.ms (-1 / +1 lines)
71	I/O support routines is commonly used and these routines buffer	71	I/O support routines is commonly used and these routines buffer
72	data in similar block sizes.	72	data in similar block sizes.
73	.PP	73	.PP
74	For each test run, a empty eight Kilobyte block	74	For each test run, an empty eight Kilobyte block
75	file system was created in the target	75	file system was created in the target
76	storage system.	76	storage system.
77	Then each of the four tests was run and timed.	77	Then each of the four tests was run and timed.

Lines 45-51 Link Here

(-)/usr/src/share/doc/papers/diskperf/motivation.ms (-1 / +1 lines)
45	cost competitive	45	cost competitive
46	in the area of disk storage for the first time.	46	in the area of disk storage for the first time.
47	Emulex's entry into the VAX 11/780 SBI controller	47	Emulex's entry into the VAX 11/780 SBI controller
48	field, the SC780, represented a important choice for us to examine, given	48	field, the SC780, represented an important choice for us to examine, given
49	our previous success with their VAX 11/750 SC750 controller and	49	our previous success with their VAX 11/750 SC750 controller and
50	their UNIBUS controllers.	50	their UNIBUS controllers.
51	The Fujitsu 2351A	51	The Fujitsu 2351A

Lines 42-48 Link Here

(-)/usr/src/share/doc/papers/malloc/intro.ms (-2 / +2 lines)
42	In the C language, there exists a little used interface to the stack,	42	In the C language, there exists a little used interface to the stack,
43	.B alloca(3) ,	43	.B alloca(3) ,
44	which will explicitly allocate space on the stack.	44	which will explicitly allocate space on the stack.
45	This is not a interface to the kernel, but merely an adjustment	45	This is not an interface to the kernel, but merely an adjustment
46	done to the stack-pointer such that space will be available and	46	done to the stack-pointer such that space will be available and
47	unharmed by any subroutine calls yet to be made while the context	47	unharmed by any subroutine calls yet to be made while the context
48	of the current subroutine is intact.	48	of the current subroutine is intact.
Lines 58-64 Link Here
58	.B brk(2) .	58	.B brk(2) .
59	The argument to brk(2) is a pointer to where the process wants the	59	The argument to brk(2) is a pointer to where the process wants the
60	heap to end.	60	heap to end.
61	There is also a interface called	61	There is also an interface called
62	.B sbrk(2)	62	.B sbrk(2)
63	taking an increment to the current end of the heap, but this is merely a	63	taking an increment to the current end of the heap, but this is merely a
64	.B libc	64	.B libc

Lines 670-676 Link Here

(-)/usr/src/share/doc/papers/sysperf/4.t (-1 / +1 lines)
670	message recipient causing almost a continuous sequence of sync operations).	670	message recipient causing almost a continuous sequence of sync operations).
671	.PP	671	.PP
672	The hashed data base files were	672	The hashed data base files were
673	installed in all mail programs, resulting in a order of magnitude	673	installed in all mail programs, resulting in an order of magnitude
674	speedup on large distribution lists. The code in \fI/bin/mail\fP	674	speedup on large distribution lists. The code in \fI/bin/mail\fP
675	that notifies the \fIcomsat\fP program when mail has been delivered to	675	that notifies the \fIcomsat\fP program when mail has been delivered to
676	a user was changed to cache host table lookups, resulting in a similar	676	a user was changed to cache host table lookups, resulting in a similar

Lines 245-251 Link Here

(-)/usr/src/share/doc/psd/21.ipc/3.t (-1 / +1 lines)
245	.DE	245	.DE
246	.PP	246	.PP
247	In the NS domain, protocols are indicated by the "client type"	247	In the NS domain, protocols are indicated by the "client type"
248	field of a IDP header. No protocol database exists; see section	248	field of an IDP header. No protocol database exists; see section
249	5 for more information.	249	5 for more information.
250	.NH 2	250	.NH 2
251	Service names	251	Service names

Lines 1318-1324 Link Here

(-)/usr/src/share/doc/smm/01.setup/3.t (-1 / +1 lines)
1318	and	1318	and
1319	.Xr lfs_cleanerd (8)	1319	.Xr lfs_cleanerd (8)
1320	for more information.	1320	for more information.
1321	For a in-depth description of the implementation and performance	1321	For an in-depth description of the implementation and performance
1322	characteristics of log-structured filesystems in general,	1322	characteristics of log-structured filesystems in general,
1323	and this one in particular, see Dr. Margo Seltzer's doctoral thesis,	1323	and this one in particular, see Dr. Margo Seltzer's doctoral thesis,
1324	available from the University of California Computer Science Department.	1324	available from the University of California Computer Science Department.

Lines 83-89 Link Here

(-)/usr/src/share/doc/smm/06.nfs/1.t (-2 / +2 lines)
83	.sh 1 "Mount Problems"	83	.sh 1 "Mount Problems"
84	.pp	84	.pp
85	There are several problems that can be encountered at the time of an NFS	85	There are several problems that can be encountered at the time of an NFS
86	mount, ranging from a unresponsive NFS server (crashed, network partitioned	86	mount, ranging from an unresponsive NFS server (crashed, network partitioned
87	from client, etc.) to various interoperability problems between different	87	from client, etc.) to various interoperability problems between different
88	NFS implementations.	88	NFS implementations.
89	.pp	89	.pp
Lines 230-236 Link Here
230	that must normally be fragmented at the IP layer for transmission.\**	230	that must normally be fragmented at the IP layer for transmission.\**
231	.(f	231	.(f
232	\**6 IP fragments for an Ethernet,	232	\**6 IP fragments for an Ethernet,
233	which has an maximum transmission unit of 1500bytes.	233	which has a maximum transmission unit of 1500bytes.
234	.)f	234	.)f
235	For IP fragments to be successfully reassembled into	235	For IP fragments to be successfully reassembled into
236	the IP datagram at the receive end, all	236	the IP datagram at the receive end, all

Lines 127-133 Link Here

(-)/usr/src/share/doc/smm/06.nfs/2.t (-2 / +2 lines)
127	an expired write caching lease to push dirty writes.	127	an expired write caching lease to push dirty writes.
128	.pp	128	.pp
129	The server maintains a \fBmodify_revision\fR number for each file. It is	129	The server maintains a \fBmodify_revision\fR number for each file. It is
130	defined as a unsigned quadword integer that is never zero and that must	130	defined as an unsigned quadword integer that is never zero and that must
131	increase whenever the corresponding file is modified on the server.	131	increase whenever the corresponding file is modified on the server.
132	It is used	132	It is used
133	by the client to determine whether or not cached data for the file is	133	by the client to determine whether or not cached data for the file is
Lines 400-406 Link Here
400	.(l	400	.(l
401	typedef unsigned hyper modifyrev;	401	typedef unsigned hyper modifyrev;
402	.)l	402	.)l
403	The "modifyrev" is a unsigned quadword integer value that is never zero	403	The "modifyrev" is an unsigned quadword integer value that is never zero
404	and increases every time the corresponding file is modified on the server.	404	and increases every time the corresponding file is modified on the server.
405	.ip \(bu	405	.ip \(bu
406	nqnfs_time	406	nqnfs_time

Lines 115-121 Link Here

(-)/usr/src/share/doc/smm/18.net/7.t (-1 / +1 lines)
115	always precedes a request to accept a connection.	115	always precedes a request to accept a connection.
116	.IP PRU_CONNECT	116	.IP PRU_CONNECT
117	.br	117	.br
118	The ``connect'' request indicates the user wants to a establish	118	The ``connect'' request indicates the user wants to establish
119	an association. The \fIaddr\fP parameter supplied describes	119	an association. The \fIaddr\fP parameter supplied describes
120	the peer to be connected to. The effect of a connect request	120	the peer to be connected to. The effect of a connect request
121	may vary depending on the protocol. Virtual circuit protocols,	121	may vary depending on the protocol. Virtual circuit protocols,

Lines 268-274 Link Here

(-)/usr/src/share/doc/usd/18.msdiffs/ms.diffs (-1 / +1 lines)
268	\&.OH \'\ef\^IThe -mx Macros\'\'Page %\ef\^P\'	268	\&.OH \'\ef\^IThe -mx Macros\'\'Page %\ef\^P\'
269	\&.EH \'\ef\^IPage %\'\'The -mx Macros\ef\^P\'	269	\&.EH \'\ef\^IPage %\'\'The -mx Macros\ef\^P\'
270	.DE	270	.DE
271	Note that it would be a error to have an apostrophe in the header text;	271	Note that it would be an error to have an apostrophe in the header text;
272	if you need one, you will have to use a different delimiter	272	if you need one, you will have to use a different delimiter
273	around the left, center, and right portions of the title.	273	around the left, center, and right portions of the title.
274	You can use any character as a delimiter, provided it doesn't appear	274	You can use any character as a delimiter, provided it doesn't appear

Lines 3-9 Link Here

(-)/usr/src/share/examples/IPv6/USAGE (-1 / +1 lines)
3	$KAME: USAGE,v 1.33 2000/11/22 10:22:57 itojun Exp $	3	$KAME: USAGE,v 1.33 2000/11/22 10:22:57 itojun Exp $
4	$FreeBSD: src/share/examples/IPv6/USAGE,v 1.1.2.2 2001/07/03 11:01:24 ume Exp $	4	$FreeBSD: src/share/examples/IPv6/USAGE,v 1.1.2.2 2001/07/03 11:01:24 ume Exp $
5		5
6	This is a introduction of how to use the commands provided in the KAME	6	This is an introduction of how to use the commands provided in the KAME
7	kit. For more information, please refer to each man page.	7	kit. For more information, please refer to each man page.
8		8
9		9




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 a slow 486/33 with 8MB RAM, more HUPs don't hurt).

I'm really interested in some more elegant method.



Q: Hi,

   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:


   isdn_fsdev="NO"
   isdn_flags=""

   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).

Lines 111-117 Link Here

(-)/usr/src/share/examples/isdn/Overview (-1 / +1 lines)
111	routines. These routines handle the card/manufacturer specific stuff	111	routines. These routines handle the card/manufacturer specific stuff
112	required to talk to a particular card.	112	required to talk to a particular card.
113		113
114	This addresses of the read/write routines are put into a arrays found	114	These addresses of the read/write routines are put into arrays found
115	in struct isic_softc and they are later called by the macros:	115	in struct isic_softc and they are later called by the macros:
116		116
117	ISAC_READ(r), ISAC_WRITE(r,v), ISAC_RDFIFO(b,s), ISAC_WRFIFO(b,s),	117	ISAC_READ(r), ISAC_WRITE(r,v), ISAC_RDFIFO(b,s), ISAC_WRFIFO(b,s),

Lines 1-5 Link Here

(-)/usr/src/share/examples/meteor/test-n.c (-1 / +1 lines)
1	/* A simple program to test the communication between the matrox meteor	1	/* A simple program to test the communication between the matrox meteor
2	* driver and an user application in the continous sync capture mode.	2	* driver and a user application in the continous sync capture mode.
3	*	3	*
4	* First the driver clears the mask and decrements the counter like it	4	* First the driver clears the mask and decrements the counter like it
5	* would in a normal application. Then it purpose does not handle these	5	* would in a normal application. Then it purpose does not handle these

Lines 1227-1233 Link Here

(-)/usr/src/share/man/man0/title.urm (-1 / +1 lines)
1227	In particular, for an overview see ``The \s-1UNIX\s+1 Time-Sharing System'' (PSD:1)	1227	In particular, for an overview see ``The \s-1UNIX\s+1 Time-Sharing System'' (PSD:1)
1228	by Ritchie and Thompson; for a tutorial see	1228	by Ritchie and Thompson; for a tutorial see
1229	``\s8\s-1UNIX\s+1\s10 for Beginners'' (USD:1) by Kernighan,	1229	``\s8\s-1UNIX\s+1\s10 for Beginners'' (USD:1) by Kernighan,
1230	and for an guide to the new features of this latest version, see	1230	and for a guide to the new features of this latest version, see
1231	``Berkeley Software Architecture Manual (4.4 Edition)'' (PSD:5).	1231	``Berkeley Software Architecture Manual (4.4 Edition)'' (PSD:5).
1232	.LP	1232	.LP
1233	Within the area it surveys, this volume attempts to be timely, complete	1233	Within the area it surveys, this volume attempts to be timely, complete

Lines 49-55 Link Here

(-)/usr/src/share/man/man4/man4.i386/wl.4 (-1 / +1 lines)
49	.Pp	49	.Pp
50	The card has three fundamental hardware	50	The card has three fundamental hardware
51	units, a so-called PSA or programmable storage area, a radio modem,	51	units, a so-called PSA or programmable storage area, a radio modem,
52	and a ethernet lan controller. The latter component is the	52	and an ethernet lan controller. The latter component is the
53	ancient (and not very honorable) Intel 82586 ethernet chip.	53	ancient (and not very honorable) Intel 82586 ethernet chip.
54	Fundamentally it appears to the operating system as an ethernet system,	54	Fundamentally it appears to the operating system as an ethernet system,
55	and speaks IEEE MAC addresses. The radio modem simply translates	55	and speaks IEEE MAC addresses. The radio modem simply translates

Lines 117-123 Link Here

(-)/usr/src/share/man/man4/keyboard.4 (-1 / +1 lines)
117	.Pp	117	.Pp
118	The function keys can be programmed using the SETFKEY ioctl call.	118	The function keys can be programmed using the SETFKEY ioctl call.
119	.Pp	119	.Pp
120	This ioctl takes a argument of the type fkeyarg_t:	120	This ioctl takes an argument of the type fkeyarg_t:
121	.Bd -literal -offset indent	121	.Bd -literal -offset indent
122	struct fkeyarg {	122	struct fkeyarg {
123	u_short keynum;	123	u_short keynum;

Lines 74-80 Link Here

(-)/usr/src/share/man/man9/kernacc.9 (-1 / +1 lines)
74	.Fn useracc	74	.Fn useracc
75	considers	75	considers
76	.Fa addr	76	.Fa addr
77	to represent an user space address.	77	to represent a user space address.
78	The process context to use for this	78	The process context to use for this
79	operation is taken from the global variable	79	operation is taken from the global variable
80	.Va curproc .	80	.Va curproc .

Lines 69-75 Link Here

(-)/usr/src/share/man/man9/inittodr.9 (-1 / +1 lines)
69	.\" If the battery-backed clock appears invalid, and	69	.\" If the battery-backed clock appears invalid, and
70	.\" .Fa base	70	.\" .Fa base
71	.\" appears non-sensical or was not provided (was given as zero),	71	.\" appears non-sensical or was not provided (was given as zero),
72	.\" a arbitrary base (typically some time in the late 1970s)	72	.\" an arbitrary base (typically some time in the late 1970s)
73	.\" will be used.	73	.\" will be used.
74	.It	74	.It
75	If the battery-backed clock does not have a valid time,	75	If the battery-backed clock does not have a valid time,

Lines 925-931 Link Here

(-)/usr/src/share/termcap/map3270 (-1 / +1 lines)
925	#	925	#
926	# MAP3270 for the IBM PC	926	# MAP3270 for the IBM PC
927	# Nearly identical to the MS-Kermit UCB 227.14 keyboard which in turn was	927	# Nearly identical to the MS-Kermit UCB 227.14 keyboard which in turn was
928	# an modest improvement of the BIJOU Yterm keyboard.	928	# a modest improvement of the BIJOU Yterm keyboard.
929	# Includes underlying ADM3A keystrokes for full S/1 compatibiliy.	929	# Includes underlying ADM3A keystrokes for full S/1 compatibiliy.
930	# Adds some Ctrl-keypad keys to compensate for TN3270 ROMBIOS dependency	930	# Adds some Ctrl-keypad keys to compensate for TN3270 ROMBIOS dependency
931	# which prevents separate use of the keypad plus and minus keys, and adds	931	# which prevents separate use of the keypad plus and minus keys, and adds

Return to bug 33559

Lines 187-193 Link Here

(-)/usr/src/share/doc/IPv6/IMPLEMENTATION (-2 / +2 lines)
187	In such cases DAD may fail, because DAD engine sees inbound NS packet	187	In such cases DAD may fail, because DAD engine sees inbound NS packet
188	(actually from the node itself) and considers it as a sign of duplicate.	188	(actually from the node itself) and considers it as a sign of duplicate.
189	In this case, drivers should be corrected to honor IFF_SIMPLEX behavior.	189	In this case, drivers should be corrected to honor IFF_SIMPLEX behavior.
190	For example, you may need to check source MAC address on a inbound packet,	190	For example, you may need to check source MAC address on an inbound packet,
191	and reject it if it is from the node itself.	191	and reject it if it is from the node itself.
192	You may also want to look at #if condition marked "heuristics" in	192	You may also want to look at #if condition marked "heuristics" in
193	sys/netinet6/nd6_nbr.c:nd6_dad_timer() as workaround (note that the code	193	sys/netinet6/nd6_nbr.c:nd6_dad_timer() as workaround (note that the code
Lines 1188-1194 Link Here
1188	based on RFC2553bis discussion.	1188	based on RFC2553bis discussion.
1189		1189
1190	If you look at multiple IPv6 implementations, you will be able to see	1190	If you look at multiple IPv6 implementations, you will be able to see
1191	both definitions. As an userland programmer, the most portable way of	1191	both definitions. As a userland programmer, the most portable way of
1192	dealing with it is to:	1192	dealing with it is to:
1193	(1) ensure ss_family and/or ss_len are available on the platform, by using	1193	(1) ensure ss_family and/or ss_len are available on the platform, by using
1194	GNU autoconf,	1194	GNU autoconf,

Lines 312-318 Link Here

(-)/usr/src/share/examples/isdn/FAQ (-3 / +3 lines)
312	since I have to wait for ppp negotiation to complete (I don't get a message	312	since I have to wait for ppp negotiation to complete (I don't get a message
313	from isdnd for that). If I'm lucky I have my connection after 3 seconds,	313	from isdnd for that). If I'm lucky I have my connection after 3 seconds,
314	but 8 seconds should suffice for worst case (the first HUP without a sleep	314	but 8 seconds should suffice for worst case (the first HUP without a sleep
315	sometimes even succeeded on an slow 486/33 with 8MB RAM, more HUPs don't hurt).	315	sometimes even succeeded on a slow 486/33 with 8MB RAM, more HUPs don't hurt).
316		316
317	I'm really interested in some more elegant method.	317	I'm really interested in some more elegant method.
318		318
Lines 1016-1022 Link Here
1016		1016
1017	Q: Hi,	1017	Q: Hi,
1018		1018
1019	I am trying to set up an ELSA QuickStep 1000pro PCI ISDN adaptor in a FreeBSD	1019	I am trying to set up a ELSA QuickStep 1000pro PCI ISDN adaptor in a FreeBSD
1020	3.3 box. I configured the kernel according to the i4b.ps documentation. At	1020	3.3 box. I configured the kernel according to the i4b.ps documentation. At
1021	boottime, these messages are displayed:	1021	boottime, these messages are displayed:
1022		1022
Lines 1070-1076 Link Here
1070	isdn_fsdev="NO"	1070	isdn_fsdev="NO"
1071	isdn_flags=""	1071	isdn_flags=""
1072		1072
1073	had to do that if i want to run isdnd as an daemon service, 'cause the	1073	had to do that if i want to run isdnd as a daemon service, 'cause the
1074	defaults in /etc/defaults/rc.conf are:	1074	defaults in /etc/defaults/rc.conf are:
1075		1075
1076	isdn_fsdev="/dev/ttyv4" # Output device for fullscreen mode (or NO for daemon mode).	1076	isdn_fsdev="/dev/ttyv4" # Output device for fullscreen mode (or NO for daemon mode).