Install an OS and supporting software (see Install a Unix-like OS or Appendix A, Install Red Hat 8/9 - for more details). See the Table 2.2, + for more details). See the +Table 2.2, “Version Compatibility Matrix”.
Install a database (see the section called “Install Oracle 8.1.7” or @@ -92,14 +93,13 @@ createdb $OPENACS_SERVICE_NAME
-Setting a global shell variable for
-cut and paste. In order to cut and paste the
-instructions into your shell, you must set the environment variable
-$OPENACS_SERVICE_NAME. In order to set it globally so that it works
-for any new users or special service users you may create, edit the
-file /etc/profile (
-/etc/share/skel/dot.profile for
-FreeBSD) and add this line:
+Setting a global shell +variable for cut and paste. In order to cut +and paste the instructions into your shell, you must set the +environment variable $OPENACS_SERVICE_NAME. In order to set it +globally so that it works for any new users or special service +users you may create, edit the file/etc/profile(/etc/share/skel/dot.profilefor FreeBSD) +and add this line:export OPENACS_SERVICE_NAME=service0
None of these locations are set in stone - they're simply the
-values that we've chosen. The values that you'll probably want to
-change, such as service name, are marked like
+ None of these locations are set in stone - they're simply
+the values that we've chosen. The values that you'll
+probably want to change, such as service name, are marked like
this. The other values we recommend you leave
unchanged unless you have a reason to change them. Some of the paths and user accounts have been changed from those
@@ -157,31 +157,34 @@
We'll do our best to assure that following our instructions will
-get you to the promised land. If something goes wrong, don't panic.
-There are plenty of ways to get help. Here are some tips: We'll do our best to assure that following our instructions
+will get you to the promised land. If something goes wrong,
+don't panic. There are plenty of ways to get help. Here are
+some tips: Keep track of the commands you are run and record their output.
I like to do my installations in a shell inside of emacs
( We'll point out where the error logs for the various pieces of
-software are. Output from those logs will help us help you. Don't
-worry if you feel overwhelmed by all the information in the error
-logs. Over time, you'll find that they make more and more sense.
-Soon, you'll actually look forward to errors so that you can run to
-the log and diagnose the problem. Search the forums at openacs.org - you'll often find many
-people who have struggled through the same spot that you're in. The bottom of each page has a link to OpenACS.org, where you can
+ We'll point out where the error logs for the various pieces
+of software are. Output from those logs will help us help you.
+Don't worry if you feel overwhelmed by all the information in
+the error logs. Over time, you'll find that they make more and
+more sense. Soon, you'll actually look forward to errors so
+that you can run to the log and diagnose the problem. Search the forums at openacs.org - you'll often find
+many people who have struggled through the same spot that
+you're in. The bottom of each page has a link to OpenACS.org, where you can
post comments and read other users comments about the contents of
the page. Ask questions at the irc channel on freenode.net (#openacs).
-They're knowledgeable and quite friendly if you can keep them on
-topic. Post a question on the forums. Make sure
-you've done a search first. When you do post, be sure to include
-your setup information (OS, etc) as well as the exact commands that
-are failing with the accompanying error. If there's a SQL error in
-the Tcl error or in the log, post that too. If you find errors in this document or if you have ideas about
+They're knowledgeable and quite friendly if you can keep them
+on topic. Post a question on the forums. Make sure
+you've done a search first. When you do post, be sure to
+include your setup information (OS, etc) as well as the exact
+commands that are failing with the accompanying error. If
+there's a SQL error in the Tcl error or in the log, post that
+too. If you find errors in this document or if you have ideas about
making it better, please post them in our BugTracker.Note
M-x shell) so that I can save
the output if needed. An alternative would be to use the
-script command.script command.