SASH(1Mspp) RISC/os Reference Manual SASH(1Mspp)
NAME
sash - general description of the standalone shell
SYNOPSIS
sash [ -a ] [ -r ] [ file [ args ]]
DESCRIPTION
sash is the MIPS standalone shell. The standalone shell is
an extended version of the PROM Monitor that includes all
the PROM Monitor commands. In addition to the PROM Monitor
commands, sash includes additional commands and is config-
ured with more device drivers and file system types. Sash
exists so that the MIPS standalone programs and the PROM
Monitor are not dependent on the operating system.
The sash program is booted using the PROM Monitor Boot com-
mand. The sash program can be booted from a cartridge tape,
from a hard disk if the software has already been installed,
or from the network. To boot the sash program from the net-
work, a machine must be running the bootfile Server Daemon
bfsd(8).
To load the sash program from the network, type:
boot -f bfs()sash [-a][-r] [file[args]]
The parenthesis in the commands shown above indicate that
the previous argument is a device. When booting over the
network, if the command is entered as shown, then it will
boot sash from the first machine that has the program the
machine name and path name.
If sash is booted without arguments, then the sash command
mode is entered. The sash command prompts is shown below.
sash:
If the -a argument is used as the first argument, then sash
assumes that an automatic operating system boot is to be
done. Sash examines the name by which it was booted and
uses the same device, controller, and unit to look for an
operating system to boot. Sash finds the correct operating
system file to boot by examining the disk volume header on
the specified device. The volume header specifies a root
partition and an operating system file name. Once the
appropriate operating system file is determined, sash boots
the operating system and passes the -a argument and any
other arguments following the -a to the operating system.
If the -r argument is specified as the first argument, then
sash assumes that the next argument is a standalone program
that is being booted by a remote debugger. Sash defines the
Printed 11/30/90 Page 1
SASH(1Mspp) RISC/os Reference Manual SASH(1Mspp)
environment variables "dbgmon" and "rdebug", boots the file
specified by the argument after the -r flag, and passes any
succeeding arguments. If the booted program was linked
against the standalone library, then the start-up code pro-
vided will note the environment variables "dbgmon" and "rde-
bug" and load the debugging monitor co-resident with the
program. This causes the program to enter the remote debug-
ging mode.
If any other argument is passed to sash when it is booted,
then sash interprets the argument as the file name of a pro-
gram to be booted immediately. Any other arguments appear-
ing on the command line to call sash will be passed through
to the booted program. Therefore, if the PROM Monitor
environment variable bootfile is set as "sash" and the com-
mand listed below was entered on the PROM Monitor command
line, then the PROM Monitor would load the file indicated by
the environment variable bootfile. The bootfile contains the
sash program.
boot dkis()unix or boot dkip()unix or boot
dksd()unix
EXTENDING THE STANDALONE SHELL
If you type a sash command on the sash command line that is
not built-in , then sash uses the first word of the command
as the name of a file. Sash then tries to boot that file by
passing any other arguments on the command line to the
booted program. This mechanism makes two-level boots possi-
ble.
If the environment variable $path is not defined, then the
first word of the command must be a complete file name
specification consisting of a device name, controller, unit,
partition, and a file path. If the environment variable
$path formed by prepending the contents of $path to the ori-
ginal file name. If $path is a list of prefixes separated
by spaces, then the standalone shell will try each prefix
from $path until the file is successfully booted or until
all prefixes have been tried.
SASH COMMANDS
When sash is booted without arguments, the sash command mode
is entered. From the command mode prompt, memory and
environment variables can be displayed and altered, and
other programs can be booted. All of the commands shown
below except cp(1) are PROM Monitor commands and can be
found in their own man page listing.
auto Initiates the two-level operating system auto-
boot sequence.
Page 2 Printed 11/30/90
SASH(1Mspp) RISC/os Reference Manual SASH(1Mspp)
boot Loads the specified program.
cat Displays the contents of the files listed on the
console.
cp Copies the contents of one file to another file.
disable Does not allow input from an output to the
specified console device.
dump Formats and displays the contents of memory.
enable Allows input from and output to the specified
console device.
fill Fills the specified range of memory with the
specified pattern.
g Displays the contents of a single memory loca-
tion in decimal, hexadecimal, and ASCII charac-
ter formats.
go Transfers control to code that is assumed to
have been previously loaded.
help Displays the syntax for all commands.
init Reinitializes the PROM Monitor software state.
init_tod Initializes the time-of-day chip.
inittod Initializes M/2030 time-of-day chip.
load Allows you to load memory over a serial line
connection from a system running the RISC/os
program cu(1).
p Puts or sets the contents of a single memory
location to a specified value.
printenv Displays the value of the PROM environment vari-
ables.
setenv Used to create a new environment variable or to
change an existing environment variable.
sload Accepts a subset of the Motorola S-record proto-
col.
spin Generates reference patterns for diagnostic use.
unsetenv Used to delete an existing environment variable.
Printed 11/30/90 Page 3
SASH(1Mspp) RISC/os Reference Manual SASH(1Mspp)
warm Examines memory for a restart block.
SEE ALSO
prom(1Mspp).
intro(1spp), dbgmon(1spp) in the System Programmer's Pack-
age.
Page 4 Printed 11/30/90