Hits since 2023-09-15 14:33:15:
1373
|
|
Click here to download
SAM-1.3.tar.gz.
(162 downloads since
2023-12-05 23:39:00)
The last-modified dates and times for the changlog.txt files (see
below) give a good indication of when and where changes were last
made. Download and unpack SAM, then read the changlog.txt files
for more information:
Date Time Log File
231022 19:16 ./lib/tool/changlog.txt
231022 19:16 ./changlog.txt
231022 19:17 ./kernel/changlog.txt
231022 19:35 ./main/changlog.txt
|
|
|
SAM was made for Slackware Linux, although it may work in
other Linux distributions.
Make a directory for SAM. For example:
mkdir /tmp/SAM_root
In the directory you made, unpack SAM. For
example:
cd /tmp/SAM_root
tar -xvzf <path to downloads>/SAM-1.3.tar.gz
Please see Unpacking SAM.
You may want to compile SAM's binaries. This is not
normally required, as suitable binaries are provided. To
compile them, first find their parent directories in
source. For example:
cd /tmp/SAM_root/kernel/source
|
|
|
Please be careful. You are fully responsible for your
use of SAM, even if I have made huge and unforgivable
errors.
As an ordinary user or as root, run SAM's "begin"
command. For example:
/tmp/SAM_root/begin
Please do not change your PATH to include the location of
SAM. Most of the executables in the root of SAM need to be
invoked using their full paths.
Although you can run SAM from the directory you made, it is not
recommended that you make any configuration changes there.
Instead, follow the directions below for setting up and using Dual
Mode.
|
|
|
Dual Mode allows you to install SAM to one directory, but
configure it in a separate, dual directory. This is a
benefit, as you can thus keep your configuration across minor version changes.
Do the above steps and verify that SAM runs.
As root: Make a dual directory for SAM.
For example:
mkdir /tmp/Dual
Make symlinks in the dual directory to represent
begin and other executables in the root of
SAM that you wish to use in SAM. Each symlink you make points
to bgen, but you give it the name of the executable
you wish it to represent. For example, you could do this as
root in /tmp/Dual:
ln -s /tmp/SAM_root/bgen begin
Copy files bprofile and
init and directory lib from SAM to
the dual directory. Use suitable file
permissions.
As an ordinary user or as root, run SAM's "begin"
command. For example:
/tmp/SAM_root/begin
Please heed the above advice about not changing the PATH, as it
applies also to the executables of the dual directory.
Not only may you run begin and the other
executables of the SAM directory via the symlinks in the dual
directory, but you may also make configuration changes to it, such
as changing files bprofile, init,
or the contents of directory lib.
|
|
|
SAM doesn't do anything. It changes
your environment, and that is all. By changing your environment,
it changes what you can do, namely it provides
access to new commands. To point you in the right direction I
will tell you about one of the new commands, then let you discover the
rest.
That command is:
menu
Try it! It will display information about the current
menu and command set
and also give a short tutorial.
When you are done with SAM, please use the (familiar)
exit command to return to the environment from which
you came.
|
|
|