Andy's enormous "Minix" -> "MINIX 3" crusade ;)

man/man1/M.1

@@ -27,7 +27,7 @@ M, U \- conveniently mount and unmount
 \fIM\fR and \fIU\fR allow easy mounting and unmounting of a device by using
 only an abbreviated device name or keyword.  Special keywords are
 \fBroot\fR, \fBtmp\fR, and \fBusr\fR for the three hard disk partitions
-Minix runs in.  Floppy devices are mounted on \fB/fd0\fR or \fB/fd1\fR.  You
+MINIX 3 runs in.  Floppy devices are mounted on \fB/fd0\fR or \fB/fd1\fR.  You
 can use \fB0\fR and \fB1\fR instead of \fBfd0\fR and \fBfd1\fP.  A device it
 doesn't know about is mounted on \fB/mnt\fR.
 .SH "SEE ALSO"

man/man1/cc.1

@@ -1,6 +1,6 @@
 .TH CC 1
 .SH NAME
-cc, pc, m2 \- Minix C, Pascal, and Modula-2 compilers
+cc, pc, m2 \- MINIX 3 C, Pascal, and Modula-2 compilers
 .SH SYNOPSIS
 .in +.5i
 .ti -.5i
@@ -101,7 +101,7 @@ cc, pc, m2 \- Minix C, Pascal, and Modula-2 compilers
 .BR pc ,
 and
 .BR m2
-are the call names of the Minix C, Pascal, and Modula-2 compilers from
+are the call names of the MINIX 3 C, Pascal, and Modula-2 compilers from
 the Amsterdam Compiler Kit (ACK).
 .PP
 All these call names are links to the
@@ -124,12 +124,12 @@ the synopsis above shows the options that the Minix-86 driver supports.  The
 rest of this manual page is geared towards the
 .B acd
 driver.  People writing software for Minix-86, or that should be
-portable to all Minix versions should stick to the options listed under
+portable to all MINIX 3 versions should stick to the options listed under
 the Minix-86 compiler.
 .SH OPTIONS
 The transformations done by the compiler are modified by the following
 options.  They are a superset of the options required by \s-2POSIX\s+2,
-with the Minix or compiler specific ones are marked as such.  Options
+with the MINIX 3 or compiler specific ones are marked as such.  Options
 for one specific compiler are ignored for others.  Read the OPTIONS section
 of
 .BR acd (1)
@@ -172,12 +172,12 @@ implicit
 .BR \-.c .
 The runtime startoff can be omitted by specifying
 .B \-.o
-for those rare cases where you want to supply your own startoff.  (Minix)
+for those rare cases where you want to supply your own startoff.  (MINIX 3)
 .TP
 .B \-c
 Transform the input files to object files and stop.  The
 .B \-o
-option may be used under Minix to set the name of the object file.
+option may be used under MINIX 3 to set the name of the object file.
 .BR Make (1)
 likes this, because
 .BI "cc \-c" " dir/file" .c
@@ -209,7 +209,7 @@ with the suffix
 .BR .i .
 File and line number information is omitted from the output.  Use
 .B \-P \-E
-under Minix to omit this info for
+under MINIX 3 to omit this info for
 .B \-E
 too.
 .TP
@@ -232,7 +232,7 @@ library.  (So you do not need to know how the archiver works.)  Note that you
 need to give object files as arguments if you want to replace old object
 files.  Transformed files are added under a (unique) temporary name.  With
 .B \-o
-you can name the library.  (Minix)  (Minix-86 can't do
+you can name the library.  (MINIX 3)  (Minix-86 can't do
 .BR \-c.a .)
 .TP
 .B \-O
@@ -244,13 +244,13 @@ optimization level to get code of reasonable quality.  Use
 to turn off optimization to speed up compilation at debug time.
 .TP
 .BI \-O level
-Compile with the given optimization level.  (Minix)
+Compile with the given optimization level.  (MINIX 3)
 .PP
 .B \-OS
 .br
 .B \-OT
 .RS
-Optimize for space or for time.  (Minix)
+Optimize for space or for time.  (MINIX 3)
 .RE
 .TP
 .B \-g
@@ -289,27 +289,27 @@ Strip the resulting executable of its symbol table.
 .RS
 Use software floating point instead of hardware floating point.  This is
 a loader flag, but in general it is best to specify this flag in all
-phases of the compilation.  (Minix)
+phases of the compilation.  (MINIX 3)
 .RE
 .TP
 .B \-fnone
 Ignored.  Used under Minix-vmd to omit floating point printing/scanning
-code.  The standard Minix compiler figures this out automatically using
+code.  The standard MINIX 3 compiler figures this out automatically using
-a special loader trick.  (Minix)
+a special loader trick.  (MINIX 3)
 .TP
 .B \-w
 Do not produce warnings about dubious C language constructs.  Normally
 the compiler is configured to do the maximum amount of checking
-without being too annoying.  (Minix)
+without being too annoying.  (MINIX 3)
 .TP
 .B \-wo
-Omit warnings about old (K&R) style.  (Minix)
+Omit warnings about old (K&R) style.  (MINIX 3)
 .TP
 .B \-ws
-Omit strict warnings.  (Minix)
+Omit strict warnings.  (MINIX 3)
 .TP
 .B \-wa
-Omit all warnings.  (Minix)
+Omit all warnings.  (MINIX 3)
 .TP
 .B \-3
 Only accept 3rd edition Modula-2.  (Modula-2)
@@ -337,7 +337,7 @@ Under Minix-86 this option transforms the function declarations (prototypes)
 to the old K&R form, i.e. the arguments declarations are removed.  This saves
 a lot of memory in the compiler and may allow a large program to be compiled.
 One must make sure that function arguments are properly type-cast where
-necessary.  (Minix)
+necessary.  (MINIX 3)
 .TP
 .BI \-m arch
 Set the target architecture for a cross compiler.  Normally the compiler
@@ -356,7 +356,7 @@ names are:
 .B m68020
 (Motorola MC68020, 32-bit ints),
 .B sparc
-(Sun SPARC).  (Minix)  (Ignored under Minix-86.)
+(Sun SPARC).  (MINIX 3)  (Ignored under Minix-86.)
 .TP
 .BI \-o " outfile"
 Set the output file for the
@@ -389,7 +389,7 @@ and
 itself.
 .RI ( Arch
 is the machine architecture name.  This is
-Minix dependent, compilers on other systems usually only look in
+MINIX 3 dependent, compilers on other systems usually only look in
 .IR directory .)
 (Minix-86 only has
 .B /lib
@@ -411,13 +411,13 @@ default.  Common I&D is probably only useful for the bootstraps.  The
 option has the same meaning as
 .BR \-sep ,
 but should no longer be used.
-(Minix)
+(MINIX 3)
 .RE
 .TP
 .B \-r
 Makes the loader produce a relocatable object file, i.e. a file that
 may be loaded again.  The runtime startoff and the default libraries are
-omitted, only the files mentioned are combined.  (Minix)
+omitted, only the files mentioned are combined.  (MINIX 3)
 .TP
 .BI \-stack " size"
 Allow the process
@@ -439,7 +439,7 @@ is used by default, translating to 64k for
 and 132k for other architectures.  Too large a size is rounded down to keep
 the data segment within 64 kilobytes for the
 .BR i86 .
-(Minix)
+(MINIX 3)
 .SH OPERANDS
 All leftover operands are treated as files to be compiled, with one
 exception.  The construct
@@ -455,8 +455,8 @@ mistake to write
 instead of
 .BR "cc\ x.c\ \-lcurses" .)
 .SH IMPLEMENTATION
-The Minix compiler implementation uses the ACK compilers adapted for use
+The MINIX 3 compiler implementation uses the ACK compilers adapted for use
-under Minix as described below.  Read
+under MINIX 3 as described below.  Read
 .BR ACK (7)
 for more detailed information on the ACK compilers themselves.
 .SS "Feature test macros"
@@ -464,7 +464,7 @@ The preprocessors are given these arguments to define feature test macros:
 .B \-D__ACK__
 tells what compiler is used.
 .B \-D__minix
-tells that this is Minix.
+tells that this is MINIX 3.
 .BI \-D__ arch
 tells the architecture.
 (More macros are defined, but they are only to be used in the include files.)
@@ -478,12 +478,12 @@ compiles a standard C program.  If you want the extensions described in
 POSIX.1 to become visible, then you have to set
 .BR _POSIX_SOURCE " to " 1
 at the start of your program.
-To enable \s-2UNIX\s+2 or Minix extensions you need to also set
+To enable \s-2UNIX\s+2 or MINIX 3 extensions you need to also set
 .BR _MINIX " to " 1 .
 If you don't want to clutter your source files with these symbols then you
 can use
 .B cc \-D_MINIX \-D_POSIX_SOURCE
-to get the POSIX.1 and the Minix extensions.
+to get the POSIX.1 and the MINIX 3 extensions.
 .SS "Preprocessing"
 Pascal, Modula-2, EM source (see below), and Assembly source are
 preprocessed by the C preprocessor if the very first character in the file

man/man1/chgrp.1

@@ -29,7 +29,7 @@ Alternatively, a decimal gid (uid) may be specified instead of a group name.
 If the \fB\-R\fR flag is used, the changes will be applied recursively to
 all files in named directories. Only the superuser may execute this command
 to set arbitrary groups. Normal users can only change the group if they own
-the file, and the group is their own group (Minix), or one of their
+the file, and the group is their own group (MINIX 3), or one of their
 supplementary groups (Minix-vmd).
 .SH "SEE ALSO"
 .BR chown (8),

man/man1/chmem.1

@@ -38,7 +38,7 @@ It is therefore important to set the amount of stack space carefully.
 If too little is provided, the program may crash.
 If too much is provided, memory will be wasted, and fewer programs will be able
 to fit in memory and run simultaneously.
-\s-2MINIX\s+2
+\s-1MINIX 3\s-1
 does not swap, so that when memory is full, subsequent attempts to fork will
 fail.
 The compiler sets the stack space

man/man1/compress.1

@@ -32,10 +32,10 @@ If \fIcompress\fR is linked to \fIuncompress\fR, the latter is the same
 as giving the \fB\-d\fP flag.
 Similarly, a link to \fIzcat\fR decompresses to \fIstdout\fR.
 The
-\s-2MINIX\s+2
+\s-1MINIX 3\s-1
 version of \fIcompress\fR uses 13-bit compression.
 This means that when compressing files on other systems for transmission to
-\s-2MINIX\s+2,
+\s-1MINIX 3\s-1,
 be sure that only 13-bit compression is used.
 On many systems, the default is 16-bit (too big).
 .SH "SEE ALSO"

man/man1/dd.1

@@ -49,7 +49,7 @@ The options are:
 .br
 	\fBconv = noerror\fR	\- Ignore errors and just keep going
 .br
-	\fBconv = silent\fR	\- Suppress statistics (Minix specific flag)
+	\fBconv = silent\fR	\- Suppress statistics (MINIX 3 specific flag)
 .PP
 Where sizes are expected, they are in bytes.
 However, the letters \fBw\fR, \fBb\fR, or \fBk\fR may be appended to the

man/man1/dosread.1

@@ -26,5 +26,5 @@ reads one \s-2MS-DOS\s+2 file and writes it on standard output.
 The file name must use slash, not backslash as a separator.
 ASCII files have the final CTRL-Z stripped, and carriage return plus
 line feed are mapped to line feed only, the usual
-\s-2MINIX\s+2
+\s-1MINIX 3\s-1
 convention.  See \fBdosdir\fR on the use of single letter drive codes.

man/man1/elvis.1

@@ -6,7 +6,7 @@ elvis, ex, vi \- The editor
 .SH DESCRIPTION
 \fBElvis\fP is a text editor which emulates \fBvi\fP/\fBex\fP.
 .PP
-On systems which pass the program name as an argument, such as Unix and Minix,
+On systems which pass the program name as an argument, such as UNIX and MINIX 3,
 you may also install \fBelvis\fP under the names "ex", "vi", "view", and "input".
 These extra names would normally be links to elvis;
 see the "ln" shell command.

man/man1/find.1

@@ -72,7 +72,7 @@ when a file is found:
 \-print0	print the file name terminated by a null character, to be
 used with
 .BR "xargs \-0" .
-(Minix extension).
+(MINIX 3 extension).
 .ti -\w'\-mtime nmm'u
 \-exec	execute a command, {} stands for the file name
 .ti -\w'\-mtime nmm'u

man/man1/isodir.1

@@ -17,7 +17,7 @@ Lists all info on files and directories (size, date, time)
 Recursively descend and print subdirectories
 .IP \-B
 List the byte offset and size of a file or directory.  (Useful in scripts that
-want to operate on an ISO image file.  To add a Minix partition table, for
+want to operate on an ISO image file.  To add a MINIX 3 partition table, for
 instance.)
 .SH "BUGS"
 Only Interchange level-1 is supported. The Red Rock extensions and Interchange

man/man1/isoread.1

@@ -15,7 +15,7 @@ program sees which function to perform by looking how it was called.
 the ^M at the end of each line.
 .IP \-B
 List the byte offset and size of a file.  (Useful in scripts that
-want to operate on an ISO image file.  To add a Minix partition table, for
+want to operate on an ISO image file.  To add a MINIX 3 partition table, for
 instance.)
 .SH "BUGS"
 Only Interchange level-1 is supported. The Red Rock extensions and Interchange 

man/man1/ls.1

@@ -30,7 +30,7 @@ and
 .PP
 Files whose names start with a dot are by default not listed.
 .PP
-Note that standard Minix doesn't have symbolic links or sockets and
+Note that standard MINIX 3 doesn't have symbolic links or sockets and
 .B \-u
 and
 .B \-c

man/man1/mail.1

@@ -36,13 +36,13 @@ mail \- send and receive electronic mail
 .PP
 \fIMail\fR is an extremely simple electronic mail program.  It can be used
 to send or receive email on a single 
-\s-2MINIX\s+2
+\s-1MINIX 3\s-1
 system, in which case it functions
 as user agent and local delivery agent.  
 If the flag \fIMAILER\fR is defined in \fImail.c\fR,
 it can also call a trans\%port agent to handle remote mail as well.
 No such agent is supplied with
-\s-2MINIX\s+2.
+\s-1MINIX 3\s-1.
 .PP
 When called by \fIuser\fR with no arguments, it examines the mailbox
 \fI/usr/spool/mail/user\fR, prints one message (depending on the \fB\-r\fR
@@ -81,7 +81,7 @@ will be delivered with Subject: No subject.
 .SH NOTES
 The \fB\-s\fR option was added to make this simple mail program
 consistent with mail programs found in other *nix variants.  Many
-programs, including the version of cron distributed with Minix releases
+programs, including the version of cron distributed with MINIX 3 releases
 2.0.3 and later, report their outcome by piping output to the mail
 program in order to send a mail message to root in lieu of writing a
 log file.  Such programs often expect the mail program to accept a
@@ -90,7 +90,7 @@ subject line using this option.
 If an external \fIMAILER\fR is used it is likely the conditional code 
 supporting this will need some editing to be made to work correctly.
 .SH AUTHOR
-The original mail program for Minix was written by Peter B. Housel.
+The original mail program for MINIX 3 was written by Peter B. Housel.
 The -e and -t options were added by C. W. Rose. The -s option was added
 by A. S. Woodhull. This man page revised by ASW 2003-07-18.
 

man/man1/make.1

@@ -70,7 +70,7 @@ Many books on
 discuss
 .I make .
 Study the numerous \fIMakefiles\fR in the 
-\s-2MINIX\s+2
+\s-1MINIX 3\s-1
 source tree for examples.
 .SH "SEE ALSO"
 .BR cc (1).

man/man1/man.1

@@ -64,7 +64,7 @@ Documents
 .br
 Larger manuals explaining some commands in more detail.
 .PP
-(If you are new to Minix then try
+(If you are new to MINIX 3 then try
 .BR "man hier" ,
 it will show you around the file system and give you many pointers to other
 manual pages.)

man/man1/mdb.1

@@ -1,6 +1,6 @@
 .TH MDB 1
 .SH NAME
-mdb \- Minix debugger
+mdb \- MINIX 3 debugger
 .SH SYNOPSIS
 .B mdb
 .RB [ \-fc ]
@@ -17,7 +17,7 @@ mdb \- Minix debugger
 .if n .sp
 ..
 .B mdb
-is the Minix debugger. 
+is the MINIX 3 debugger. 
 .SH OPTIONS
 Its command line options are:
 .TP

man/man1/mkfs.1

@@ -80,7 +80,7 @@ and 64 Mb for a version 1 file system.  Alas the 8086
 .I fsck
 runs out of memory on a V2 file system larger than 128 Mb, so for the 8086
 version of
-\s-2MINIX\s+2
+\s-1MINIX 3\s-1
 you have to limit yourself to file systems of that size.
 .SH "SEE ALSO"
 .BR mkproto (1),

man/man1/mkproto.1

@@ -1,6 +1,6 @@
 .TH MKPROTO 1
 .SH NAME
-mkproto \- create a MINIX prototype file
+mkproto \- create a MINIX 3 prototype file
 .SH SYNOPSIS
 \fBmkproto \fR[\fB\-b \fIn\fR] [\fB\-d \fIstr\fR] [\fB\-g \fIn\fR] [\fB\-i \fIn\fR] [\fB\-p \fInnn\fR] [\fB\-s\fR] [\fB\-t \fIroot\fR] [\fB\-u \fIn\fR] \fIsource_directory\fR [\fIprototype_file\fR]\fR
 .br

man/man1/postmort.1

@@ -1,6 +1,6 @@
 .TH POSTMORT 1
 .SH NAME
-postmort \- perform post-mortem on PC Minix core files
+postmort \- perform post-mortem on PC MINIX 3 core files
 .SH SYNOPSIS
 \fBpostmort\fR [\fB\-dpt\fR] \fB\-c \fIcorefile \fB\-s \fIsymbfile\fR
 .br
@@ -25,7 +25,7 @@ postmort \- perform post-mortem on PC Minix core files
 .SH DESCRIPTION
 .PP
 .I Postmort
-does a simple static analysis of a PC Minix core file;
+does a simple static analysis of a PC MINIX 3 core file;
 By default, it looks for the
 file 'core' in the local directory and loads that for analysis; it
 also searches for the file 'symbol.out', and if that fails 'a.out',

man/man1/readall.1

@@ -29,7 +29,7 @@ the disk, making it safer to use when one is worried about a sick system.
 When the \fB\-b\fR flag is given, the output is a shell script that
 calls the \fIbadblocks\fR program to marked all the bad blocks.
 Whenever installing 
-\s-2MINIX\s+2,
+\s-1MINIX 3\s-1,
 it is wise to run \fIreadall\fR with the \fB\-b\fR flag first on all
 the hard disks.
 .SH "SEE ALSO"

man/man1/readfs.1

@@ -1,6 +1,6 @@
 .TH READFS 1
 .SH NAME
-readfs \- read a MINIX file system
+readfs \- read a MINIX 3 file system
 .SH SYNOPSIS
 \fBreadfs\fR [\fB\-il\fR] \fIblock_special\fR [\fIdir\fR]\fR
 .br
@@ -22,7 +22,7 @@ readfs \- read a MINIX file system
 .SH DESCRIPTION
 .PP
 \fIReadfs\fR reads a diskette containing a 
-\s-2MINIX\s+2
+\s-1MINIX 3\s-1
 file system.  It can
 extract all the files from it, give a listing of them, or both.  The files
 extracted can be put in a user-specified directory (default: current

man/man1/rz.1

@@ -29,7 +29,7 @@ rz \- receive a file using the zmodem protocol
 .PP
 The XMODEM, YMODEM, and ZMODEM family of file transfer programs are widely
 used on personal computers.
-\s-2MINIX\s+2
+\s-1MINIX 3\s-1
 supports ZMODEM, the most advanced of the set.
 The programs \fIsz\fR and \fIrz\fR are used for sending and receiving,
 respectively.

man/man1/spell.1

@@ -19,7 +19,7 @@ spell \- print all words in a file not present in the dictionary
 .SH DESCRIPTION
 .PP
 \fISpell\fR is the 
-\s-2MINIX\s+2
+\s-1MINIX 3\s-1
 spelling checker.  
 It is actually a short shell script.
 First, the program \fIprep\fR strips off the \fIroff\fR, 

man/man1/stty.1

@@ -238,12 +238,12 @@ The
 .BR xpixels
 and
 .BR ypixels
-keywords are Minix additions beyond the keywords defined by POSIX.
+keywords are MINIX 3 additions beyond the keywords defined by POSIX.
 .B Rows
 and
 .B cols
 are common UNIX extensions, however.
-There are more Minix specific flags that match the Minix specific attributes
+There are more MINIX 3 specific flags that match the MINIX 3 specific attributes
 described in
 .BR tty (4).
 .SH AUTHOR

man/man1/sz.1

@@ -51,7 +51,7 @@ The file can be received using \fIrz\fR.
 \fISz\fR uses the ZMODEM error correcting
 protocol to send one or more files over a dial-in serial
 port to a variety of programs running under
-\s-2MINIX\s+2,
+\s-1MINIX 3\s-1,
 \s-2UNIX\s+2, 
 \s-2MS-DOS\s0, \s-2CP/M\s0, \s-2VMS\s0, and other operating systems.
 It is the successor to XMODEM and YMODEM.
@@ -228,7 +228,7 @@ conventions appropriate to the receiving environment.
 Send only the \fI.c\fR and \fI.h\fR files that exist on both systems,
 and are newer on the sending system than the corresponding
 version on the receiving system, converting 
-\s-2MINIX\s+2
+\s-1MINIX 3\s-1
 to \s-2MS-DOS\s0 text format.
 .SH "SEE ALSO"
 .BR rz (1),

man/man1/tar.1

@@ -38,7 +38,7 @@ is that the
 format is somewhat more standardized than the
 .I ar 
 format, making it theoretically possible to transport 
-\s-2MINIX\s+2
+\s-1MINIX 3\s-1
 files to another computer, but do not bet on it.
 If the target machine runs
 \&MS-DOS ,

man/man1/term.1

@@ -27,7 +27,7 @@ term \- turn PC into a dumb terminal [IBM]
 .SH DESCRIPTION
 .PP
 \fITerm\fR allows 
-\s-2MINIX\s+2
+\s-1MINIX 3\s-1
 to talk to a terminal or modem over RS232 
 port 1.  The program first sets the baudrate, parity and character length, 
 and then forks.

man/man1/uue.1

@@ -26,7 +26,7 @@ uue, uuencode \- encode a binary file to ASCII (e.g., for mailing)
 file to an encoding using only 64 ASCII characters.
 \fIUudecode\fR converts it back to the original file.
 The \fIuue\fR and \fIuud\fR programs are the 
-\s-2MINIX\s+2
+\s-1MINIX 3\s-1
 versions of these programs, and are compatible with the \s-2UNIX\s0 ones.
 The files produced can even be sent successfully over BITNET, which is 
 notorious for mangling files.

man/man1/which.1

@@ -19,7 +19,7 @@ which \- examine $PATH to see which file will be executed
 .SH DESCRIPTION
 .PP
 The $PATH shell variable controls the 
-\s-2MINIX\s+2
+\s-1MINIX 3\s-1
 search rules. 
 If a command \fIa.out\fR is given, the shell first tries to find an 
 executable file in the working directory.  

man/man1/xargs.1

@@ -137,7 +137,7 @@ produced by the
 .B \-print0
 option of
 .BR find (1).
-This is a Minix specific extension to
+This is a MINIX 3 specific extension to
 .BR xargs .
 .PP
 If no

man/man2/execve.2

@@ -185,7 +185,7 @@ is currently available.
 The number of bytes in the new process's argument list
 is larger than the system-imposed limit ARG_MAX.
 The limit in the system as released is 4096 bytes for
-16-bit Minix, 16384 bytes for 32-bit Minix, and unlimited for Minix-vmd.
+16-bit MINIX 3, 16384 bytes for 32-bit Minix, and unlimited for Minix-vmd.
 .TP 15
 [EFAULT]
 \fIPath\fP\|, \fIargv\fP\|, or \fIenvp\fP point

man/man2/getpriority.2

@@ -14,7 +14,7 @@ int setpriority(int \fIwhich\fP, int \fIwho\fP, int \fIprio\fP)
 returns the scheduling priority of the process, process group, or user
 referred to in \fIwho\fP. Which of the three is indicated in
 \fIwhich\fP, by PRIO_PROCESS, PRIO_PGRP and PRIO_USER, respectively.
-In Minix, currently only PRIO_PROCESS is implemented.
+In MINIX 3, currently only PRIO_PROCESS is implemented.
 
 The range of the returned value is between PRIO_MIN and PRIO_MAX,
 currently between -20 and 20, and is the so-called nice value of

man/man2/intro.2

@@ -77,8 +77,8 @@ or a disk pack is not loaded on a drive.
 .en 7 E2BIG "Arg list too long
 An argument list longer than ARG_MAX bytes is presented to
 .BR execve .
-ARG_MAX is set to 4096 bytes for 16-bit Minix, 16384 bytes for 32-bit
+ARG_MAX is set to 4096 bytes for 16-bit MINIX 3, 16384 bytes for 32-bit
-Minix, and unlimited for Minix-vmd as these systems are released.
+MINIX 3, and unlimited for Minix-vmd as these systems are released.
 .en 8 ENOEXEC "Exec format error
 A request is made to execute a file
 that, although it has the appropriate permissions,
@@ -163,7 +163,7 @@ and temporarily no more
 can be accepted.
 .en 24 EMFILE "Too many open files
 The limit on the number of open files per process, OPEN_MAX, is reached.
-As released, this limit is 20 for Minix, and 30 for Minix-vmd.
+As released, this limit is 20 for MINIX 3, and 30 for Minix-vmd.
 .en 25 ENOTTY "Not a typewriter
 The file mentioned in an
 .B ioctl
@@ -171,7 +171,7 @@ is not a terminal or one of the
 devices to which this call applies.  (Often seen error from programs with
 bugs in their error reporting code.)
 .en 26 ETXTBSY "Text file busy
-Attempt to execute a program that is open for writing.  Obsolete under Minix.
+Attempt to execute a program that is open for writing.  Obsolete under MINIX 3.
 .en 27 EFBIG "File too large
 The size of a file exceeded the maximum (little over 64 megabytes for
 the V2 file system).
@@ -303,7 +303,7 @@ One of these groups is distinguished from others and
 used in implementing accounting facilities.  The positive
 integer corresponding to this distinguished group is termed 
 the real group ID.
-(Under standard Minix this is the only group a process can be a member of.)
+(Under standard MINIX 3 this is the only group a process can be a member of.)
 .IP
 All processes have a real user ID and real group ID.
 These are initialized from the equivalent attributes
@@ -325,7 +325,7 @@ The group access list is an additional set of group ID's
 used only in determining resource accessibility.  Access checks
 are performed as described below in ``File Access Permissions''.
 The maximum number of additional group ID's is NGROUPS_MAX.
-For Minix this is 0, but Minix-vmd supports a list of up to 16
+For MINIX 3 this is 0, but Minix-vmd supports a list of up to 16
 additional group ID's.  (Also known as ``supplemental'' group ID's.)
 .TP 5
 Super-user

man/man2/pipe.2

@@ -31,7 +31,7 @@ A read using the descriptor
 .IR fildes [0]
 will pick up the data.
 .PP
-PIPE_MAX equals 7168 under Minix, but note that most systems use 4096.
+PIPE_MAX equals 7168 under MINIX 3, but note that most systems use 4096.
 .PP
 It is assumed that after the
 pipe has been set up,

man/man2/ptrace.2

@@ -20,7 +20,7 @@ int ptrace(int \fIrequest\fP, pid_t \fIpid\fP, long \fIaddr\fP, long \fIdata\fP)
 .fi
 .SH DESCRIPTION
 .ft B
-Note: This manual page has no relation to Minix.  Someone who knows ptrace()
+Note: This manual page has no relation to MINIX 3.  Someone who knows ptrace()
 has to check, or rewrite, this page.  (kjb)
 .ft R
 .PP

man/man2/reboot.2

@@ -56,7 +56,7 @@ the return value is -1 and an error is indicated by
 .BR halt (8),
 .BR sync (2).
 .SH NOTES
-Minix can not return to the monitor if running in real mode.  This means
+MINIX 3 can not return to the monitor if running in real mode.  This means
 that most of the reboot functions will change to a system reset.
 .SH AUTHOR
 Edvard Tuinder (v892231@si.hhs.NL)

man/man2/sigaction.2

@@ -113,7 +113,7 @@ Note that
 .B signal()
 and all of the
 .B SA_*
-flags are Minix extensions.
+flags are MINIX 3 extensions.
 .PP
 Signal handlers are reset to
 .B SIG_DFL
@@ -121,7 +121,7 @@ on an
 .BR execve (2).
 Signals that are ignored stay ignored.
 .SS Signals
-Minix knows about the following signals:
+MINIX 3 knows about the following signals:
 .PP
 .nf
 .ta +11n +7n +8n
@@ -167,7 +167,7 @@ The signal is ignored if not caught.
 Only Minix-vmd implements this signal.
 .TP
 .B x
-Minix extension, not defined by \s-2POSIX\s+2.
+MINIX 3 extension, not defined by \s-2POSIX\s+2.
 .TP
 .B p
 These signals are not implemented, but \s-2POSIX\s+2 requires that they are

man/man2/svrctl.2

@@ -15,7 +15,7 @@ int svrctl(u32_t \fIrequest\fP, void *\fIdata\fP);
 .SH DESCRIPTION
 .B Svrctl
 allows root to control the kernel in various ways, or implements some very
-Minix specific system calls that don't deserve their own system call number.
+MINIX 3 specific system calls that don't deserve their own system call number.
 .PP
 This system call makes it easy to add new ways of setting and getting kernel
 parameters, but at the same time, backwards compatibility is not guaranteed.

man/man2/uname.2

@@ -28,7 +28,7 @@ struct utsname {
 .PP
 The strings are always null terminated, and may be of a different length then
 shown here.  The first five are required by \s-2POSIX\s+2, the last is
-Minix specific.
+MINIX 3 specific.
 .SH "SEE ALSO"
 .BR uname (1).
 .SH AUTHOR

man/man2/wait.2

@@ -65,7 +65,7 @@ there are no processes that wish to report status (WNOHANG),
 and/or that children of the current process that are stopped
 due to a SIGTTIN, SIGTTOU, SIGTSTP, or SIGSTOP signal should also have
 their status reported (WUNTRACED).  (Job control is not implemented for
-Minix, but these symbols and signals are.)
+MINIX 3, but these symbols and signals are.)
 .PP
 When the WNOHANG option is specified and no processes
 wish to report status, 
@@ -75,7 +75,7 @@ either returns 0 under some implementations, or \-1 with
 set to
 .B EAGAIN
 under others.
-(Under Minix it returns 0.)
+(Under MINIX 3 it returns 0.)
 The WNOHANG and WUNTRACED options may be combined by 
 .IR or 'ing
 the two values.
@@ -120,7 +120,7 @@ Signal number if the process died by a signal, zero otherwise.
 True if the process died by a signal.
 .TP 5
 .BI "WIFSTOPPED(" status ")"
-True if the process is stopped.  (Never true under Minix.)
+True if the process is stopped.  (Never true under MINIX 3.)
 .TP 5
 .BI "WSTOPSIG(" status ")"
 Signal number of the signal that stopped the process.
@@ -153,7 +153,7 @@ The \fIstatus\fP argument points to an illegal address.
 [EAGAIN]
 .B Waitpid
 is called with the WNOHANG option and no child has exited yet.  (Not under
-Minix, it'll return 0 in this case and leave
+MINIX 3, it'll return 0 in this case and leave
 .B errno
 alone.)
 .SH "SEE ALSO"

man/man3/directory.3

@@ -38,7 +38,7 @@ allows the directory to be read again from the beginning.
 .B Closedir()
 closes the directory and releases administrative data.
 .PP
-The Minix specific functions
+The MINIX 3 specific functions
 .B telldir()
 and
 .B seekdir()

man/man3/execl.3

@@ -160,7 +160,7 @@ but duplicate the shell's actions in searching for an executable
 file in a list of directories.
 The directory list is obtained from the environment variable
 .BR PATH .
-Under standard Minix, if a file is found that is executable, but does
+Under standard MINIX 3, if a file is found that is executable, but does
 not have the proper executable header then it is assumed to be
 a shell script.
 .B Execlp

man/man3/getgrent.3

@@ -117,7 +117,7 @@ visible.  The
 field is also not defined by \s-2POSIX\s+2, but is always visible.
 Portable code cannot reliably detect errors by setting
 .B errno
-to zero.  Under Minix it is better to make a
+to zero.  Under MINIX 3 it is better to make a
 .B getgrent()
 scan if you need to look up several group-id's or names, but portable code
 had better use several

man/man3/getpwent.3

@@ -122,7 +122,7 @@ and
 fields are also not defined by \s-2POSIX\s+2, but are always visible.
 Portable code cannot reliably detect errors by setting
 .B errno
-to zero.  Under Minix it is better to make a
+to zero.  Under MINIX 3 it is better to make a
 .B getpwent()
 scan if you need to look up several user-id's or names, but portable code
 had better use several

man/man3/getttyent.3

@@ -89,7 +89,7 @@ and
 .B getttynam()
 return a pointer to static storage that is overwritten in each call.
 .PP
-The Minix
+The MINIX 3
 .B struct ttyent
 has only the
 .B ty_name

man/man3/int64.3

@@ -35,7 +35,7 @@ u64_t make64(unsigned long \fIlo\fP, unsigned long \fIhi\fP)
 ..
 The
 .B int64
-family of functions allow Minix to handle disks of up to 4 terabytes using
+family of functions allow MINIX 3 to handle disks of up to 4 terabytes using
 32 bit sector numbers and 64 bit byte offsets on a machine where the C type
 .B long
 is 32 bits.  The <minix/u64.h> include file defines a 64 bit data
@@ -174,11 +174,11 @@ kernel.  They should not be used for anything else.)
 With the usual disk block size of 512 bytes the maximum disk size is 512
 \(** 4 gigabytes = 2 terabytes.
 .PP
-Standard Minix only uses 64 bit computations within the disk drivers, so
+Standard MINIX 3 only uses 64 bit computations within the disk drivers, so
 individual partitions are still limited to 4 gigabytes.  Minix-vmd has 64
 bit computations also in the file system code.
 .PP
-Special care must be taken when accessing disk devices.  For Minix one may
+Special care must be taken when accessing disk devices.  For MINIX 3 one may
 have to temporarily change the start of the partition to go beyond 4 G.
 Minix-vmd can go beyond 4 G, but the
 .B lseek

man/man3/servxcheck.3

@@ -114,7 +114,7 @@ Jan 10 20:27:20 flotsam inetd[174]: service 'shell' granted to jetsam.cs.vu.nl
 .RE
 .SH BUGS
 IP and DNS based access checks will stop most crackers, but not the really
-determined ones.  Luckily Minix is sufficiently strange to thwart the well
+determined ones.  Luckily MINIX 3 is sufficiently strange to thwart the well
 known cracking schemes.  But don't ever allow yourself to feel secure.
 .SH AUTHOR
 Kees J. Bot <kjb@cs.vu.nl>

man/man3/termcap.3

@@ -162,6 +162,6 @@ if a null (\fB^@\fR) is inappropriate.
 .SH AUTHOR
 William Joy
 .SH NOTES
-The Minix implementation does not support any of the external variables,
+The MINIX 3 implementation does not support any of the external variables,
 only the functions calls.  The Minix-vmd termcap does support it all,
 although noone in his right mind meddles with those variables.

man/man3/termios.3

@@ -82,7 +82,7 @@ Encode the new output baud rate into the termios structure.
 .B tcsendbreak(\fIfd\fP, \fIduration\fP)
 Emit a break condition on a serial line for a time indicated by
 .IR duration .
-(Always 0.4 seconds under Minix,
+(Always 0.4 seconds under MINIX 3,
 .I duration
 is ignored.)
 .TP
@@ -130,7 +130,7 @@ does not refer to a terminal device, and
 if one of the functions waiting for output to drain is interrupted.
 .SH NOTES
 It may be interesting to know that the functions operating on the tty are
-directly translated into the following Minix
+directly translated into the following MINIX 3
 .B ioctl
 requests:
 .BR TCGETS ,

man/man3/ttyslot.3

@@ -51,6 +51,6 @@ utmp file is not used.
 .B Ttyslot()
 is often found in a UNIX implementation,
 .B fttyslot()
-is Minix specific.
+is MINIX 3 specific.
 .SH AUTHOR
 Kees J. Bot (kjb@cs.vu.nl)

man/man4/console.4

@@ -35,7 +35,7 @@ Adapter	Usable memory	Mono/Colour
 .RE
 .PP
 MDA and Hercules are the same to the console driver, because the graphics
-mode of the Hercules is of no use to Minix.  EGA and VGA are also mostly
+mode of the Hercules is of no use to MINIX 3.  EGA and VGA are also mostly
 seen as the same in text mode.  An EGA adapter is either a monochrome or a
 colour device depending on the screen attached to it.  A VGA adapter can run
 in either monochrome or colour (grayscale) mode depending on how the Boot
@@ -189,7 +189,7 @@ Font memory consists of 256 character definitions of 32 lines per character
 and 8 pixels per line.  The first line is the topmost line of the character.
 The leftmost pixel is lit if the most significant bit of a line is set, etc.
 How many lines are used depends on the current video mode.  The 80x25 video
-mode used by Minix has an 8x16 character cell, 80x28 has 8x14 characters,
+mode used by MINIX 3 has an 8x16 character cell, 80x28 has 8x14 characters,
 and 132x43 or 132x50 has 8x8 characters.  The boot variable
 .B console
 is used by both the Boot Monitor and the console driver to set the video

man/man4/controller.4

@@ -9,7 +9,7 @@ controller, disk, tape, at, bios, esdi, aha1540, ncr810, dosfile, fatfile \- con
 The
 .BI c n *
 family of devices refer to drivers that control disks, disk like devices,
-and tapes.  Minix contains a number of drivers for several different
+and tapes.  MINIX 3 contains a number of drivers for several different
 controllers.  These controllers can have disks, cdroms and tapes attached to
 them.  Boot Monitor variables specify which drivers are activated using
 the variables
@@ -69,7 +69,7 @@ minor	device	what?	obsolete
 .PP
 The device names in
 .B /dev
-also name the controller, of course, so the usual place for the Minix
+also name the controller, of course, so the usual place for the MINIX 3
 root device, the first subpartition of the second partition of disk 0 on
 controller 0 is
 .BR /dev/c0d0p1s0 .
@@ -78,12 +78,12 @@ Note that everything is numbered from 0!  The first controller is controller
 .BR p1 .
 .PP
 The fourth column in the table above shows the disk devices names that were
-used by previous versions of Minix for what is now controller 0.  These
+used by previous versions of MINIX 3 for what is now controller 0.  These
 devices are no longer present in
 .BR /dev .
 .SS Disks
 Most disks are arrays of 512 byte sectors.  The disk devices are normally
-block devices, which means they are block buffered by the Minix file system
+block devices, which means they are block buffered by the MINIX 3 file system
 cache using 1024 byte blocks.  The FS cache allows I/O at any byte offset,
 and takes care of cutting and pasting incomplete blocks together.  If one
 creates a character device for a disk device, then I/O must be in multiples
@@ -101,8 +101,8 @@ partitions may be defined, named
 to
 .BR c0d0p3
 for disk 0 on controller 0.  To make things interesting you can also place a
-partition table in the first sector of a Minix partition, which divides the
+partition table in the first sector of a MINIX 3 partition, which divides the
-partition into up to four subpartitions.  Normally Minix is installed into a
+partition into up to four subpartitions.  Normally MINIX 3 is installed into a
 single partition, with the root, swap and /usr file systems in subpartitions.
 .PP
 If a partition is an extended partition then it contains a linked list of
@@ -139,7 +139,7 @@ struct part_entry {
 
 /* Partition types (sysind). */
 #define NO_PART	0x00	/* unused entry */
-#define MINIX_PART	0x81	/* Minix partition type */
+#define MINIX_PART	0x81	/* MINIX 3 partition type */
 .fi
 .PP
 The cylinder numbers are encoded in a very strange way, bits 8 and 9 are
@@ -288,7 +288,7 @@ By setting the Boot variables
 .BR c0
 to
 .BR c3
-under Minix, or
+under MINIX 3, or
 .BR c0
 to
 .BR c4
@@ -312,7 +312,7 @@ DMA_SECTORS (see
 it works well enough.
 .SS esdi
 A hard disk driver for use on some PS/2 models.
-.SS "xt \fR(Minix only)"
+.SS "xt \fR(MINIX 3 only)"
 A hard disk driver for IBM/XT type hard disks.  Useful for old 286 based
 machines that have such a disk.  On XTs you are better off with the
 .B bios
@@ -326,10 +326,10 @@ This will eventually become a Symbios 810 SCSI driver.  (Formerly owned by
 NCR.)  KJB has read the docs on this card three times, but has still done
 nothing, the lazy bum.
 .SS dosfile
-The "DOS file as disk" driver that is used when Minix is running
+The "DOS file as disk" driver that is used when MINIX 3 is running
-under DOS.  It treats a large DOS file as a Minix disk.  Only primary
+under DOS.  It treats a large DOS file as a MINIX 3 disk.  Only primary
 partitions are supported, there are no subpartitions.  This is the default
-driver when Minix is started under DOS.
+driver when MINIX 3 is started under DOS.
 .SS fatfile
 Uses a large file on a FAT file system as a disk.  It needs one of the other
 disk drivers to do the actual I/O.  This driver only knows how to interpret

man/man4/dev.4

@@ -45,9 +45,9 @@ those devices.  Data read or written by processes is passed through the file
 system block cache.  Unaligned bytes read or written are extracted or
 reassembled by the file server from or to whole blocks in the cache.  The
 file server transfers data to or from the device driver as blocks to
-positions at block size boundaries.  These blocks are Minix blocks of 1024
+positions at block size boundaries.  These blocks are MINIX 3 blocks of 1024
 bytes, disk devices usually have a 512 byte block size.  Only block devices
-can be mounted as part of the file system tree if they contain a Minix file
+can be mounted as part of the file system tree if they contain a MINIX 3 file
 system.
 .PP
 The major device number (2 for
@@ -61,7 +61,7 @@ and 0 for
 .BR console )
 is passed to the driver to select a device among a number of related devices
 that are all managed by that driver.  The device drivers are usually kernel
-tasks under Minix, small processes that are contained within the address
+tasks under MINIX 3, small processes that are contained within the address
 space of the kernel.  The following tasks and associated devices exist:
 .SS "Memory (major 1)"
 The
@@ -122,9 +122,9 @@ Each of these devices accesses a range of sectors on the
 device.  It is customary to give each operating system on a disk a primary
 partition.  So the Windows C: "drive" can be on
 .BR c0d0p0 ,
-and Minix can be on
+and MINIX 3 can be on
 .BR c0d0p1 .
-Minix wants to have several partitions on its own, so
+MINIX 3 wants to have several partitions on its own, so
 .B c0d0p1
 can be further subdivided into the subpartitions
 .BR c0d0p1s0 ,
@@ -202,7 +202,7 @@ device is used to control the audio driver.
 .SH FILES
 .TP 10
 .B /dev/*
-All Minix devices
+All MINIX 3 devices
 .SH "SEE ALSO"
 .BR read (2),
 .BR write (2),
@@ -241,7 +241,7 @@ Some devices are not present by default.  The
 .BR MAKEDEV
 script knows how to make them.
 .SS "MS-DOS/Windows equivalents"
-The names of MS-DOS/Windows devices probably map to Minix devices as follows:
+The names of MS-DOS/Windows devices probably map to MINIX 3 devices as follows:
 .PP
 .RS
 .nf

man/man4/fd.4

@@ -5,9 +5,9 @@ fd \- floppy disk
 The
 .B fd*
 devices refer to the Floppy disk driver using the NEC PD765 floppy disk
-controller.  These diskettes are arrays of 512 byte sectors, although Minix
+controller.  These diskettes are arrays of 512 byte sectors, although MINIX 3
 always works with two sectors at a time due to its 1024 byte block size.  You
-can read or write any number of bytes however, Minix takes care of cutting
+can read or write any number of bytes however, MINIX 3 takes care of cutting
 and pasting incomplete blocks together.
 .PP
 The driver is normally configured for two floppy disk devices

man/man4/ip.4

@@ -11,7 +11,7 @@
 		  Greg Sharp, April 1992
 		  - updated keywords for auto index generation
 	Modified: Kees J. Bot, June 1994
-		  - changed to man(7) format for Minix.
+		  - changed to man(7) format for MINIX 3.
 ..
 .TH IP 4
 .SH NAME
@@ -28,7 +28,7 @@ The
 .BR tcp* ,
 and
 .B udp*
-devices give access to the Internet Protocol (IP) services in Minix.
+devices give access to the Internet Protocol (IP) services in MINIX 3.
 There can be up to 16 different networks, with 4 network devices each
 (a network has either an
 .B eth*
@@ -1268,7 +1268,7 @@ When
 .B NWUO_DI_IPOPT
 is set IP option will be stripped from received packets and no IP options will
 be sent.
-.ig \" Minix doesn't have this stuff (yet? ever?)
+.ig \" MINIX 3 doesn't have this stuff (yet? ever?)
 .SS "UDP Library Functions"
 .PP
 The following routines provide an somewhat easier to use interface to UDP than

man/man4/tty.4

@@ -71,7 +71,7 @@ set to
 .BR EAGAIN .
 .SS "Special characters"
 Some characters have special functions in some of the terminal modes.  These
-characters are as follows, with the Minix defaults shown in parentheses:
+characters are as follows, with the MINIX 3 defaults shown in parentheses:
 .TP 5
 .BR INTR " (^?)"
 Special input character that is recognized if
@@ -140,7 +140,7 @@ are set.  A
 .B CR NL
 sequence is output instead of just
 .BR NL .
-(Minix specific, but almost mandatory on any UNIX-like system.)
+(MINIX 3 specific, but almost mandatory on any UNIX-like system.)
 .TP
 .BR TAB " (^I)"
 Special character on output if
@@ -161,7 +161,7 @@ Special input character if job control is implemented and
 .B ISIG
 is set.  It causes a
 .B SIGTSTP
-signal to be send to the terminal process group.  (Minix does not have job
+signal to be send to the terminal process group.  (MINIX 3 does not have job
 control.)
 .TP
 .BR STOP " (^S)"
@@ -205,7 +205,7 @@ All of these characters except
 .B NL
 and
 .B TAB
-may be changed or disabled under Minix.  (Changes to
+may be changed or disabled under MINIX 3.  (Changes to
 .B START
 and
 .B STOP
@@ -213,13 +213,13 @@ may be ignored under other termios implementations.)  The
 .B REPRINT
 and
 .B LNEXT
-characters are Minix extensions that are commonly present in other
+characters are MINIX 3 extensions that are commonly present in other
 implementations.  \s-2POSIX\s+2 is unclear on whether
 .BR IEXTEN,
 .BR IGNCR
 and
 .BR ICRNL
-should be active in non-canonical mode, but under Minix they are.
+should be active in non-canonical mode, but under MINIX 3 they are.
 .SS "Terminal attributes"
 The attributes of a terminal, such as whether the mode should be canonical or
 non-canonical, are controlled by routines that use the
@@ -284,7 +284,7 @@ Enable start/stop output control.
 Enable start/stop input control.  (Not implemented.)
 .TP
 .B IXANY
-Allow any character to restart output.  (Minix specific.)
+Allow any character to restart output.  (MINIX 3 specific.)
 .TP
 .B ISTRIP
 Strip characters to seven bits.
@@ -322,7 +322,7 @@ field contains the following single bit flags that control output processing:
 .TP
 .B OPOST
 Perform output processing.  This flag is the "main switch" on output
-processing.  All other flags are Minix specific.
+processing.  All other flags are MINIX 3 specific.
 .TP
 .B ONLCR
 Transform an
@@ -473,7 +473,7 @@ a signal is sent.
 Send a
 .B SIGTTOU
 signal if job control is implemented and a background process tries to
-write.  (Minix has no job control.)
+write.  (MINIX 3 has no job control.)
 .SS "Input and output speed"
 The input and output speed are encoded into the
 .B c_ispeed
@@ -523,7 +523,7 @@ fields and the
 .B B57600
 and
 .B B115200
-symbols are Minix specific.)
+symbols are MINIX 3 specific.)
 .SS "Special characters"
 The
 .B c_cc
@@ -560,7 +560,7 @@ subscripts respectively, and may ignore changes to
 .B START
 and
 .BR STOP .
-(Under Minix all special characters have their own
+(Under MINIX 3 all special characters have their own
 .I c_cc
 slot and can all be modified.)
 .SS "Raw I/O Parameters"
@@ -632,7 +632,7 @@ reach the terminal even when standard input, output and error are
 redirected.  Opening this device can also be used as a test to see if a
 process has a controlling tty or not.
 .PP
-For Minix a special write-only device
+For MINIX 3 a special write-only device
 .B /dev/log
 exists for processes that want to write messages to the system console.
 Unlike the console this device is still accessible when a session leader
@@ -701,10 +701,10 @@ terminal interface are still supported by the terminal driver by emulation.
 Note that these old functions cannot control all termios attributes, so the
 terminal must be in a relatively sane state to avoid problems.
 .SH FILES
-The list below shows all devices that Minix and Minix-vmd have.  Not all of
+The list below shows all devices that MINIX 3 and Minix-vmd have.  Not all of
 these devices are configured in by default, as indicated by the numbers
 (i/j/k, l/m/n) that tell the minimum, default and maximum possible number of
-these devices for Minix (i/j/k) and Minix-vmd (l/m/n).
+these devices for MINIX 3 (i/j/k) and Minix-vmd (l/m/n).
 .TP 20
 .B /dev/console
 System console.
@@ -730,7 +730,7 @@ Associated pseudo tty controllers.
 .BR read (2),
 .BR write (2).
 .SH BUGS
-A fair number of flags are not implemented under Minix (yet).  Luckily they
+A fair number of flags are not implemented under MINIX 3 (yet).  Luckily they
 are very limited utility and only apply to RS-232, not to the user interface.
 .SH AUTHOR
 Kees J. Bot (kjb@cs.vu.nl)

man/man5/crontab.5

@@ -91,7 +91,7 @@ oneliner.  The time fields must all be on the same line.
 .SH FILES
 .TP 25n
 .B /usr/lib/crontab
-Main Minix crontab file.
+Main MINIX 3 crontab file.
 .TP
 .B /usr/local/lib/crontab
 Local jobs for all systems in an organization.

man/man5/dhcp.conf.5

@@ -90,7 +90,7 @@ own networks, it ignored on entries for other hosts.
 .PP
 .RS
 Includes the macro or parameters if one of the class names is matched.  A
-host normally includes a class ID in its request.  Minix and Minix-vmd
+host normally includes a class ID in its request.  MINIX 3 and Minix-vmd
 use "Minix" as the class name.  For Windows the class ID starts with
 "MSFT", and Solaris' starts with "SUNW".
 (Use
@@ -243,7 +243,7 @@ The
 field tells the maximum number of items that may be used with the tag, with
 0 meaning "unlimited".
 .SP
-Three tags, the ones that Minix really cares about, have been predefined,
+Three tags, the ones that MINIX 3 really cares about, have been predefined,
 and there are also a few pseudotags predefined for the static fields in a
 DHCP packet that one may want to set:
 .SP
@@ -400,13 +400,13 @@ two external servers at the VU that know the world.
 host darask {
 	option server;
 	DNSserver saone;
-	class Minix { DNSserver saone 130.37.24.3 130.37.24.6; };
+	class MINIX 3 { DNSserver saone 130.37.24.3 130.37.24.6; };
 };
 .xE
 .cS
 The darask is also a server, the backup for saone on the odd chance that it
 is unavailable.  It uses saone and the external name servers, but only
-when it is running Minix.  When running Windows it only uses saone.
+when it is running MINIX 3.  When running Windows it only uses saone.
 .cE
 .xS
 .ta +32m +16m
@@ -473,7 +473,7 @@ tag numbers and their meaning are standard, the names are made up.)
 .SH NOTES
 The amount of memory
 .B dhcpd
-needs increases with the size of configuration file.  Minix can
+needs increases with the size of configuration file.  MINIX 3 can
 handle
 .B dhcptags.conf
 and a modest sized
@@ -485,12 +485,12 @@ Items that are only necessary for a certain host should only be specified
 for that host.  Items for a whole network are best added to a netblock
 specification.  Use class elements for a certain type of host, and macros
 for exceptions.  Try to limit information as much as possibly to those hosts
-that need it.  (Don't go overboard.  A Minix machine won't be bothered by a
+that need it.  (Don't go overboard.  A MINIX 3 machine won't be bothered by a
 few NetBIOS tags.)
 .PP
 DHCPINFORM requests should always be answered when being a server, but
 J. Random Sysadmin trying to diagnose problems doesn't like it when little
-Minix machines show up in a packet trace unexpectedly.  It's best to be
+MINIX 3 machines show up in a packet trace unexpectedly.  It's best to be
 inconspicuous on a network you don't own.
 .SH BUGS
 There are a few too many subtle mistakes one can make.

man/man5/dir.5

@@ -35,7 +35,7 @@ in length.  Any character other than null or '\fB/\fP' is allowed.
 .PP
 See
 .BR directory (3)
-for a portable way to access directories, Minix is probably the last system
+for a portable way to access directories, MINIX 3 is probably the last system
 with these old V7 format directories.
 .SH "SEE ALSO"
 .BR directory (3).

man/man5/fstab.5

@@ -18,7 +18,7 @@ and
 is not read by
 .B mount
 as it should be.  It is instead a simple shell script listing the two or
-three devices that Minix needs to operate:  The device names of the root
+three devices that MINIX 3 needs to operate:  The device names of the root
 file system, the swap file system (optional), and the file system for
 .BR /usr .
 .PP

man/man5/passwd.5

@@ -55,7 +55,7 @@ Lastly the
 .I shell
 field is the path name of the users login shell, it may be empty to indicate
 .BR /bin/sh .
-A Minix specific extension allows the shell field to contain extra space
+A MINIX 3 specific extension allows the shell field to contain extra space
 separated arguments for the shell.
 .PP
 Lines in the group file consist of four fields:
@@ -137,7 +137,7 @@ id is used in those cases that a program may not have any privileges at all.
 The
 .B ast
 id is the honorary home directory for Andrew S. Tanenbaum, the creator of
-Minix.  You can also find the initial contents for a new home directory
+MINIX 3.  You can also find the initial contents for a new home directory
 there.
 .PP
 The special group file entries are:

man/man5/rhosts.5

@@ -35,7 +35,7 @@ from
 .I host
 to login.
 .PP
-Under Minix
+Under MINIX 3
 .I host
 may be a pattern using
 .B "*"
@@ -48,7 +48,7 @@ may also be an IP address, or a network specification in CIDR form, e.g.
 .BR rlogin (1),
 .BR rsh (1).
 .SH NOTES
-Minix has no restrictions on becoming super-user remotely.  Other systems
+MINIX 3 has no restrictions on becoming super-user remotely.  Other systems
 usually require one to log in as a user and then use
 .BR su
 to become root.

man/man5/serv.access.5

@@ -160,7 +160,7 @@ it always requires a password, and your only way in if things are seriously
 hosed.
 .SH BUGS
 IP and DNS based access checks will stop most crackers, but not the really
-determined ones.  Luckily Minix is sufficiently strange to thwart the well
+determined ones.  Luckily MINIX 3 is sufficiently strange to thwart the well
 known cracking schemes.  But don't ever allow yourself to feel secure.
 .SH AUTHOR
 Kees J. Bot <kjb@cs.vu.nl>

man/man5/termcap.5

@@ -1860,6 +1860,6 @@ in this file is used only if the kernel does not have any information.
 .PP
 Not all programs support all entries.
 .PP
-The Minix
+The MINIX 3
 .BR termcap (3)
 does not understand everything described here, unlike the one Minix-vmd uses.

man/man7/ACK.7

@@ -24,15 +24,15 @@ ACK \- Additional information on the Amsterdam Compiler Kit compilers
 \s-2UNIX\s+2
 ..
 .de MX
-.if n Minix
+.if n MINIX 3
-.if t \s-2MINIX\s+2
+.if t \s-1MINIX 3\s-1
 ..
-.if n .ds Mx Minix
+.if n .ds Mx MINIX 3
-.if t .ds Mx \s-2MINIX\s+2
+.if t .ds Mx \s-1MINIX 3\s-1
 .if n .ds Mp Minix-PC
 .if t .ds Mx \s-2MINIX-PC\s+2
 .if n .ds Mv Minix-vmd
-.if t .ds Mv \s-2MINIX\s+2-vmd
+.if t .ds Mv \s-1MINIX 3\s-1-vmd
 .if n .ds Cw \fR
 .if t .ds Cw \fC
 .de CW
@@ -145,7 +145,7 @@ different type, the resulting value will usually be garbage.  The
 compiler makes no effort to catch these errors.
 .IP \(bu
 The alignment of types under 16-bit \*(Mp is 1 byte for characters and 2
-bytes for all other types.  Under other Minix versions 'int' and smaller
+bytes for all other types.  Under other MINIX 3 versions 'int' and smaller
 types are aligned to a multiple of their size, bigger scalar types are
 aligned like 'int'.  Arrays have the same alignment as their elements;
 structs and unions are aligned like their field with the worst alignment.

man/man7/hier.7

@@ -6,7 +6,7 @@ hier \- file system hierarchy
 .if t .sp 0.4
 .if n .sp
 ..
-A tour through the Minix directory hierarchy.
+A tour through the MINIX 3 directory hierarchy.
 .nf
 .SP
 /	root
@@ -59,7 +59,7 @@ A tour through the Minix directory hierarchy.
 	...
 .SP
 /minix
-	Minix kernel image, \fBmonitor\fP(8)
+	MINIX 3 kernel image, \fBmonitor\fP(8)
 .SP
 /tmp/	Small, short-lived temporary files, cf /usr/tmp/
 .SP
@@ -108,7 +108,7 @@ A tour through the Minix directory hierarchy.
 .SP
 	include/
 		C-compiler include files
-		minix/	Minix kernel include files
+		minix/	MINIX 3 kernel include files
 			...
 		...
 .SP
@@ -164,7 +164,7 @@ A tour through the Minix directory hierarchy.
 .SP
 	src/	System and command sources (home of bin)
 		LICENSE
-			Minix license to use
+			MINIX 3 license to use
 		commands/
 			Utility sources
 		crclist

man/man7/man.7

@@ -1,5 +1,5 @@
 .\" man(7) manpage by rosenkra@hall.cray.com (Bill Rosenkranz)
-.\" Modified a bit for Minix by Kees J. Bot (kjb@cs.vu.nl)
+.\" Modified a bit for MINIX 3 by Kees J. Bot (kjb@cs.vu.nl)
 .\"
 .TH MAN 7
 .SH NAME
@@ -26,7 +26,7 @@ reaching a non-indented paragraph (i.e. at .SH or .SS).
 .SH FILES
 .TP 25n
 /usr/lib/tmac/tmac.an
-For standard Minix nroff.
+For standard MINIX 3 nroff.
 .TP
 /usr/lib/cawf/man.mac
 For cawf.
@@ -259,7 +259,7 @@ A typical manual page for a command or function is laid out as follows:
 Even though
 .BR cawf (1)
 has a better chance at formatting a random manual page then the standard
-Minix nroff, it has two annoying bugs in its macro set.  Both .PP and .IP 
+MINIX 3 nroff, it has two annoying bugs in its macro set.  Both .PP and .IP 
 reset the indentation level to the level set by .SH.  This means that
 you can't use them in a piece of text indented by .RS.  For .IP this is
 troublesome, you can see why in the unformatted source of this text.  .PP

man/man8/boot.8

@@ -9,18 +9,18 @@ boot \- from power on to the login prompt
 At power on the machine reads the first sector of the boot device into memory
 and executes it.  This bootstrap code loads
 .BR /boot/boot ,
-the Minix Boot Monitor.  The monitor loads the kernel binaries from
+the MINIX 3 Boot Monitor.  The monitor loads the kernel binaries from
 .BR /boot/image ,
 or the newest file in
 .B /boot/image
 if it is a directory.
 .PP
-The Minix system is now running, the different tasks initialize themselves
+The MINIX 3 system is now running, the different tasks initialize themselves
 and control is transferred to the last one,
 .BR init .
 .PP
 .B Init
-is the grandparent of all Minix processes, it is responsible for starting
+is the grandparent of all MINIX 3 processes, it is responsible for starting
 login processes on each terminal, but first it runs
 .BR /etc/rc .
 .PP
@@ -30,7 +30,7 @@ keyboard translation to the mapping in
 .B /etc/keymap
 if present, followed by a call to
 .BR readclock (8)
-to set Minix time from the hardware clock.  Next the file systems are checked
+to set MINIX 3 time from the hardware clock.  Next the file systems are checked
 if necessary and the
 .B /usr
 file system is mounted.
@@ -110,7 +110,7 @@ This section lists extra variables or variable settings:
 Choose the driver that is to be used as controller
 .IR n ,
 in order: IBM/AT (classic AT or newer IDE), BIOS (any disk), ESDI
-(some PS/2s), IBM/XT, Adaptec 154x, Minix under DOS "file as disk",
+(some PS/2s), IBM/XT, Adaptec 154x, MINIX 3 under DOS "file as disk",
 FAT file system "file as disk".
 By default
 .B at
@@ -311,7 +311,7 @@ It can also be seen among the drivers in the output of
 See also
 .BR inet (8).
 .PP
-In a small network there may not be a DHCP server for Minix to obtain its IP
+In a small network there may not be a DHCP server for MINIX 3 to obtain its IP
 address and name from, so you need specify the ethernet address of your machine
 and host names of all machines in the hosts and DHCP configuration files.
 Suppose your machine is to be named "flotsam", and another machine in the
@@ -428,7 +428,7 @@ Note that
 is sourced, so you can use the same variables and functions that
 .BR /usr/etc/rc
 uses.
-These changes undo all the efforts to make Minix TCP/IP
+These changes undo all the efforts to make MINIX 3 TCP/IP
 autoconfigurable.  Make very sure that all the IP addresses are correct, and
 that the IP address of your machine is unique.  (Mistakenly using the
 address of a main server will make all other machines look at your machine,
@@ -436,7 +436,7 @@ and will make all the users of all other machines look at you.)
 .SH FILES
 .TP 20n
 /boot
-Minix Boot Monitor.
+MINIX 3 Boot Monitor.
 .TP
 /minix
 Kernel image, or directory containing them.
@@ -519,6 +519,6 @@ they are bad.
 Indefinite hangs are possible if I/O addresses or IRQ's are wrong.  A driver
 may babble about addresses and IRQ's, but that does not mean that what it
 says is true, it may just be configured that way.  It is very difficult to
-find peripherals on a PC automatically, and Minix doesn't even try.
+find peripherals on a PC automatically, and MINIX 3 doesn't even try.
 .SH AUTHOR
 Kees J. Bot <kjb@cs.vu.nl>

man/man8/config.8

@@ -1,17 +1,17 @@
 .TH CONFIG 8
 .SH NAME
-config \- configuring Minix tasks and servers
+config \- configuring MINIX 3 tasks and servers
 .SH DESCRIPTION
 .de SP
 .if t .sp 0.4
 .if n .sp
 ..
-Minix has a number of configuration files containing parameters that can
+MINIX 3 has a number of configuration files containing parameters that can
 be changed to enable or disable a device driver, to change the number of
 times a resource can be used, or to tune the performance of the system.
 We will name the file that contains the parameter, the name of the
 parameter, and the values it can be set to.  Some comments are prefixed by
-"8086" for Minix running in 16-bit real mode, "286" for 16-bit protected
+"8086" for MINIX 3 running in 16-bit real mode, "286" for 16-bit protected
 mode, and "386" for 32-bit protected mode.
 Configuration file names can be
 .RI < file.h >
@@ -34,7 +34,7 @@ in 32-bit mode.
 .ti 2m
 .RB < minix/config.h >
 .br
-This is the main configuration file for the Minix.  It contains lots of
+This is the main configuration file for the MINIX 3.  It contains lots of
 boolean variables to enable or disable drivers and a number of parameters
 that specify the sizes of system data structures:
 .TP
@@ -132,14 +132,14 @@ disks.  In real mode it is best to use the BIOS driver.
 Enables the Adaptec 1540 series SCSI driver.
 .TP
 .SB ENABLE_DOSFILE
-Enable the "DOS file as disk" driver that is used when Minix is run from
+Enable the "DOS file as disk" driver that is used when MINIX 3 is run from
 MS-DOS to access a large file as a disk.
 .TP
 .SB ENABLE_FATFILE
 Enable the "FAT file as disk" driver that interprets a FAT file system
 to find a large file to use as a disk.  This driver combined with a fast
-native Minix disk driver is a better choice then the previous driver.  (And
+native MINIX 3 disk driver is a better choice then the previous driver.  (And
-it works when Minix is not started from MS-DOS.)  This is the last driver
+it works when MINIX 3 is not started from MS-DOS.)  This is the last driver
 that needs to be assigned to a controller task.
 .TP
 .SB ENABLE_SB16
@@ -290,7 +290,7 @@ default setting for
 allows up to four backlogged TCP streams, i.e. when data is output faster
 then it is read.  If more buffers are needed then one of the TCP connections
 is shut down.  When this happens you will see a "not enough buffers left"
-error.  This could happen for instance if a Minix web server is assaulted by
+error.  This could happen for instance if a MINIX 3 web server is assaulted by
 a browser that likes to open several connections to the server
 simultaneously.  The fix is to increase
 .SB BUF512_NR

man/man8/cron.8

@@ -113,7 +113,7 @@ if you want to give root the same treatment as ordinary users.
 .SH FILES
 .TP 25n
 .B /usr/lib/crontab
-Main Minix crontab file.
+Main MINIX 3 crontab file.
 .TP
 .B /usr/local/lib/crontab
 Local jobs for all systems in an organization.

man/man8/dhcpd.8

@@ -94,7 +94,7 @@ If the daemon finds out that all networks have an infinite lease (configured
 with a fixed address), there is no router information to keep warm, and
 it isn't a server then it simply exits.
 .SS "Asynchronous I/O?"
-Minix doesn't have the asynchronous I/O that Minix-vmd has, so under Minix
+MINIX 3 doesn't have the asynchronous I/O that Minix-vmd has, so under MINIX 3
 the daemon only works with one network at a time.  If it's stuck on the same
 network for 32 seconds then that network is closed and another network is
 tried for 32 seconds.  This usually works ok as a client, but as a server it
@@ -200,7 +200,7 @@ any IP stack will immediately respond, so that the DHCP server can't
 possibly beat it at sending out an ACK.  (The DHCP server has to commit the
 lease to stable storage first anyway.)
 .PP
-Way more nonsense can be sent in a DHCP packet that Minix could do
+Way more nonsense can be sent in a DHCP packet that MINIX 3 could do
 something with, but nobody does so we don't bother.
 .PP
 DHCP was invented by a rabid gerbil on speed.

man/man8/dosminix.8

@@ -1,6 +1,6 @@
 .TH DOSMINIX 8
 .SH NAME
-dosminix, mkfile \- Running Minix under DOS
+dosminix, mkfile \- Running MINIX 3 under DOS
 .SH SYNOPSIS
 .RB "C:\eMINIX> " "boot disk0.mnx" "\0\0\0\0\0(Typical example)"
 .br
@@ -10,21 +10,21 @@ dosminix, mkfile \- Running Minix under DOS
 .if t .sp 0.4
 .if n .sp
 ..
-This text describes running Minix
+This text describes running MINIX 3
 .\" or Minix-vmd
 under DOS.  The DOS version
 of the Boot Monitor, described in
 .BR monitor (8),
-grabs as much memory as DOS is willing to give, loads Minix into that memory
+grabs as much memory as DOS is willing to give, loads MINIX 3 into that memory
-from the active partition of a "file as disk", and jumps to the Minix kernel
+from the active partition of a "file as disk", and jumps to the MINIX 3 kernel
-to let Minix take control.  As far as DOS is concerned Minix is just a part
+to let MINIX 3 take control.  As far as DOS is concerned MINIX 3 is just a part
 of the
 .B boot.com
 program.
 .PP
 In the example above
 .B disk0.mnx
-is the "file as disk".  It is a file of many megabytes that is used by Minix
+is the "file as disk".  It is a file of many megabytes that is used by MINIX 3
 as a disk of four partitions.  These partitions will normally be
 .B /dev/dosd1
 through
@@ -41,7 +41,7 @@ It is better to use the special name
 to indicate this device, usually in the setting
 .BR rootdev = bootdev .
 .PP
-Once Minix is running it will operate the same as if started from a regular
+Once MINIX 3 is running it will operate the same as if started from a regular
 disk partition until it is shut down.  On shutdown from protected mode it
 will return to the Boot Monitor prompt, and with the
 .B exit
@@ -49,7 +49,7 @@ command you leave the Boot Monitor and return to DOS.  Shutting down from
 real mode will reboot the machine, just like when run from a disk partition.
 (This more or less crashes DOS, but DOS is used to such abuse.)
 .SS EMM386
-Minix can't run in protected mode (286 or 386 mode) if DOS is using a memory
+MINIX 3 can't run in protected mode (286 or 386 mode) if DOS is using a memory
 manager like
 .BR EMM386 .
 You can either temporarily comment out EMM386 from
@@ -90,14 +90,14 @@ anything else, or things will go horribly wrong.  Save MSDOS.SYS and exit.
 Don't forget to make MSDOS.SYS read-only again, and also hide all the hidden
 files again, unless you like it this way.
 .SS "DOS compatibility box"
-The 16-bit version of standard Minix can be run in real mode in a DOS box.
+The 16-bit version of standard MINIX 3 can be run in real mode in a DOS box.
 This is somewhat surprising, because it means Windows 95 simulates devices
-like the keyboard, timer, and interrupt controller well enough to fool Minix
+like the keyboard, timer, and interrupt controller well enough to fool MINIX 3
 into thinking that all is well.  Alas it doesn't work as well under Windows
 NT.  Keypresses get lost if you type to fast, and using the floppy
-occasionally locks Minix up.  This is a bit disappointing, because it is the
+occasionally locks MINIX 3 up.  This is a bit disappointing, because it is the
-only way to run Minix under NT.  Under Windows 95 one is better off
+only way to run MINIX 3 under NT.  Under Windows 95 one is better off
-putting the system in DOS at boot and then to run Minix in protected mode.
+putting the system in DOS at boot and then to run MINIX 3 in protected mode.
 .PP
 One thing that is better under NT is that the Boot Monitor is able to get a
 so-called "Upper Memory Block", thereby raising useful memory to about 750K.
@@ -109,32 +109,32 @@ some of this memory you can put
 at the start of
 .BR autoexec.bat .
 The monitor will grab a 64K UMB if it can get it, and keep that memory safe
-for use by Minix when it is later started from Windows.
+for use by MINIX 3 when it is later started from Windows.
 .PP
-The easiest way to start Minix is to give all Minix disk files the suffix
+The easiest way to start MINIX 3 is to give all MINIX 3 disk files the suffix
 .BR MNX .
 Doubleclick on the disk you want to run to make the "\fBOpen With\fP" window
 appear.  Click on "\fBOther\fP" and browse to the
 .B BOOT.COM
-program.  Set the name of the .mnx files to "\fBMinix "disk" file\fP" in the
+program.  Set the name of the .mnx files to "\fBMINIX 3 "disk" file\fP" in the
 description box if you want everything right.  In the future you can
-just click on a Minix disk file to run it, you don't have to start a DOS
+just click on a MINIX 3 disk file to run it, you don't have to start a DOS
 box first.  (To make it perfect use "View", "Options", "File Types", choose
-"Minix "disk" file", "Edit", "Change Icon", "Browse", select MINIX.ICO.)
+"MINIX 3 "disk" file", "Edit", "Change Icon", "Browse", select MINIX.ICO.)
 .PP
-When Minix shuts down it will try to reboot what it thinks is a PC.  Windows
+When MINIX 3 shuts down it will try to reboot what it thinks is a PC.  Windows
 seems to assume that the DOS session has exited.  Right-click on the
 BOOT.COM program, "Properties", "Program", and enable "Close on exit" to make
-the DOS box disappear automatically when Minix thinks it reboots.  You may
+the DOS box disappear automatically when MINIX 3 thinks it reboots.  You may
 also want to lock the font to
 .BR 7x12 ,
 or any other font that isn't ugly.
 .PP
-Minix disk files are opened in a write-exclusive mode.  A second Minix
+MINIX 3 disk files are opened in a write-exclusive mode.  A second MINIX 3
 session can only open it read-only, which may lead to a "can't open
 root device" error.
 .SS "Mkfile"
-Minix disk files can be created or resized with the
+MINIX 3 disk files can be created or resized with the
 .B mkfile
 utility.  Its two arguments are the size and name of the disk file.  The
 size is a number optionally followed by the letter
@@ -153,7 +153,7 @@ will create a 50 megabyte file named
 If the file already exist then it is shrunk or grown to 50 megabytes.  No
 data is lost if the file is grown.  If the file is shrunk then only the data
 that is cut off is lost.  These features allow one to inrease the size of a
-Minix /usr partition with the following recipe:
+MINIX 3 /usr partition with the following recipe:
 .PP
 .RS
 .ta +24n+2m
@@ -184,11 +184,11 @@ boot disk0.mnx	Run the larger system
 .fi
 .RE
 .PP
-Now Minix runs from a larger "disk".  Don't worry if it claims to have
+Now MINIX 3 runs from a larger "disk".  Don't worry if it claims to have
 crashed, there wasn't a "shutdown" entry in /usr/adm/wtmp at the time it was
 copied.
 .PP
-The above recipe is for a ordinary standard Minix installation with /usr on
+The above recipe is for a ordinary standard MINIX 3 installation with /usr on
 the second and last partition.
 .\" Minix-vmd usually has /usr on the third and
 .\" last partition (dosd3 / dosd8), its
@@ -201,10 +201,10 @@ the second and last partition.
 In the recipe above you saw how simple it is to create a new system, just
 copy a disk file.  It is equally simple to make a backup, you just copy the
 disk file.  To make a test system: copy the disk file.  To make another test
-system: copy the disk file.  Let friends have their own Minix: copy the disk
+system: copy the disk file.  Let friends have their own MINIX 3: copy the disk
 file again.  (Exciting, eh?)
 .PP
-You may want to save a Minix disk file in a ZIP file to save space.  It may
+You may want to save a MINIX 3 disk file in a ZIP file to save space.  It may
 look as a good idea to first run
 .B "make clean"
 in
@@ -233,7 +233,7 @@ will almost disappear in the ZIP file.
 .\" cp /dev/zero junk
 .\" .RE
 .\" .PP
-.\" instead of the echo/while pair of lines above.  Standard Minix doesn't have
+.\" instead of the echo/while pair of lines above.  Standard MINIX 3 doesn't have
 .\" /dev/zero.
 .SS "FAT driver"
 The dos disk driver, described in
@@ -241,8 +241,8 @@ The dos disk driver, described in
 has two identities.  By default you get the "\fBfile\fP" driver, that uses
 DOS file I/O calls to access a large DOS file as a disk.  The other
 alternative is the "\fBFAT\fP" driver.  The FAT driver sits on top of an
-ordinary Minix disk driver, and interprets a partition as a FAT (File Access
+ordinary MINIX 3 disk driver, and interprets a partition as a FAT (File Access
-Table) file system to find a file to use as a Minix disk.  The result
+Table) file system to find a file to use as a MINIX 3 disk.  The result
 has the same effect as the file driver, except that no costly calls to DOS
 are made.  To enable this feature you have to use the following Boot
 environment settings:
@@ -256,10 +256,10 @@ dosd0 = hd1:\eminix\edisk0.mnx
 .PP
 The
 .B dosd
-setting tells Minix to use the FAT driver, and the
+setting tells MINIX 3 to use the FAT driver, and the
 .B dosd0
-setting tells the Minix device and DOS file name to use.  Disk I/O should
+setting tells the MINIX 3 device and DOS file name to use.  Disk I/O should
-be sped up nicely by this change, although typical use of Minix doesn't
+be sped up nicely by this change, although typical use of MINIX 3 doesn't
 require fast disk I/O, so the difference won't be too noticable.
 .PP
 Support for FAT-32 (big file system support added in the later Windows 95
@@ -267,7 +267,7 @@ releases) has not been tested very well.  The FAT-12 and FAT-16 code has
 been used a lot, and seems safe.  Note the risks inherent in these
 drivers:  The file driver uses simple DOS file I/O calls, leaving it to
 DOS to know its own file system.  The FAT driver interprets FAT file system
-structures by itself.  Minix booted from a real hard disk partition can
+structures by itself.  MINIX 3 booted from a real hard disk partition can
 only use DOS disk files through the FAT driver.
 .SH "SEE ALSO"
 .BR dosd (4),

man/man8/fdisk.8

@@ -27,27 +27,27 @@ it.
 It then presents a menu to allow the user to modify partitions, store the
 partition table on a file, or load it from a file.  Partitions can be marked
 as 
-\s-2MINIX\s+2,
+\s-1MINIX 3\s-1,
 DOS or other, as well as active or not.
 Using \fIfdisk\fR is self-explanatory.  
 However, be aware that
 repartitioning a disk will cause information on it to be lost.  
 Rebooting the system \fIimmediately\fR 
 is mandatory after changing partition sizes and parameters.
-\s-2MINIX\s+2, 
+\s-1MINIX 3\s-1, 
 \&\s-2XENIX\s0, \s-2PC-IX\s0, and \s-2MS-DOS\s0 all have different 
 partition numbering schemes.
 Thus when using multiple systems on the same disk, be careful.
 .PP
 Note that
-\s-2MINIX\s+2,
+\s-1MINIX 3\s-1,
 unlike
 \&MS-DOS ,
 cannot access the last sector in a partition with an odd number of sectors.
 The reason that odd partition sizes do not cause a problem with
 \s-2MS-DOS\s0 is that \s-2MS-DOS\s0 allocates disk space in units of
 512-byte sectors, whereas 
-\s-2MINIX\s+2
+\s-1MINIX 3\s-1
 uses 1K blocks.
 \fIFdisk\fR has a variety of other features that can be seen by typing \fIh\fR.
 .PP

man/man8/ftpd.8

@@ -134,7 +134,7 @@ can be used to create or check an anonymous FTP tree.
 .SH BUGS
 The anonymous account is inherently dangerous and should
 avoided when possible.
-.ig \" Minix doesn't have privileged port numbers (yet?)
+.ig \" MINIX 3 doesn't have privileged port numbers (yet?)
 .PP
 The server must run as the super-user
 to create sockets with privileged port numbers.  It maintains

man/man8/inet.8

@@ -93,7 +93,7 @@ Creates pseudo IP network
 usable for IP over serial lines, tunnels and whatnot.
 .RE
 .SH OPTIONS
-Some options can be given between braces.  Minix only understands one of these
+Some options can be given between braces.  MINIX 3 only understands one of these
 options, "default".  Minix-vmd does them all, of course.
 .PP
 .BR default ;

man/man8/init.8

@@ -2,7 +2,7 @@
 .SH NAME
 init \- grandparent of all processes
 .SH DESCRIPTION
-The first program started by Minix is
+The first program started by MINIX 3 is
 .BR init .
 The actions performed by
 .B init
@@ -89,7 +89,7 @@ that line manually,
 doesn't do that for you.
 .TP
 .B SIGTERM
-Normally sent by programs that halt or reboot Minix.  Causes
+Normally sent by programs that halt or reboot MINIX 3.  Causes
 .B init
 to stop spawning new processes.
 .TP
@@ -104,12 +104,12 @@ command.  A second abort signal makes
 .B init
 halt the system directly with a system call.  The keyboard driver halts the
 system, without a sync, after the third CTRL-ALT-DEL.
-.SS "Minix vs. Minix-vmd"
+.SS "MINIX 3 vs. Minix-vmd"
-There are a few differences between standard Minix and Minix-vmd on how
+There are a few differences between standard MINIX 3 and Minix-vmd on how
 .B init
 is run.  The
 .B /etc/rc
-file is executed under standard Minix with input connected to
+file is executed under standard MINIX 3 with input connected to
 .BR /dev/console ,
 but under Minix-vmd this is still
 .BR /dev/null .
@@ -120,7 +120,7 @@ with the
 program if they need user interaction.
 Minix-vmd passes the value of the
 .B bootopts
-boot variable to /etc/rc.  Standard Minix does not.
+boot variable to /etc/rc.  Standard MINIX 3 does not.
 .SH FILES
 .TP 25n
 .B /etc/ttytab

man/man8/installboot.8

@@ -30,7 +30,7 @@ installboot \- make a device bootable
 ..
 .B Installboot
 may be used to make a device bootable by constructing a kernel image and
-installing bootstrap code into the boot block of a Minix file system.  To
+installing bootstrap code into the boot block of a MINIX 3 file system.  To
 understand how this can be done one first has to know what happens when a
 PC is booted.
 .PP
@@ -44,7 +44,7 @@ in the first sector of /dev/fd0, /dev/c0d0p0, /dev/c0d0p1, /dev/c0d0p2, or
 The bootstrap will locate the operating system on the device it itself was
 loaded from, load it, and execute it.
 .PP
-To make a Minix file system
+To make a MINIX 3 file system
 .B /dev/fd0
 mounted on
 .B /mnt
@@ -86,7 +86,7 @@ The
 .B \-image
 option (or the
 .B \-i
-shorthand) combines the executable files needed to run Minix in one file.
+shorthand) combines the executable files needed to run MINIX 3 in one file.
 Only the names and a few zero bytes are inserted into the image.  The name
 is for identification and the zeros are used to pad separate pieces to
 sector boundaries for fast loading.
@@ -156,10 +156,10 @@ Old boot parameters are kept if there are no images added.
 This option fills a blank floppy in
 .I device
 with boot code and kernel images.  This "boot disk" does not have a root
-file system, only the Boot Monitor and Minix kernels.  The boot parameters
+file system, only the Boot Monitor and MINIX 3 kernels.  The boot parameters
 sector is filled with code that enables menu options for selecting an
 image.  After loading an image, the Monitor will ask you to insert a root
-file system diskette before starting Minix.
+file system diskette before starting MINIX 3.
 .SP
 The labels used on the images should match those on the executables used
 inside the image.  You can put a comma separated list of labels on an image
@@ -198,7 +198,7 @@ then its bootstrap code is copied to
 .IR device .
 The master bootstrap on a hard disk boots the active partition on that disk
 at boot time.  The MS-DOS fdisk command normally puts a master bootstrap on
-the hard disk.  Minix has two bootstraps that can be used as a master
+the hard disk.  MINIX 3 has two bootstraps that can be used as a master
 bootstrap,
 .B masterboot
 and
@@ -212,9 +212,9 @@ If installed on a hard disk then it will load the bootstrap of the active
 partition and run it.
 .B Masterboot
 can be put in the first sector of a hard disk to boot the active partition,
-or in the first sector of a Minix partition to boot the active subpartition.
+or in the first sector of a MINIX 3 partition to boot the active subpartition.
 .SP
-If installed on a Minix floppy then it will try to boot the next floppy or
+If installed on a MINIX 3 floppy then it will try to boot the next floppy or
 the first hard disk.  Ideal for floppies with just data on it, they will no
 longer obstruct the boot process if left in the drive.  Also a very useful
 trick to boot from floppy drive 1.
@@ -292,15 +292,15 @@ under MS-DOS 5.0 (or newer) to restore the master bootstrap.
 .SH FILES
 .TP 25
 .B /usr/mdec/bootblock
-Minix bootstrap for the Minix root device.  To be placed in the boot sector.
+MINIX 3 bootstrap for the Minix root device.  To be placed in the boot sector.
 .TP
 .B /usr/mdec/boot
-Minix Boot Monitor.  Can usually be found in the root directory of a bootable
+MINIX 3 Boot Monitor.  Can usually be found in the root directory of a bootable
 device.
 .TP
 .B /usr/mdec/masterboot
 Master bootstrap.  Can be placed in the first sector of a disk to select the
-active partition.  In a Minix primary partition it selects the active
+active partition.  In a MINIX 3 primary partition it selects the active
 subpartition.
 .TP
 .B /usr/mdec/jumpboot
@@ -333,7 +333,7 @@ monitor instead of just "boot"?
 .RE
 .SP
 .I Device
-is not a Minix file system
+is not a MINIX 3 file system
 .RS
 You are using
 .B \-device
@@ -380,9 +380,9 @@ Not bootable
 Partition does not exist (jumpboot), or it's bootstrap isn't executable.
 .RE
 .SH NOTES
-The Minix bootstraps can boot beyond the 8G disk size limit if the BIOS
+The MINIX 3 bootstraps can boot beyond the 8G disk size limit if the BIOS
 supports the IBM/MS INT 13 Extensions.  Alas only Minix-vmd can make use of
-this, standard Minix has a 4G disk size limit.
+this, standard MINIX 3 has a 4G disk size limit.
 .SH BUGS
 It has four more options than the SunOS installboot program it is modeled
 after.

man/man8/irdpd.8

@@ -66,7 +66,7 @@ This daemon has gone out of favour thanks to
 .BR dhcpd ,
 that also does router solicitations among other things.
 .PP
-Under standard Minix this daemon can't listen to both IRDP and RIP
+Under standard MINIX 3 this daemon can't listen to both IRDP and RIP
 at the same time, so it starts out with IRDP.  It switches over to RIP
 if it can't find a router, or if it threatens to lose its router.  It
 does not switch back.

man/man8/mkdist.8

@@ -1,11 +1,11 @@
 .TH MKDIST 8
 .SH NAME
-mkdist \- make a Minix distribution
+mkdist \- make a MINIX 3 distribution
 .SH SYNOPSIS
 .B mkdist
 .SH DESCRIPTION
 .B Mkdist
-makes a Minix distribution on floppies.  Run the command as
+makes a MINIX 3 distribution on floppies.  Run the command as
 .B root
 and follow the instructions.  It will make one or two bootable installation
 floppies and a compressed tar file of

man/man8/monitor.8

@@ -1,6 +1,6 @@
 .TH MONITOR 8
 .SH NAME
-monitor, edparams \- load and start Minix, modify boot parameters
+monitor, edparams \- load and start MINIX 3, modify boot parameters
 .SH SYNOPSIS
 .B /boot
 .br
@@ -17,8 +17,8 @@ monitor, edparams \- load and start Minix, modify boot parameters
 .if n .sp
 ..
 This text describes the Boot Monitor, a boot time interactive program designed
-not only to load and start Minix, its most important task, but to also
+not only to load and start MINIX 3, its most important task, but to also
-provide an interface to configure Minix and to boot other operating systems.
+provide an interface to configure MINIX 3 and to boot other operating systems.
 .PP
 The monitor is controlled with an environment that is modeled after the
 Bourne shell.  This environment is filled at startup with default values
@@ -40,17 +40,17 @@ it commands as arguments.
 .PP
 The DOS version of the monitor, usually named
 .B boot.com
-under DOS, boots Minix from a "DOS virtual disk".
+under DOS, boots MINIX 3 from a "DOS virtual disk".
 .B Boot.com
 is a simple COM program that interprets a DOS
-file as a disk, loads a Minix kernel from the active partition in the same
+file as a disk, loads a MINIX 3 kernel from the active partition in the same
-way as the BIOS based monitor, and executes it to start Minix.  All the
+way as the BIOS based monitor, and executes it to start MINIX 3.  All the
 monitor commands function in the same way, except for the
 .B boot
-command, it can only load Minix.  The monitor grabs as much free memory as
+command, it can only load MINIX 3.  The monitor grabs as much free memory as
-it can for Minix to work in, as the
+it can for MINIX 3 to work in, as the
 .B memory
-variable shows.  Further details on how to run Minix under DOS, Windows 95,
+variable shows.  Further details on how to run MINIX 3 under DOS, Windows 95,
 or even Windows NT are written down in
 .BR dosminix (8).
 .SH COMMANDS
@@ -131,7 +131,7 @@ to initialize?"  Or: "Does the keyboard have LEDs?"
 .SP
 .B memory
 .RS
-List of memory free for use by Minix.  It is a comma separated list of
+List of memory free for use by MINIX 3.  It is a comma separated list of
 .IR base:size
 pairs denoting the byte offsets and sizes of free memory in hexadecimal.
 .B "800:925E0,100000:F00000"
@@ -139,7 +139,7 @@ is a typical example of about 585K starting at 2K, and 15M starting at 1M.
 (The first 2K are BIOS parameters and the 53K under the 640K boundary is
 the monitor itself.)  The very last number you can play with if you know
 what you are doing.  Either increase it if the monitor has it wrong, or
-decrease it to test if Minix still runs with less memory then normal.
+decrease it to test if MINIX 3 still runs with less memory then normal.
 .RE
 .SP
 .B video
@@ -181,7 +181,7 @@ to a suitable default, so that most machines can find their disk.
 .B console
 .RS
 If set to a hexadecimal value it makes the monitor set the BIOS video mode to
-this value when Minix is started.
+this value when MINIX 3 is started.
 This allows the use of video modes with more rows or colums than the
 standard 80x25 mode.  You can use any text mode in the 00-FF range, and VESA
 extended modes in the 100-FFF range.  Most text modes use a 9x16 font with
@@ -221,7 +221,7 @@ The name of the file containing the kernel image, by default
 If it refers to a directory however then the newest file inside the
 directory is chosen to be the kernel image.  The names inside
 .B /minix/
-are best set to the Minix version you are using, which looks good when the
+are best set to the MINIX 3 version you are using, which looks good when the
 monitor prints its name.  Rules for pretty printing image names:
 .RS
 .SP
@@ -253,13 +253,13 @@ image name tell the starting sector and sector count of the image on disk.
 Define function.
 .br
 Functions may be used to bundle a set of commands, so that you can easily
-boot Minix with a different set of parameters then normal.  E.g.
+boot MINIX 3 with a different set of parameters then normal.  E.g.
 .SP
 .RS
 ram() { rootdev=ram; boot }
 .RE
 .SP
-will allow you to run Minix with the root device on RAM for a change, if you
+will allow you to run MINIX 3 with the root device on RAM for a change, if you
 normally use a real device as root.  There are three predefined functions,
 .BR leader ,
 with default value an
@@ -275,7 +275,7 @@ The monitor executes
 .B leader;main
 at startup to show the banner message and a menu.  The
 .B trailer
-function is executed just before Minix is started.  These three functions can
+function is executed just before MINIX 3 is started.  These three functions can
 be redefined as you please.
 .RE
 .SP
@@ -339,17 +339,17 @@ to increase it's heap.
 .br
 \fBboot\fP \fIdevice\fP
 .RS
-Boot Minix or another O.S.
+Boot MINIX 3 or another O.S.
 .br
 Without an argument,
 .B boot
-will load and execute the Minix image named by the
+will load and execute the MINIX 3 image named by the
 .B image
 variable.  With options the variable
 .B bootopts
 is first set to
 .BI \- opts
-before Minix is started, and unset when Minix returns.  With a
+before MINIX 3 is started, and unset when Minix returns.  With a
 .I device
 argument,
 .B boot
@@ -372,7 +372,7 @@ then partition 2 is first made active.  You'll then need to use
 .SP
 with
 .I keys
-chosen so that Minix is booted at startup.  (See
+chosen so that MINIX 3 is booted at startup.  (See
 .BR installboot (8).)
 .RE
 .SP
@@ -381,7 +381,7 @@ chosen so that Minix is booted at startup.  (See
 Copies output to and takes input from serial line
 .I n
 (0-3) at 9600 baud, 8 bits, no parity.
-This allows you to control a Minix system remotely through an RS-232
+This allows you to control a MINIX 3 system remotely through an RS-232
 connection.
 .RE
 .SP
@@ -443,7 +443,7 @@ will use this one hidden built-in function:
 Kernel selecting functions only add new options to this set, but if you
 define a two argument function yourself then the above one is no longer
 shown, allowing you to customize the menu completely.  Your first
-function definition should therefore be one that starts Minix.
+function definition should therefore be one that starts MINIX 3.
 .SP
 Menu entries are shown in the same order as
 .B set
@@ -486,7 +486,7 @@ is killed when the prompt is printed.  Example:
 main() {trap 10000 boot; menu}
 .RE
 .SP
-This gives you 10 seconds to choose a menu option before Minix is booted.
+This gives you 10 seconds to choose a menu option before MINIX 3 is booted.
 .RE
 .SP
 \fBunset\fP \fIname\fP ...
@@ -502,7 +502,7 @@ to remove the "device name translation" property from a variable.
 .RS
 Exit the monitor.
 .br
-Reboot the machine, exit to Minix or exit to DOS as appropriate.
+Reboot the machine, exit to MINIX 3 or exit to DOS as appropriate.
 .RE
 .SP
 \fBoff\fP
@@ -521,7 +521,7 @@ Treat a number of commands as a single command.  Used for function
 definitions when a function body must contain more than one command.
 .RE
 .SH DEVICES
-The Minix kernel can't do anything with device names, so they have to be
+The MINIX 3 kernel can't do anything with device names, so they have to be
 translated to device numbers before they are passed to the kernel.  This
 number is found under the st_rdev field (see
 .BR stat (2))
@@ -537,7 +537,7 @@ or 'c0d0p1s0', and then searched for in /dev.
 .B Bootdev
 can only be translated to a device for the first controller, and only if
 the disks on that controller are numbered without "gaps".  (The master
-device on the second IDE channel is always d2 on Minix.  The BIOS will
+device on the second IDE channel is always d2 on MINIX 3.  The BIOS will
 call it disk 0, 1, or 2 depending on the number of disks on the first
 IDE channel.)
 .SP
@@ -548,7 +548,7 @@ for device names, and it is best to always omit
 .B c0
 for the
 .B boot
-command, and to always use the full name for variables passed to Minix.
+command, and to always use the full name for variables passed to MINIX 3.
 .SH EXTENSIONS
 A few extensions have been made to this program for kernel hackers.  They
 may be triggered by setting bits in the flags word in the kernel startup

man/man8/nonamed.8

@@ -41,7 +41,7 @@ then only the hosts file is used to answer queries, and any query for a name
 not in that file gets a failure response.
 .PP
 .B Nonamed
-accepts both UDP and TCP queries under Minix-vmd.  Under standard Minix
+accepts both UDP and TCP queries under Minix-vmd.  Under standard MINIX 3
 only UDP queries are accepted.  \*(NI relayed UDP queries can be outstanding
 before it forgets where the first one came from.
 .PP
@@ -293,7 +293,7 @@ neighbouring name daemon on another PC at home.
 .PP
 The default cache size seems to be more than enough for normal use, but if
 you do decide to make it larger then don't forget to increase the stack size
-of the program under standard Minix.
+of the program under standard MINIX 3.
 .PP
 Don't let two
 .BR nonamed 's

man/man8/part.8

@@ -30,11 +30,11 @@ values for the base or size of a partition.  These values are: Aligned to a
 cylinder, taped to other partitions (inside or outside), or filling out holes.
 .BR "Use this key" !
 .PP
-Minix subpartition tables or extended partitions may be edited after hitting
+MINIX 3 subpartition tables or extended partitions may be edited after hitting
 the '>' key.  The number of this partition will be shown after the device
 name on the second row, e.g.
 .BR /dev/hd0:2 .
-Minix subpartition tables are shown as is, but extended partition bases are
+MINIX 3 subpartition tables are shown as is, but extended partition bases are
 translated to absolute offsets on the screen to hide the gory details of their
 implementation from the innocent user.  (Hit 'p' if you dare.)  The '<' key
 will bring you back to the enclosing partition table.
@@ -50,7 +50,7 @@ sorted by device number and starting with
 .PP
 Values that are out of range, overlapping, or otherwise strange are shown in
 reverse video.  Values that may possibly be a problem for operating systems
-other then Minix are shown in bold characters.
+other then MINIX 3 are shown in bold characters.
 .PP
 The name of the device is highlighted when it has not been read yet.
 .PP
@@ -65,15 +65,15 @@ if they are inside some other partition, if the base equals the device's base
 complies with the good old \s-2UNIX\s+2 tradition of trusting the user.
 It will write any table, no matter how bad.  You have been warned.
 .PP
-By the way, as far as Minix is concerned there is absolutely no reason to
+By the way, as far as MINIX 3 is concerned there is absolutely no reason to
 make partitions start precisely on a cylinder or track nor does it have to
-be an exact number of cylinders long.  Minix only looks at the base and size
+be an exact number of cylinders long.  MINIX 3 only looks at the base and size
 of a partition, the geometry of the drive doesn't have to be correct.  Other
 Operating systems can be very picky about partitions that are not aligned.
 Some partition editors may refuse to edit a table, others may even make a
 mess of the table.  The only exception is the first partition, it
 traditionally starts on the first track, not the first cylinder.  All
-editors must understand this.  (Subpartition tables are Minix specific, so
+editors must understand this.  (Subpartition tables are MINIX 3 specific, so
 there is no reason at all for any alignment.)
 .SS "Extended Partitions"
 Extended partitions are a mess that is only made slightly better by

man/man8/partition.8

@@ -12,7 +12,7 @@ makes a partition table on
 .I device
 using the types and sizes given.  It may be used in combination with
 .BR repartition (8)
-for automatic installation of Minix.  
+for automatic installation of MINIX 3.  
 .PP
 You may give up to four \fItype\fP:\fIlength\fP[\fB+*\fP] specifications
 for the partitions.  You may also specify holes before, between, and after
@@ -39,12 +39,12 @@ to indicate that an existing partition of the given type must be kept
 from the old partition table.
 .PP
 Partitions are padded out to cylinder boundaries, except for the first one,
-it starts on track 1.  Some operating systems care about this.  Minix and
+it starts on track 1.  Some operating systems care about this.  MINIX 3 and
 MS-DOS do not.
 .SH OPTIONS
 .TP
 .B \-m
-Minix only, no need to pad partitions.  This is the default for subpartition
+MINIX 3 only, no need to pad partitions.  This is the default for subpartition
 tables.
 .TP
 .B \-f
@@ -55,7 +55,7 @@ Play-act, don't write the new table, just show what it would look like.
 .SH EXAMPLE
 .B "partition /dev/hd0 01:16384 81:40000 81:2880* 06:20000+"
 .PP
-Partitions disk 0 into an 8 Mb DOS partition, 20 Mb Minix /usr, 1.44 Mb Minix
+Partitions disk 0 into an 8 Mb DOS partition, 20 Mb MINIX 3 /usr, 1.44 Mb MINIX 3
 / (active), and a DOS partition of at least 10 Mb at the end of the disk.
 (06:0+ would have been ok too, it's just a sanity check.)
 .SH "SEE ALSO"

man/man8/rarpd.8

@@ -21,7 +21,7 @@ looks up the six octet ethernet number in the
 file finding a host name.  This name is translated to the IP address of the
 host by a DNS lookup.  The IP address is then sent to the host.
 .PP
-Under Minix the program forks as needed to give each network its own server.
+Under MINIX 3 the program forks as needed to give each network its own server.
 Under Minix-vmd all networks are handled in the same program using async I/O.
 .SS "Private Ethernet Addresses"
 For VU practical work, where students have to create their own IP stack

man/man8/repartition.8

@@ -26,7 +26,7 @@ repartition /dev/hd4 /etc/hd4.table
 Reload the partition table of drive 0 setting /dev/hd[1\-4], and the
 subpartition table of /dev/hd4 setting /dev/hd4[a\-d] using a file.
 The latter may be useful if you need more than the 4 subpartitions a
-single Minix partition gives you.
+single MINIX 3 partition gives you.
 .SH DIAGNOSTICS
 The new table is printed on standard output.
 .SH FILES

man/man8/serial-ip.8

@@ -12,19 +12,19 @@ serial-ip \- Serial IP (SLIP or PPP) setup
 This text and the serial IP code is not finished.  Code needs to be added to
 .B nonamed
 to allow it to be used both with and without a connection to the Internet,
-and by now there is a PPP program for standard Minix "out there" that will
+and by now there is a PPP program for standard MINIX 3 "out there" that will
 change everything that is said in this text.  So much to do, so little
 time...
 .br
 \-\-\-\-\-\-\-
 .PP
-This manual page describes the Minix network setup to use serial line IP.
+This manual page describes the MINIX 3 network setup to use serial line IP.
 The serial IP protocol used can either be the older SLIP by means of the
 .BR slip (8)
 program, or PPP (Point-to-Point Protocol), the newer and better serial IP
 protocol implemented by the
 .BR ppp (8)
-program.  Alas standard Minix only supports SLIP.
+program.  Alas standard MINIX 3 only supports SLIP.
 .PP
 In the following text all descriptions and examples will name SLIP or the
 .BR slip
@@ -42,7 +42,7 @@ program is like this:
 .PP
 The argument of the program, the
 .B /dev/psip2
-device, is one of the so-called "Pseudo IP" devices that the Minix TCP/IP
+device, is one of the so-called "Pseudo IP" devices that the MINIX 3 TCP/IP
 driver
 .BR inet (8)
 offers to implement a virtual network on.  On an ethernet IP packets are
@@ -58,7 +58,7 @@ through an RS-232 serial line like the second serial line
 as used in the example above.
 .PP
 If we look at the flow of data over normal ethernet then this is what a TCP
-connection between two Minix machines,
+connection between two MINIX 3 machines,
 .B telnet
 for instance, looks like:
 .PP
@@ -112,7 +112,7 @@ by your service provider.  Let's choose another address on that network,
 for instance.  (You can use the address of the SLIP gateway if you want
 to make it look pretty, but it doesn't really matter, anything "out there"
 is ok.)
-To make Minix aware of the situation you have to configure the pseudo IP
+To make MINIX 3 aware of the situation you have to configure the pseudo IP
 network.  For Minix-vmd you need to look for the
 .B if-then-else-fi
 code in
@@ -138,7 +138,7 @@ add_route -g 192.168.0.1
 .fi
 .RE
 .PP
-For standard Minix one has to edit
+For standard MINIX 3 one has to edit
 .B /etc/rc
 instead at the point of the XXX comments.  The
 .B ifconfig

man/man8/slip.8

@@ -19,7 +19,7 @@ The
 .I pseudo-ip-device
 argument names one of the
 .B /dev/psip*
-devices that is offered by the Minix TCP/IP driver
+devices that is offered by the MINIX 3 TCP/IP driver
 .BR inet (8).
 The
 .B slip
@@ -41,7 +41,7 @@ standard output.  A typical use is like this:
 The SLIP protocol is just a very simple packet framing protocol.  It defines
 two characters as markers on a byte stream to frame packets.  SLIP does
 not implement any higher level addressing, error detection, or compression.
-Thanks to its simplicity it can be used under Minix, any other system would
+Thanks to its simplicity it can be used under MINIX 3, any other system would
 prefer to use the Point-to-Point protocol: PPP.
 .PP
 The SLIP packet framing protocol as defined in RFC-1055 is as follows:
@@ -58,7 +58,7 @@ at all by escaping it this way, making finding the framing END easier.)
 .PP
 The manual page
 .BR serial-ip (8)
-describes how to configure the Minix network devices to be used with a
+describes how to configure the MINIX 3 network devices to be used with a
 serial IP connection.
 ..
 .SH FILES
@@ -73,7 +73,7 @@ Pseudo-IP devices for use by
 ..
 .BR RFC-1055 .
 .SH NOTES
-Under Minix
+Under MINIX 3
 .B slip
 forks in two to handle the two data streams in or out of the serial line.
 Under Minix-vmd it uses asynchronous I/O to handle the two streams within

man/man8/sync.8

@@ -18,7 +18,7 @@ sync \- flush the cache to disk
 .EX "sync" "Write out all modified cache blocks"
 .SH DESCRIPTION
 .PP
-\s-2MINIX\s+2
+\s-1MINIX 3\s-1
 maintains a cache of recently used disk blocks.
 The 
 .I sync

man/man9/as.9

@@ -1,3 +1,5 @@
+.so mnx.mac
+.TH AS 9
 .\" unchecked (kjb)
 .CD "as \(en assembler"
 .SE "AS\(emASSEMBLER [IBM]"

man/man9/awk.9

@@ -1,3 +1,5 @@
+.so mnx.mac
+.TH AWK 9
 .CD "awk \(en pattern matching language"
 .SX "awk \fIrules\fR [\fIfile\fR] ...
 .FL "\fR(none)"

man/man9/de.9

@@ -1,3 +1,5 @@
+.so mnx.mac
+.TH DE 9
 .CD "de \(en disk editor"
 .SX "de\fR [\fB\(enw\fR] \fIblock_device"
 .SX "de \(enr \fIfile

man/man9/dis88.9

@@ -1,3 +1,5 @@
+.so mnx.mac
+.TH DIS88 9
 .CD "dis88 \(en disassembler [IBM]"
 .SX "dis88\fR [\fB\(eno\fR] \fIinfile\fR [\fIoutfile\fR]"
 .FL "\(eno" "List the object code along with the assembly code"

man/man9/elle.9

@@ -1,3 +1,5 @@
+.so mnx.mac
+.TH ELLE 9
 .CD "elle \(en ELLE Looks Like Emacs"
 .SX "elle \fIfile\fR [\fIfile2\fR]"
 .FL "\fR(none)"

man/man9/elvis.9

@@ -1,3 +1,5 @@
+.so mnx.mac
+.TH ELVIS 9
 .CD "elvis \(en clone of the Berkeley vi editor"
 .SX "elvis \fR[\fB\(enRerv\fR] [\fB\(ent \fItag\fR] \fR[\fIfile\fR] ..."
 .FL "\(enR" "Set the read-only option"

man/man9/kermit.9

@@ -1,3 +1,5 @@
+.so mnx.mac
+.TH KERMIT 9
 .CD "kermit \(en transfer a file using the kermit protocol"
 .SX "kermit"
 .FL "\fR(many)"

man/man9/m4.9

@@ -1,3 +1,5 @@
+.so mnx.mac
+.TH M4 9
 .CD "m4 \(en macro processor"
 .SX "m4\fR [\fB\(enD \fIname\fR = \fIvalue\fR]\fR [\fB\(enU \fIname\fR] 
 .FL "\(enD" "Define a symbol"

man/man9/macros.9

@@ -1,3 +1,5 @@
+.so mnx.mac
+.TH MACROS 9
 .\" Macro package for producing books (based on -ms)
 .nr PS 12
 .nr PZ 12
@@ -1402,7 +1404,7 @@ Fig.\|\|\|\\*(CN-\\n+k.~\c
 .ds M9 \\s-1MINIX\\s+1
 .ds m0 minix
 .de MX
-\s-2MINIX\s+2\\$1
+\s-1MINIX 3\s-1\\$1
 ..
 .de Ux
 \s-2UNIX\s+2\\$1

man/man9/mined.9

@@ -1,3 +1,5 @@
+.so mnx.mac
+.TH MINED 9
 .CD "mined \(en \*(M2 editor"
 .SX "mined\fR [\fIfile\fR]
 .FL "\fR(none)"