uncompress
or zcat
and the tar
utilities
SATAN
.
Then:
cd SATAN
'SATAN.<os>.<yymmr>.tar.Z'
or
'SATAN.<os>.<yymmr>.tar.gzip'
where <os>
stands
for the operating system, e.g. AIX
or Linux
,
<yymmr>
denotes some version number,
e.g. 0112c
zcat SATAN.AIX.0112c.tar.Z | tar -xvf -(you might also use separate calls of
uncompress
and
tar
)
$SATAN
to point to the SATAN
directory:
export SATAN=`pwd`This is the quick and dirty way. To be permanent you must define the shell variable in your login script (e.g.
.profile
if you use the ksh
)
export PATH=$SATAN/bin:$PATH
satan tut flegAs of the
0112g
release, versioning is supported,
i.e. in addition to the normal version selected by $SATAN
,
$SATANNEW
, $SATANOLD
and $SATANTEST
may point to different directories and are selected by the
new
, old
and test
keywords, respectively, of the various shell scripts.
Note, however, that also the PATH
variable should reflect the chosen version.
SATAN
-related files in
a single directory. Assume the installation directory is work:SATAN
.
Then:
cd SATAN
'SATAN.amiga.<yymmr>.run'
where <yymmr>
denotes some version number,
e.g. 0112g
satan.amiga.0112g.run
SATAN
to point to the SATAN
directory:
assign SATAN: work:SATAN setenv SATAN work:SATANThis is the quick and dirty way. To be permanent you must put these definitions in your startup procedure, e.g.
s:user-startup
PATH SATAN:C add
SATAN
with a tutorial
satan tut flegAs of the
0112g
release, versioning is supported,
i.e. in addition to the normal version selected by SATAN:
,
SATANNEW:
, SATANOLD:
and SATANTEST:
may point to different directories and are selected by the
new
, old
and test
keywords, respectively, of the various shell scripts.
Note, however, that also the PATH
definition should reflect the chosen version.