Cosmetic changes for better HTML output.

11 files changed, 44 insertions, 39 deletions

diff --git a/share/doc/papers/diskperf/appendix.ms b/share/doc/papers/diskperf/appendix.ms
index ccc4878..e059249 100644
--- a/share/doc/papers/diskperf/appendix.ms
+++ b/share/doc/papers/diskperf/appendix.ms
@@ -31,12 +31,13 @@
 .\"
 .\"	@(#)appendix.ms	6.2 (Berkeley) 4/16/91
 .\"
-.nr H2 1
+.\" .nr H2 1
 .ds RH Appendix A
-.SH
+.NH
 \s+2Appendix A\s0
-.SH
+.NH 2
 read_8192
+.PP
 .DS
 #define	BUFSIZ 8192
 main( argc, argv)
@@ -50,8 +51,9 @@ char **argv;
 		read(j, buf, BUFSIZ);
 }
 .DE
-.SH
+.NH 2
 write_4096
+.PP
 .DS
 #define	BUFSIZ 4096
 main( argc, argv)
@@ -65,8 +67,9 @@ char **argv;
 		write(j, buf, BUFSIZ);
 }
 .DE
-.SH
+.NH 2
 write_8192
+.PP
 .DS
 #define	BUFSIZ 8192
 main( argc, argv)
@@ -81,8 +84,9 @@ char **argv;
 }
 .DE
 .bp
-.SH
+.NH 2
 rewrite_8192
+.PP
 .DS
 #define	BUFSIZ 8192
 main( argc, argv)
diff --git a/share/doc/papers/diskperf/conclusions.ms b/share/doc/papers/diskperf/conclusions.ms
index b69d9a8..2abdcc3 100644
--- a/share/doc/papers/diskperf/conclusions.ms
+++ b/share/doc/papers/diskperf/conclusions.ms
@@ -95,7 +95,7 @@ transfers are used.
 .ds RH Acknowledgements
 .nr H2 1
 .sp 1
-.SH
+.NH
 \s+2Acknowledgements\s0
 .PP
 We thank Paul Massigilia and Bill Grace
@@ -116,7 +116,7 @@ Contract No. N00039-82-C-0235.
 .ds RH References
 .nr H2 1
 .sp 1
-.SH
+.NH
 \s+2References\s0
 .LP
 .IP [McKusick83] 20
diff --git a/share/doc/papers/fsinterface/fsinterface.ms b/share/doc/papers/fsinterface/fsinterface.ms
index 5f9caff..e8462fc 100644
--- a/share/doc/papers/fsinterface/fsinterface.ms
+++ b/share/doc/papers/fsinterface/fsinterface.ms
@@ -93,7 +93,7 @@ This proposal and the rationale underlying its development
 have been presented to major software vendors
 as an early step toward convergence on a compatible filesystem interface.
 .AE
-.SH
+.NH
 Introduction
 .PP
 As network communications and workstation environments
@@ -154,7 +154,7 @@ the implementations were done, and from the filesystems originally targetted
 by the designs.
 These differences are summarized in the following sections
 within the limitations of the published specifications.
-.SH
+.NH
 Design goals
 .PP
 There are several design goals which, in varying degrees,
@@ -224,7 +224,7 @@ at the expense of performance.
 Although the performance of RFS is yet to be seen,
 AT&T seems to have considered compatibility far more important than modularity
 or performance.
-.SH
+.NH
 Differences among filesystem interfaces
 .PP
 The existing filesystem interfaces may be characterized
@@ -290,7 +290,7 @@ is the name lookup operation.
 that obtain a ``file handle'' for a vnode which may be given
 to a client by a server, such that the vnode may be retrieved
 upon later presentation of the file handle.)
-.SH
+.NH
 Name translation issues
 .PP
 Each of the systems described include a mechanism for performing
@@ -443,7 +443,7 @@ but the VFS interface forces all filesystems to share the problem.
 This restriction against locking between calls also
 forces duplication of work during file creation and deletion.
 This is considered unacceptable.
-.SH
+.NH
 Support facilities and other interactions
 .PP
 Several support facilities are used by the current
@@ -543,7 +543,7 @@ which may create problems with reentrancy,
 the style of the system call interface,
 and the conventions for synchronization
 (sleep/wakeup, handling of interrupted system calls, semaphores).
-.SH
+.NH
 The Berkeley Proposal
 .PP
 The Sun VFS interface has been most widely used of the three described here.
@@ -765,7 +765,7 @@ enum	uio_seg {
 	UIO_USERISPACE		/* from user I space */
 };
 .DE
-.SH
+.NH
 File and filesystem operations
 .PP
 With the introduction of the data structures used by the filesystem
@@ -1082,7 +1082,7 @@ struct vattr {
 \fB+\fP	u_long	va_bytes1;	/* reserved if va_bytes not a quad */
 };
 .DE
-.SH
+.NH
 Conclusions
 .PP
 The Sun VFS filesystem interface is the most widely used generic
@@ -1096,7 +1096,7 @@ The proposed interface is now being implemented by the Computer Systems
 Research Group at Berkeley.
 If the design succeeds in improving the flexibility and performance
 of the filesystem layering, it will be advanced as a model interface.
-.SH
+.NH
 Acknowledgements
 .PP
 The filesystem interface described here is derived from Sun's VFS interface.
@@ -1105,7 +1105,7 @@ We are indebted to members of the Sun and DEC system groups
 for long discussions of the issues involved.
 .br
 .ne 2i
-.SH
+.NH
 References
 
 .IP Brownbridge82 \w'Satyanarayanan85\0\0'u
diff --git a/share/doc/papers/kerntune/4.t b/share/doc/papers/kerntune/4.t
index fcd0ad0..38bae43 100644
--- a/share/doc/papers/kerntune/4.t
+++ b/share/doc/papers/kerntune/4.t
@@ -59,7 +59,7 @@ These changes reduce the percentage of time spent running
 in the system by nearly 9%.
 .nr H2 1
 .ds RH Acknowledgements
-.SH
+.NH
 \s+2Acknowledgements\s0
 .PP
 I would like to thank Robert Elz for sharing his ideas and 
@@ -73,7 +73,7 @@ Contract No. N00039-82-C-0235.
 .ds RH References
 .nr H2 1
 .sp 2
-.SH
+.NH
 \s+2References\s-2
 .LP
 .IP [Bentley81] 20
diff --git a/share/doc/papers/memfs/1.t b/share/doc/papers/memfs/1.t
index a065844..e079be9 100644
--- a/share/doc/papers/memfs/1.t
+++ b/share/doc/papers/memfs/1.t
@@ -33,7 +33,7 @@
 .\"
 .nr PS 11
 .nr VS 13
-.SH
+.NH
 Introduction
 .PP
 This paper describes the motivation for and implementation of
@@ -150,7 +150,7 @@ We await the results of others trying this approach.
 .[
 Ohta
 .]
-.SH
+.NH
 Implementation
 .PP
 The current implementation took less time to write than did this paper.
@@ -268,7 +268,7 @@ but have not been recently accessed (or have been deleted).
 .[
 leffler
 .]
-.SH
+.NH
 Performance
 .PP
 The performance of the current memory-based filesystem is determined by
@@ -313,7 +313,7 @@ Here, the low latency of the memory-based filesystem is
 noticeable compared to the disk-based filesystem,
 as a synchronous operation can be done with
 just two context switches instead of incurring the disk latency.
-.SH
+.NH
 Future Work
 .PP
 The most obvious shortcoming of the current implementation
diff --git a/share/doc/papers/memfs/A.t b/share/doc/papers/memfs/A.t
index c1938c8..09d8e93 100644
--- a/share/doc/papers/memfs/A.t
+++ b/share/doc/papers/memfs/A.t
@@ -34,7 +34,7 @@
 .bp
 .nr PS 10
 .nr VS 12
-.SH
+.NH
 Appendix A - Implementation Details
 .LP
 .nf
diff --git a/share/doc/papers/memfs/tmac.srefs b/share/doc/papers/memfs/tmac.srefs
index 6245118..96199b8 100644
--- a/share/doc/papers/memfs/tmac.srefs
+++ b/share/doc/papers/memfs/tmac.srefs
@@ -142,7 +142,8 @@ in \\f2\\*([B\\f1\c
 .\}
 .el .sp 27p
 .Li 2 30.5P
-\fBReferences\fP
+.NH
+References
 .br
 .if \\n(Ns<2 \{\
 .	nr Ns 1
diff --git a/share/doc/papers/newvm/1.t b/share/doc/papers/newvm/1.t
index 036adee..7b66674 100644
--- a/share/doc/papers/newvm/1.t
+++ b/share/doc/papers/newvm/1.t
@@ -43,7 +43,7 @@ This section of the paper describes the current design,
 points out the current technological trends,
 and attempts to define the new design considerations that should
 be taken into account in a new virtual memory design.
-.SH
+.NH 2
 Implementation of 4.3BSD virtual memory
 .PP
 All Berkeley Software Distributions through 4.3BSD
@@ -71,7 +71,7 @@ to contain newly faulted pages.
 If a previously accessed page that has been pushed to swap is once
 again used, a free page is reallocated and filled from the swap area
 [Babaoglu79], [Someren84].
-.SH
+.NH 2
 Design assumptions for 4.3BSD virtual memory
 .PP
 The design criteria for the current virtual memory implementation
@@ -110,7 +110,7 @@ Given the high cost of memory there was little incentive to have
 the kernel keep track of the contents of the swap area once a process
 exited since it could almost as easily and quickly be reread from the
 file system.
-.SH
+.NH 2
 New influences
 .PP
 In the ten years since the current virtual memory system was designed,
@@ -190,7 +190,7 @@ User Interface
 This section outlines our new virtual memory interface as it is
 currently envisioned.
 The details of the system call interface are contained in Appendix A.
-.SH
+.NH 2
 Regions
 .PP
 The virtual memory interface is designed to support both large,
@@ -259,7 +259,7 @@ processes that wish to attach to the region.
 Such a descriptor may be bound into the UNIX file system
 name space so that other processes can find it just as
 they would with a mapped file.
-.SH
+.NH 2
 Shared memory as high speed interprocess communication
 .PP
 The primary use envisioned for shared memory is to
diff --git a/share/doc/papers/newvm/a.t b/share/doc/papers/newvm/a.t
index 7248e25..5a9bac4 100644
--- a/share/doc/papers/newvm/a.t
+++ b/share/doc/papers/newvm/a.t
@@ -36,7 +36,7 @@
 .ne 2i
 .NH
 Appendix A \- Virtual Memory Interface
-.SH
+.NH 2
 Mapping pages
 .PP
 The system supports sharing of data between processes
@@ -148,7 +148,7 @@ caddr_t addr; int len;
 This call deletes the mappings for the specified address range,
 and causes further references to addresses within the range
 to generate invalid memory references.
-.SH
+.NH 2
 Page protection control
 .PP
 A process can control the protection of pages using the call
@@ -159,7 +159,7 @@ caddr_t addr; int len, prot;
 This call changes the specified pages to have protection \fIprot\fP\|.
 Not all implementations will guarantee protection on a page basis;
 the granularity of protection changes may be as large as an entire region.
-.SH
+.NH 2
 Giving and getting advice
 .PP
 A process that has knowledge of its memory behavior may
@@ -188,7 +188,7 @@ caddr_t addr; int len; result char *vec;
 Here the current core residency of the pages is returned
 in the character array \fIvec\fP, with a value of 1 meaning
 that the page is in-core.
-.SH
+.NH 2
 Synchronization primitives
 .PP
 Primitives are provided for synchronization using semaphores in shared memory.
diff --git a/share/doc/papers/nqnfs/nqnfs.me b/share/doc/papers/nqnfs/nqnfs.me
index ce9003e..fba2a3b 100644
--- a/share/doc/papers/nqnfs/nqnfs.me
+++ b/share/doc/papers/nqnfs/nqnfs.me
@@ -56,10 +56,7 @@ Association.
 .nr PS 12
 .ps 12
 .ce
-\fBAbstract\fR
-.nr PS 10
-.ps 10
-.pp
+.AB
 There are some constraints inherent in the NFS\(tm\(mo protocol
 that result in performance limitations
 for high performance
@@ -75,6 +72,8 @@ The emphasis is on observed performance of a
 preliminary implementation of the protocol, in order to show
 how well this design works
 and to suggest possible areas for further improvement.
+.AE
+
 .sh 1 "Introduction"
 .pp
 It has been observed that
diff --git a/share/doc/papers/px/Makefile b/share/doc/papers/px/Makefile
index f0d1ea8..0bd4323 100644
--- a/share/doc/papers/px/Makefile
+++ b/share/doc/papers/px/Makefile
@@ -8,6 +8,7 @@ EXTRA=	fig1.1.n fig1.2.n fig1.3.n fig2.3.raw fig2.4.n fig3.2.n \
 	fig3.3.n table2.1.n table2.2.n table2.3.n table3.1.n tmac.p
 OBJS=	fig2.3.n
 CLEANFILES+=fig2.3.n
+MACROS= -ms
 
 USE_SOELIM=	yes
 USE_SOELIMPP=	yes