Minix/minix
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
Ben Gras
2005-08-22 12:56:02 +00:00
parent f4402bd129
commit 05930b53de
98 changed files with 326 additions and 306 deletions
Download Patch File Download Diff File Expand all files Collapse all files
man/man5/crontab.5
+1 -1
View File
@@ -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
+7 -7
View File
@@ -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
+1 -1
View File
@@ -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
+1 -1
View File
@@ -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
+2 -2
View File
@@ -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
+2 -2
View File
@@ -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
+1 -1
View File
@@ -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
+1 -1
View File
@@ -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.