Getting Started with SAM
========================

SAM provides three wizard scripts to get started with SAM 

o getsolaris  -  create a directory with Solaris software
o simulate    -  create a SAM configuration (rc-file) and start SAM

These three wizard scripts are in the bin directory of the release.
In this document we assume that this bin directory is on your PATH.

There are man pages under the man directory of the release. Add the 
man directory to you MANPATH environment variable to see the man
pages for the three wizard scripts.

% man getsolaris
% man simulate


Solaris
=======

First get a set of binaries to run Solaris
To see which Solaris versions are available do:

% getsolaris -p n2 -l

This will output something along the lines of

Use -v with one of:  int12

Then use -v with the version you want to use:

% getsolaris -p n2 -v int12 int12

This creates a directory int12 that contains a number
of soft-links 

% cd int12
% ls -l
total 42
...
...      52 Mar 28 16:00 disk1 -> .../disk1
...

If you see the above you are ready to start running SAM. If not then
check the error message: is the version correct? does the directory exist?
getsolaris expects that the destination directory int12 does not exists.

Now start SAM through the wizard

% simulate -p n2 -c 1c1t -s -a -v

This will create a SAM n2 configuration for the 1c1t (one strand)
machine description (md). The -s option tells simulate to boot 
solaris, -a tells simulate to auto boot obp followed by solaris,
and -v tells simulate to boot solaris in verbose mode.

At the SAM prompt 'sam>>>' type run, and this should take you to
the solaris login prompt. Login as root.

A bigger configuration can be booted with 

% simulate -p n2 -c 1c2t -w2 -s -a -v

using a two strand md (cpu0 and cpu2) and two worker threads. 
Make sure you use -w P on a machine with P or more cpus.