Andy's enormous "Minix" -> "MINIX 3" crusade ;)
This commit is contained in:
@@ -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()
|
||||
|
||||
+1
-1
@@ -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
|
||||
|
||||
+1
-1
@@ -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
|
||||
|
||||
+1
-1
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
+3
-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
|
||||
|
||||
@@ -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>
|
||||
|
||||
+1
-1
@@ -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.
|
||||
|
||||
+2
-2
@@ -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 ,
|
||||
|
||||
+1
-1
@@ -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)
|
||||
|
||||
Reference in New Issue
Block a user