Converted 'vmunix' to 'kernel'.

6 files changed, 44 insertions, 44 deletions

diff --git a/share/doc/smm/01.setup/2.t b/share/doc/smm/01.setup/2.t
index ddc4f7e..396f956 100644
--- a/share/doc/smm/01.setup/2.t
+++ b/share/doc/smm/01.setup/2.t
@@ -370,7 +370,7 @@ prompt for a kernel file to boot:
 HP433 CPU
 Boot
 .R
-\fB:\fP \fI/vmunix\fP
+\fB:\fP \fI/kernel\fP
 .DE
 .LP
 After providing the kernel name, the machine will boot \*(4B with
@@ -755,7 +755,7 @@ Boot the supplied kernel:
 .DS
 .ft CW
 # halt
-ok boot sd(0,3)vmunix -s		[for old proms] OR
+ok boot sd(0,3)kernel -s		[for old proms] OR
 ok boot disk3 -s			[for new proms]
 \&... [\*(4B boot messages]
 .DE
@@ -773,7 +773,7 @@ to set up \*(4B to reboot automatically:
 .DS
 .ft CW
 # halt
-ok setenv boot-from sd(0,3)vmunix	[for old proms] OR
+ok setenv boot-from sd(0,3)kernel	[for old proms] OR
 ok setenv boot-device disk3		[for new proms]
 .DE
 If you build backwards-compatible filesystems, either with the SunOS
@@ -857,8 +857,8 @@ tar xf /dev/rmt0
 will extract the following four files:
 .DS
 A) root.image: \fIdd\fP image of the root filesystem
-B) vmunix.tape: \fIdd\fP image for creating boot tapes
-C) vmunix.net: file for booting over the network
+B) kernel.tape: \fIdd\fP image for creating boot tapes
+C) kernel.net: file for booting over the network
 D) root.dump: \fIdump\fP image of the root filesystem
 .DE
 There are three basic ways a system can be bootstrapped corresponding to the
@@ -886,8 +886,8 @@ following PROM commands. If you are booting on a 3100, the disk must be SCSI
 id zero because of a bug.
 .DS
 .ft CW
-DEC 3100:    boot \-f rz(0,0,0)vmunix
-DEC 5000:    boot 5/rz0/vmunix
+DEC 3100:    boot \-f rz(0,0,0)kernel
+DEC 5000:    boot 5/rz0/kernel
 .DE
 You can then proceed to section 2.5
 to create reasonable disk partitions for your machine
@@ -903,7 +903,7 @@ First, you will need to create a boot tape. This can be done using
 \fIdd\fP as in the following example.
 .DS
 .ft CW
-dd if=vmunix.tape of=/dev/nrmt0 bs=1b
+dd if=kernel.tape of=/dev/nrmt0 bs=1b
 dd if=root.dump of=/dev/nrmt0 bs=\*(Bzb
 .DE
 The actual special file syntax for the tape drive will vary depending on
@@ -925,15 +925,15 @@ Next you should proceed to section 2.4.3 to build a disk-based root filesystem.
 .PP
 You will need a host machine that is running the \fIbootp\fP server 
 with the
-.Pn vmunix.net
+.Pn kernel.net
 file installed in the default directory defined by the
 configuration file for
 .Xr bootp .
 Here are two example PROM commands to boot across the net:
 .DS
 .ft CW
-DEC 3100:	boot \-f tftp()vmunix.net m
-DEC 5000:	boot 6/tftp/vmunix.net m
+DEC 3100:	boot \-f tftp()kernel.net m
+DEC 5000:	boot 6/tftp/kernel.net m
 .DE
 This command should load the kernel and mini-root into memory and
 run the same as the tape install (procedure B).
@@ -1001,8 +1001,8 @@ When the restore finishes, clean up with:
 Reset the system and initialize the PROM monitor to boot automatically.
 .DS
 .ft CW
-DEC 3100:	setenv bootpath boot \-f rz(0,?,0)vmunix
-DEC 5000:	setenv bootpath 5/rz?/vmunix -a
+DEC 3100:	setenv bootpath boot \-f rz(0,?,0)kernel
+DEC 5000:	setenv bootpath 5/rz?/kernel -a
 .DE
 .IP 4)
 After booting UNIX, you will need to create
@@ -1370,7 +1370,7 @@ directory is a memory-based filesystem.
 Note that to interleave the paging between the two disks
 you must build a system configuration that specifies:
 .DS
-config	vmunix	root on \*(Dk0 swap on \*(Dk0 and \*(Dk1
+config	kernel	root on \*(Dk0 swap on \*(Dk0 and \*(Dk1
 .DE
 The
 .Pn /etc/fstab
diff --git a/share/doc/smm/01.setup/4.t b/share/doc/smm/01.setup/4.t
index fee3fc2..d26dac7 100644
--- a/share/doc/smm/01.setup/4.t
+++ b/share/doc/smm/01.setup/4.t
@@ -200,24 +200,24 @@ and look at the sample configuration files in the
 directory.
 .PP
 The configured system image
-.Pn vmunix
+.Pn kernel
 should be copied to the root, and then booted to try it out.
 It is best to name it
-.Pn /newvmunix
+.Pn /newkernel
 so as not to destroy the working system until you are sure it does work:
 .DS
-\fB#\fP \fIcp vmunix /newvmunix\fP
+\fB#\fP \fIcp kernel /newkernel\fP
 \fB#\fP \fIsync\fP
 .DE
 It is also a good idea to keep the previous system around under some other
 name.  In particular, we recommend that you save the generic distribution
 version of the system permanently as
-.Pn /genvmunix
+.Pn /genkernel
 for use in emergencies.
 To boot the new version of the system you should follow the
 bootstrap procedures outlined in section 6.1.
 After having booted and tested the new system, it should be installed as
-.Pn /vmunix
+.Pn /kernel
 before going into multiuser operation.
 A systematic scheme for numbering and saving old versions
 of the system may be useful.
diff --git a/share/doc/smm/01.setup/spell.ok b/share/doc/smm/01.setup/spell.ok
index c4f58a2..daedb66 100644
--- a/share/doc/smm/01.setup/spell.ok
+++ b/share/doc/smm/01.setup/spell.ok
@@ -294,7 +294,7 @@ ftpwelcome
 fts
 funopen
 gcc
-genvmunix
+genkernel
 getcap
 gettytab
 gid
@@ -411,7 +411,7 @@ netx25
 newdev
 newlfs
 news3400
-newvmunix
+newkernel
 nfs
 nfsd
 nfsiod
@@ -590,9 +590,9 @@ vax
 ventel
 vfs
 vm
-vmunix
-vmunix.net
-vmunix.tape
+kernel
+kernel.net
+kernel.tape
 vnode
 vnodes
 vol
diff --git a/share/doc/smm/06.nfs/1.t b/share/doc/smm/06.nfs/1.t
index 6804ed1..f68a863 100644
--- a/share/doc/smm/06.nfs/1.t
+++ b/share/doc/smm/06.nfs/1.t
@@ -512,7 +512,7 @@ planning (dreaming) stage.
 The NFS client does include kernel support for diskless/dataless operation
 where the root file system and optionally the swap area is remote NFS mounted.
 A diskless/dataless client is configured using a version of the
-``swapvmunix.c'' file as provided in the directory \fIcontrib/diskless.nfs\fR.
+``swapkernel.c'' file as provided in the directory \fIcontrib/diskless.nfs\fR.
 If the swap device == NODEV, it specifies an NFS mounted swap area and should
 be configured the same size as set up by diskless_setup when run on the server.
 This file must be put in the \fIsys/compile/<machine_name>\fR kernel build
@@ -529,7 +529,7 @@ flexibility when setting up different servers.
 .lp
 The tools are as follows:
 .ip \(bu
-diskless_offset.c - This little program reads a ``vmunix'' object file and
+diskless_offset.c - This little program reads a ``kernel'' object file and
 writes the file byte offset of the nfs_diskless structure in it to
 standard out. It was kept separate because it sometimes has to
 be compiled/linked in funny ways depending on the client architecture.
@@ -537,47 +537,47 @@ be compiled/linked in funny ways depending on the client architecture.
 .ip \(bu
 diskless_setup.c - This program is run on the server and sets up files for a
 given client. It mostly just fills in an nfs_diskless structure and
-writes it out to either the "vmunix" file or a separate file called
+writes it out to either the "kernel" file or a separate file called
 /var/diskless/setup.<official-hostname>
 .ip \(bu
 diskless_boot.c - There are two functions in here that may be used
-by a bootstrap server such as tftpd to permit sharing of the ``vmunix''
+by a bootstrap server such as tftpd to permit sharing of the ``kernel''
 object file for similar clients. This saves disk space on the bootstrap
 server and simplify organization, but are not critical for correct operation.
-They read the ``vmunix''
+They read the ``kernel''
 file, but optionally fill in the nfs_diskless structure from a
 separate "setup.<official-hostname>" file so that there is only
-one copy of "vmunix" for all similar (same arch etc.) clients.
+one copy of "kernel" for all similar (same arch etc.) clients.
 These functions use a text file called
 /var/diskless/boot.<official-hostname> to control the netboot.
 .lp
 The basic setup steps are:
 .ip \(bu
-make a "vmunix" for the client(s) with mountroot() == nfs_mountroot()
+make a "kernel" for the client(s) with mountroot() == nfs_mountroot()
 and swdevt[0].sw_dev == NODEV if it is to do nfs swapping as well
-(See the same swapvmunix.c file)
+(See the same swapkernel.c file)
 .ip \(bu
-run diskless_offset on the vmunix file to find out the byte offset
+run diskless_offset on the kernel file to find out the byte offset
 of the nfs_diskless structure
 .ip \(bu
 Run diskless_setup on the server to set up the server and fill in the
 nfs_diskless structure for that client.
 The nfs_diskless structure can either be written into the
-vmunix file (the -x option) or
+kernel file (the -x option) or
 saved in /var/diskless/setup.<official-hostname>.
 .ip \(bu
 Set up the bootstrap server. If the nfs_diskless structure was written into
-the ``vmunix'' file, any vanilla bootstrap protocol such as bootp/tftp can
+the ``kernel'' file, any vanilla bootstrap protocol such as bootp/tftp can
 be used. If the bootstrap server has been modified to use the functions in
 diskless_boot.c, then a
 file called /var/diskless/boot.<official-hostname>
 must be created.
 It is simply a two line text file, where the first line is the pathname
-of the correct ``vmunix'' file and the second line has the pathname of
+of the correct ``kernel'' file and the second line has the pathname of
 the nfs_diskless structure file and its byte offset in it.
 For example:
 .br
-	/var/diskless/vmunix.pmax
+	/var/diskless/kernel.pmax
 .br
 	/var/diskless/setup.rickers.cis.uoguelph.ca 642308
 .br
diff --git a/share/man/man7/hier.7 b/share/man/man7/hier.7
index 8d9ab10..e8e8614 100644
--- a/share/man/man7/hier.7
+++ b/share/man/man7/hier.7
@@ -368,7 +368,7 @@ commonly ~uucp; public uucp temporary directory
 .It Li tmp/ 
 temporary files that are kept between system reboots
 .El
-.It Li /vmunix
+.It Li /kernel
 pure kernel executable (the operating system loaded into memory
 at boot time).  
 .El
diff --git a/share/man/tools/newsp.errs b/share/man/tools/newsp.errs
index 2cde891..7eb1c76 100644
--- a/share/man/tools/newsp.errs
+++ b/share/man/tools/newsp.errs
@@ -1059,7 +1059,7 @@ vk
 vlp
 vlpmacs
 vmcore
-vmunix
+kernel
 vol
 vpd
 vpf
@@ -1570,7 +1570,7 @@ tzp
 uio.h
 usec
 vec
-vmunix
+kernel
 wait.h
 writefds
 writen
@@ -2526,7 +2526,7 @@ vidnorm
 vlimit.3c
 vlimit.h
 vm
-vmunix
+kernel
 vrbose
 vtimes.3c
 vtimes.h
@@ -3931,7 +3931,7 @@ vaxif
 vaxmba
 vaxuba
 versatec
-vmunix
+kernel
 vpacct
 vv.c
 wd
@@ -4564,8 +4564,8 @@ vipw
 vipw.8
 vmcore
 vmcore.n
-vmunix
-vmunix.n
+kernel
+kernel.n
 whod
 whoent
 xfc