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

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
-it works when Minix is not started from MS-DOS.)  This is the last driver
+native MINIX 3 disk driver is a better choice then the previous driver.  (And
+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
-from the active partition of a "file as disk", and jumps to the Minix kernel
-to let Minix take control.  As far as DOS is concerned Minix is just a part
+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 3 kernel
+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
-only way to run Minix under NT.  Under Windows 95 one is better off
-putting the system in DOS at boot and then to run Minix in protected mode.
+occasionally locks MINIX 3 up.  This is a bit disappointing, because it is the
+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 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
-Table) file system to find a file to use as a Minix disk.  The result
+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 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
-be sped up nicely by this change, although typical use of Minix doesn't
+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 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"
-There are a few differences between standard Minix and Minix-vmd on how
+.SS "MINIX 3 vs. Minix-vmd"
+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
-provide an interface to configure Minix and to boot other operating systems.
+not only to load and start MINIX 3, its most important task, but to also
+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
-way as the BIOS based monitor, and executes it to start Minix.  All the
+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 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
-it can for Minix to work in, as the
+command, it can only load MINIX 3.  The monitor grabs as much free memory as
+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