1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- This document was generated using DocBuilder 3.3.3 -->
<HTML>
<HEAD>
<TITLE>Installation</TITLE>
<SCRIPT type="text/javascript" src="../../doc/erlresolvelinks.js">
</SCRIPT>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#FF00FF"
ALINK="#FF0000">
<CENTER>
<A HREF="http://www.erlang.se"><IMG BORDER=0 ALT="[Ericsson AB]" SRC="min_head.gif"></A>
</CENTER>
<A NAME="1"><!-- Empty --></A>
<H2>1 Installation</H2>
<A NAME="1.1"><!-- Empty --></A>
<H3>1.1 UNIX</H3>
<A NAME="1.1.1"><!-- Empty --></A>
<H4>1.1.1 Introduction</H4>
<P>The system is delivered as a single compressed tar file.
<P>To browse the on-line HTML documentation, Netscape or an equivalent
browser supporting frames is needed.<A NAME="1.1.2"><!-- Empty --></A>
<H4>1.1.2 Installation Procedure</H4>
<P>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 <CODE>$PATH</CODE>. The only requirements
are that the file system where it is placed has enough free space,
and that the users who run Erlang/OTP have read access to it. In the
example below, the directory tree is assumed to be located at
<CODE>/usr/local/erlang</CODE>, which is here called the <STRONG>top-level
directory</STRONG>.
<P>It is assumed that you have the compressed tar file, the name of
which is <CODE><PREFIX>.tar.gz</CODE>, where <CODE><PREFIX></CODE> is a string
denoting the particular Erlang/OTP release, e.g.
<CODE>otp_LXA_11930_sunos5_R9B</CODE>.
<P>Wherever the string <CODE><PREFIX></CODE> is used below, it should
be replaced by the actual name prefix of the compressed tar file.
<P>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.
<P>
<OL>
<LI>
If the <STRONG>top-level directory</STRONG> does not already exist,
create it:<BR>
<PRE>
mkdir /usr/local/erlang
</PRE>
</LI>
<LI>
Change the current directory to the <STRONG>top level
directory</STRONG>:<BR>
<PRE>
cd /usr/local/erlang
</PRE>
</LI>
<LI>
Create the <STRONG>installation directory</STRONG> with an appropriate
name. For example:
<BR>
<PRE>
mkdir otp_r7b
</PRE>
</LI>
<LI>
Change to the <STRONG>installation directory</STRONG>, e.g.<BR>
<PRE>
cd otp_r7b
</PRE>
</LI>
<LI>
Assuming the compressed tar file resides in the directory
<CODE><SOME-DIR></CODE>,. extract the compressed tar file into the
current directory:<BR>
<PRE>
gunzip -c <SOME-DIR>/<PREFIX>.tar.gz | tar xfp -
</PRE>
</LI>
<LI>
Read the <CODE>README</CODE> file in the installation directory for
last minute updates, before proceeding.<BR>
</LI>
<LI>
Run the <CODE>Install</CODE> script in the installation directory,
with the absolute path of the installation directory as argument,
<BR>
<PRE>
./Install /usr/local/erlang/otp_r7b
</PRE>
and supply answers to the prompts.<BR>
In most cases, there is a default answer in square brackets
(<CODE>[]</CODE>). If the default is satisfactory, just press
<CODE><Return></CODE>. In general you are only prompted for one thing:
<BR>
<UL>
<LI>
"Do you want to use a minimal system startup instead of the
SASL startup?"<BR>
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.<BR>
</LI>
</UL>
</LI>
<LI>
Make Erlang/OTP available for users, either by putting the path
<CODE>/usr/local/erlang/otp_r7b/bin</CODE> in users <CODE>$PATH</CODE>
variable, or link the executable
<CODE>/usr/local/erlang/otp_r7b/bin/erl</CODE> accordingly, e.g.:<BR>
<PRE>
ln -s /usr/local/erlang/otp_r7b/bin/erl /usr/local/bin/erl
</PRE>
</LI>
</OL>
<A NAME="1.2"><!-- Empty --></A>
<H3>1.2 Windows</H3>
<A NAME="1.2.1"><!-- Empty --></A>
<H4>1.2.1 Introduction</H4>
<P>The system is delivered as a single <CODE>.exe</CODE> file.
<P>To browse the on-line HTML documentation, Netscape or an equivalent
browser supporting frames is needed.<A NAME="1.2.2"><!-- Empty --></A>
<H4>1.2.2 Installation Procedure</H4>
<P>The installation procedure is is automated. Double-click the
<CODE>.exe</CODE> file icon and follow the instructions.<CENTER>
<HR>
<SMALL>
Copyright © 1991-2006
<A HREF="http://www.erlang.se">Ericsson AB</A><BR>
</SMALL>
</CENTER>
</BODY>
</HTML>
|
