.th "KSOS RC" V 4/21/86
.sh "NAME"
/sys/rc - KSOS initialization command file
.sh "DESCRIPTION"
The /sys/rc file is a means by which certain commands may be executed
during the startup of the KSOS system in an automatic and preset
fashion.  This command file is normally used to check the integrity of
filesystems, mount filesystems, start daemons, and execute special
one-time-only system initialization procedures.
.s1
At system startup, the KSOS process, SIP, reads the file '/sys/rc' and
treats each line within the file as if it is a command line to be
executed by the KSOS process, SSP.  Furthermore, each line must
reference a command by it's fully-specified pathname.  Also, a command
line can specify another file to be processed as an indirect command
file.
.s1
Comments are not allowed.  An additional command file is specified by
its pathname and any arguments are ignored.  Blank lines are ignored.
Extra spaces or tabs are ignored if not included within double-quote
marks.
.s1
Asynchronous execution of a command (e.g. starting a daemon) is indicated
by the '&' (ampersand) character at the end of the line. Indirect
command files can not be executed asynchronously.
.sh "NOTES"
At the moment, access to 'rc' files from UNIX is only by means of the
tools 'krd' and 'kwr'.  The 'rc' files may ONLY be modified under UNIX
as there are no editors executable under KSOS.  The modification
process is as follows:
.s2
krd > 'a temp file'
.br
/dev/ksos        (the device name)
.br
6                (the device extent)
.br
/sys/rc          (the full pathname of the file)
.br
              this will retrieve the 'rc' file from KSOS
.s2
[edit the 'rc' file in whatever manner you prefer]
.s2
kwr
.br
/dev/ksos        (the device name)
.br
6                (the device extent)
.br
name of the 'temp file'    (pathname to be read from)
.br
/sys/rc          (full pathname to be written to)
.br
blank filename to exit
.br
              this will replace the 'rc' file back to KSOS
.s3
.sh "EXAMPLES"

/sys/server/user/TCP 1 10 2 3 &

/sys/server/user/TCP 2 10 2 3 &

/sys/server/user/TCP 3 10 2 3 &

/sys/server/operator/STC d4/0 6

/sys/tmp/f17  2

/sys/tmp/f01     '    ' was 4

/sys/server/operator/STC      d4/0     8

/sys/server/user/TEST4

.sh "CAVEATS"
At the present time, the ownership/security information used in the
execution of each command is derived from the command file's jnode.
Also, no conditional command execution is possible because there is
no general means of returning execution status.
