$Id: manual,v 1.1 1996/03/20 20:01:23 paul Exp $ 
    

Manual pages for SunOS Minix commands
-------------------------------------

Command:   sunread - read a SunOS file
Syntax:    sunread file
Examples:  sunread commands/bin/cp >cp  # copy 'cp' onto the Minix file system
	   sunread /etc/passwd		# read the SunOS password file
Flags:	   none
  
  Sunread reads the desired SunOS file onto the Minix user's current
standard output. If a relative pathname is supplied, it is relative to
the user's current SunOS directory when Minix was booted.  Since SunOS
and Minix files use the same end of line character, there is no
distinction between text and binary files.



Command:   sunwrite - write a SunOS file
Syntax:    sunwrite file
Examples:  sunwrite rc </etc/rc  # copy /etc/rc into the current SunOS dir.
	   sunwrite /dev/console # copy standard input onto the Sun's console
Flags:	   none

  Sunwrite is the opposite of Sunread in that it copies Minix's
standard input to a given SunOS file. 'sunwrite' is a link to 'sunread'



Manual pages for extra SunOS utilities
--------------------------------------

Command:   minix - start up Solaris Minix
Syntax:    minix [config-file]
Flags:	   -d Turn on debugging
	   -mnone No memory protection
	   -mhalf Partial memory protection (the default)
	   -mfull Full memory protection
	   
  The program loads the Minix kernel, memory manager, file system and
init into memory and passes control to the Minix kernel.  A
configuration file is used to specify a setup for your Minix
system.  Typing 'minix <config file>' can be used to select a
particular configuration, otherwise the current directory then your
home directory are searched for the file '.minix'.  If you wish to kill
SunOS Minix from within SunOS, you should use 'ps' to find the process
id of the second Minix process and then use 'kill'. Try to refrain from
using 'kill -9' unless absolutely necessary.

Using a command line option, it is possible to enable one of three
levels of memory protection. The first level results in no protection
at all. The second level makes the text segment of each Minix process
read only and disallows access to memory that is not currently in
use. The third level gives almost complete protection such that a
process may only reference its own address space and not that of other
processes or the kernel. Due to the overhead caused by the software
controlled context switching, this third level would normally only be
used to detect serious memory corruption problems.


Command:   mcc - compile a Minix C program
Syntax:    similar to gcc
Flags:	   similar to gcc

  This is simply a shell script that executes gcc with the correct
command line options, include files and libraries.  In order to use
mcc, the environment variables MX_INCL and MX_LIB must be defined
correctly.  The -S option can be used to sepcify the stack + heap
space to allocate when the program is started.  The amount of space is
specified as per the stanadrd minix install command.

Note that if include files cannot be found in $MX_INCL, then
/usr/include will be searched.  Solaris Minix programs should get
all of their include files from $MX_INCL.  mcc -M can be
used to check which files are actually included.


Command:   mlogin - login into Minix
Syntax:    mlogin hostname
Flags:	   none

mlogin is used to login to an existing Minix system.  The Minix
system can be any of those that are currently executing on the Sun
system that is executing mlogin.  The minix configuration file used
when booting the 'logged into' Minix system must supply a unique host
name.  That hostname is the one that must be supplied to mlogin.
To exit from mlogin, hold down the control key and type 'quit'.
