This document describes installation procedures for binary releases. Documentation of the build and installation procedures for the source release can be found in the source tree at the following locations:
Where
The system is delivered as a single compressed tar file.
To browse the on-line HTML documentation, Netscape or an equivalent browser supporting frames is needed.
When installed, the entire system, except for a small start-up
script, resides in a single directory tree. The location of this
directory tree can be chosen arbitrarily by the installer, and it
does not need to be in the user's
It is assumed that you have the compressed tar file, the name of
which is
Wherever the string
The tape archive file does not have one single directory in which all other files are rooted. Therefore the tape archive file must be extracted into an empty (newly created) directory.
If the top-level directory does not already exist, create it:
mkdir /usr/local/erlang
Change the current directory to the top level directory:
cd /usr/local/erlang
Create the installation directory with an appropriate name. For example:
mkdir otp_r7b
Change to the installation directory, e.g.
cd otp_r7b
Assuming the compressed tar file resides in the directory
gunzip -c <SOME-DIR>/<PREFIX>.tar.gz | tar xfp -
Read the
Run the
./Install /usr/local/erlang/otp_r7b
and supply answers to the prompts.
In most cases, there is a default answer in square brackets
(
"Do you want to use a minimal system startup instead of the
SASL startup?"
In a minimal system, only the Kernel and STDLIB applications
are loaded and started. If the SASL startup is used, the SASL
application is included as well. Normally, the minimal system
is enough.
Make Erlang/OTP available for users, either by putting the path
ln -s /usr/local/erlang/otp_r7b/bin/erl /usr/local/bin/erl
The system is delivered as a single
To browse the on-line HTML documentation, Netscape or an equivalent browser supporting frames is needed.
The installation procedure is is automated. Double-click the