Running System/161

There are two versions of System/161 that are built and installed: the normal one, sys161, and one compiled to be able to log information about what's happening and generally assist debugging, which is called trace161.

The general format for the command line for either of these is like this:

sys161 [ System/161 options ] kernel [ kernel options ]

The System/161 options are:

-c configfile

Specify alternate config file. Default is sys161.conf.

-p port

Listen for debugger connections on specified TCP port. The default is to use the Unix-domain socket ./.sockets/gdb for debugger connections.
Note: because the remote gdb protocol does not support authentication, use this option only with caution.

-s

Pass signal-generating characters (^C, ^Z, etc.) through to the running kernel instead of treating them as requests to sys161.

-w

Wait for a debugger connection immediately on startup.

The following additional options control trace161's tracing and are ignored by sys161:

-f tracefile

Set the file trace information is logged to. By default, stderr is used. Specifying -f- sends output to stdout instead of stderr.

-t traceflags

Tell System/161 what to trace. The following flags are available:

d	Trace disk I/O
e	Trace emufs I/O
j	Trace jumps and branches
k	Trace instructions in kernel mode
n	Trace network I/O
t	Trace TLB/MMU activity
u	Trace instructions in user mode
x	Trace exceptions

Caution: tracing instructions generates huge amounts of output that may overwhelm smaller host systems.

The following option is also only available in trace161:

-P

Collect a kernel profile and leave it in the file gmon.out for analysis by gprof.

The kernel is an operating system kernel to load and run. It should be an ELF-format executable for the same processor type as System/161 is compiled to support. For further information, see below.

Note that options found after the kernel name will be passed to the kernel and not interpreted by System/161.