head	1.23;
access;
symbols
	caudium_1_4_9:1.20.2.3
	caudium_1_4_8:1.20.2.3
	caudium_1_4_7:1.20.2.3
	caudium_1_4_6:1.20.2.3
	caudium_1_2_35:1.11.2.7
	caudium_1_2_34:1.11.2.7
	caudium_1_4_5:1.20.2.2
	caudium_1_4_4:1.20.2.2
	caudium_1_4_3:1.20.2.1
	caudium_1_4_2:1.20.2.1
	caudium_1_5_1:1.21
	caudium_1_4_1:1.20.2.1
	stable_1_4:1.20.0.2
	caudium_1_3_33:1.20
	caudium_1_3_32:1.20
	caudium_1_3_31:1.19
	caudium_1_3_30:1.19
	caudium_1_3_29:1.19
	caudium_1_2_33:1.11.2.7
	caudium_1_2_32:1.11.2.7
	caudium_1_3_23:1.16
	caudium_1_3_22:1.16
	caudium_1_3_21:1.13
	caudium_1_3_20:1.13
	caudium_1_3_19:1.12
	caudium_1_3_18:1.12
	caudium_1_2_31:1.11.2.6
	caudium_1_2_30:1.11.2.6
	caudium_1_2_29:1.11.2.4
	caudium_1_2_28:1.11.2.4
	caudium_1_3_17:1.12
	caudium_1_3_16:1.12
	caudium_1_2_27:1.11.2.3
	caudium_1_2_26:1.11.2.3
	caudium_1_2_25:1.11.2.3
	caudium_1_2_24:1.11.2.3
	caudium_1_0_57:1.6
	caudium_1_0_56:1.6
	caudium_1_3_15:1.12
	caudium_1_3_14:1.12
	caudium_1_2_23:1.11.2.2
	caudium_1_2_22:1.11.2.2
	caudium_1_2_21:1.11.2.2
	caudium_1_2_20:1.11.2.2
	caudium_1_0_55:1.6
	caudium_1_0_54:1.6
	caudium_1_3_13:1.12
	caudium_1_3_12:1.12
	caudium_1_3_11:1.12
	caudium_1_3_10:1.12
	caudium_1_2_19:1.11.2.2
	caudium_1_2_18:1.11.2.2
	caudium_1_3_9:1.12
	caudium_1_3_8:1.12
	caudium_1_3_7:1.12
	caudium_1_3_6:1.12
	caudium_1_2_17:1.11.2.2
	caudium_1_2_16:1.11.2.2
	caudium_1_2_15:1.11.2.2
	caudium_1_2_14:1.11.2.2
	caudium_1_2_12:1.11.2.2
	caudium_1_2_10:1.11.2.2
	caudium_1_3_5:1.12
	caudium_1_3_4:1.12
	caudium_1_2_9:1.11.2.2
	caudium_1_2_8:1.11.2.2
	caudium_1_3_3:1.12
	caudium_1_2_7:1.11.2.2
	caudium_1_2_6:1.11.2.2
	caudium_1_0_53:1.6
	caudium_1_0_52:1.6
	caudium_1_0_51:1.6
	caudium_1_0_50:1.6
	caudium_1_0_45:1.6
	caudium_1_0_44:1.6
	caudium_1_0_43:1.6
	caudium_1_0_42:1.6
	Caudium_1_3_2:1.12
	caudium_1_2_5:1.11.2.2
	caudium_1_2_4:1.11.2.2
	caudium_1_0_41:1.6
	caudium_1_0_40:1.6
	caudium_1_0_39:1.6
	Caudium_1_0_38:1.6
	caudium_1_2_3:1.11.2.1
	caudium_1_2_2:1.11.2.1
	caudium_1_3_1:1.11
	caudium_1_2_1:1.11
	stable_1_2:1.11.0.2
	caudium_1_0_37:1.6
	caudium_1_0_36:1.6
	caudium_1_1_5:1.8
	caudium_1_1_4:1.8
	caudium_1_1_3:1.8
	caudium_1_1_2:1.8
	caudium_1_0_34:1.6
	caudium_1_0_32:1.6
	caudium_1_0_30:1.6
	caudium_1_0_28:1.6
	caudium_1_0_24:1.6
	caudium_1_0_22:1.6
	caudium_1_0_20:1.6
	caudium_1_0_18:1.6
	caudium_1_0_17:1.6
	caudium_1_0_16:1.6
	caudium_1_0_15:1.6
	caudium_1_0_14:1.6
	caudium_1_0_13:1.6
	caudium_1_0_12:1.6
	caudium_1_0_11:1.6
	caudium_1_0_10:1.6
	stable_1_0:1.6.0.2
	caudium_1_0_9:1.4
	caudium_1_0_8:1.4
	caudium_1_0_7:1.4
	caudium_1_0_6:1.4
	caudium_1_0_5:1.4
	caudium_1_0_4:1.4
	caudium_1_0_3:1.4
	caudium_1_0_2:1.4
	start:1.1.1.1
	Roxen:1.1.1;
locks; strict;
comment	@# @;


1.23
date	2007.12.16.20.09.06;	author hww3;	state Exp;
branches;
next	1.22;

1.22
date	2007.12.16.17.36.36;	author hww3;	state Exp;
branches;
next	1.21;

1.21
date	2004.09.14.08.08.59;	author kiwi;	state Exp;
branches;
next	1.20;

1.20
date	2004.05.17.14.36.23;	author kiwi;	state Exp;
branches
	1.20.2.1;
next	1.19;

1.19
date	2004.02.24.17.59.06;	author kiwi;	state Exp;
branches;
next	1.18;

1.18
date	2004.02.19.09.51.16;	author vida;	state Exp;
branches;
next	1.17;

1.17
date	2003.11.30.16.21.19;	author kiwi;	state Exp;
branches;
next	1.16;

1.16
date	2003.11.30.13.10.22;	author kiwi;	state Exp;
branches;
next	1.15;

1.15
date	2003.09.28.17.16.03;	author kiwi;	state Exp;
branches;
next	1.14;

1.14
date	2003.09.28.16.53.53;	author kiwi;	state Exp;
branches;
next	1.13;

1.13
date	2003.09.28.16.45.01;	author kiwi;	state Exp;
branches;
next	1.12;

1.12
date	2002.01.29.21.17.03;	author kiwi;	state Exp;
branches;
next	1.11;

1.11
date	2002.01.07.15.20.06;	author grendel;	state Exp;
branches
	1.11.2.1;
next	1.10;

1.10
date	2002.01.07.13.29.43;	author kiwi;	state Exp;
branches;
next	1.9;

1.9
date	2002.01.03.14.38.39;	author kiwi;	state Exp;
branches;
next	1.8;

1.8
date	2001.01.23.07.40.48;	author wilsonm;	state Exp;
branches;
next	1.7;

1.7
date	2000.12.13.06.57.40;	author neotron;	state Exp;
branches;
next	1.6;

1.6
date	2000.12.11.03.47.51;	author neotron;	state Exp;
branches;
next	1.5;

1.5
date	2000.12.11.03.47.19;	author neotron;	state Exp;
branches;
next	1.4;

1.4
date	2000.08.07.01.45.07;	author neotron;	state Exp;
branches;
next	1.3;

1.3
date	2000.08.06.11.03.24;	author kvoigt;	state Exp;
branches;
next	1.2;

1.2
date	2000.07.28.16.58.09;	author neotron;	state Exp;
branches;
next	1.1;

1.1
date	2000.07.28.16.31.07;	author neotron;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	2000.07.28.16.31.07;	author neotron;	state Exp;
branches;
next	;

1.11.2.1
date	2002.01.29.16.43.25;	author kiwi;	state Exp;
branches;
next	1.11.2.2;

1.11.2.2
date	2002.01.29.21.17.44;	author kiwi;	state Exp;
branches;
next	1.11.2.3;

1.11.2.3
date	2003.03.02.18.38.41;	author kiwi;	state Exp;
branches;
next	1.11.2.4;

1.11.2.4
date	2003.06.23.18.30.38;	author kiwi;	state Exp;
branches;
next	1.11.2.5;

1.11.2.5
date	2003.06.23.19.06.48;	author kiwi;	state Exp;
branches;
next	1.11.2.6;

1.11.2.6
date	2003.06.23.19.16.32;	author kiwi;	state Exp;
branches;
next	1.11.2.7;

1.11.2.7
date	2004.01.27.13.12.48;	author kiwi;	state Exp;
branches;
next	;

1.20.2.1
date	2004.09.14.08.17.55;	author kiwi;	state Exp;
branches;
next	1.20.2.2;

1.20.2.2
date	2004.10.28.13.15.26;	author kiwi;	state Exp;
branches;
next	1.20.2.3;

1.20.2.3
date	2005.06.29.13.54.49;	author kiwi;	state Exp;
branches;
next	1.20.2.4;

1.20.2.4
date	2007.12.16.17.35.55;	author hww3;	state Exp;
branches;
next	1.20.2.5;

1.20.2.5
date	2007.12.16.20.08.36;	author hww3;	state Exp;
branches;
next	;


desc
@@


1.23
log
@notes
@
text
@Before Installing:

There are a few required packages for installing Caudium.  Most are included
with your distribution.  The configure script should alert you to anything
that is missing, but here is a list of packages that you will most likely
have to install yourself.

NOTE: If you're upgrading from a previous version of Caudium, please read 
the README file, which contains a list of suggestions for ensuring a 
smooth and successful upgrade process.

Required Packages:
  Pike 7.6:
    You will need version 7.6.112 or newer. Caudium 1.4 will not be
    able to run with older pike (eg pike 7.5, 7.2, 7.1, 7.0, 7.4 or 0.6).

    NOTE: some users have reported difficulty using the Mysql support 
    included with versions of Pike between 7.6.66 and 7.6.112. A fix for 
    this bug has been submitted to the Pike team and should be available 
    with releases of Pike after 7.6.112.

    You may apply the change directly to your existing Pike 7.6.112  
    source directory; download the latest version of mysql.c from the Pike 
    website:

    http://pike.ida.liu.se/cvs/Pike/7.6/src/modules/Mysql/mysql.c?1.93

Optional Packages (recommended)
  Sablotron (requires expat)
    In order to use the XSLT parser you will need to get the Sablotron
    XSLT parser package.  This is highly recommended.  As of version 0.50,
    you will need to install the expat libraries.  You can get these two
    packages from:

      Expat:
       http://sourceforge.net/projects/expat/ 
      Sablotron:
        http://www.gingerall.com/

  MySQL or other SQL packages
    If you want to use an SQL database backend with Caudium, then you need
    to have it installed BEFORE building Pike.  You can get MySQL from
    http://www.mysql.com/

  PHP
    See http://caudium.net/server/docs/related/php4.rxml

Tuning Notes
++++++++++++

Caudium is designed to operate with a minimum of dedicated resources. 
However, as a non-forking webserver, there are some special considerations 
you should keep in mind when deploying Caudium. 

1. Most operating systems have a default limit of 256 file 
descriptors per process. This low limit most commonly results in a "No 
more file descriptors" error. This usually happens when you have many 
virtual servers or experience a spike in traffic. Setting this value to 
2048 or more usually provides better results.

Unfortunately, every operating system has different limits and means for 
altering these limits. On many modern operating systems, the system wide 
limit is set sufficiently high that you can use the "ulimit" command 
before starting Caudium to increase these limits. 

Some useful links are provided below that may provide additional insight 
into the file descriptor limit situation for your particular OS:

Solaris: http://www.unixguide.net/sun/faq/3.48.shtml
MacOS X: http://www.amug.org/~glguerin/howto/More-open-files.html
Linux: http://bloggerdigest.blogspot.com/2006/10/file-descriptors-vs-linux-performance.html
FreeBSD: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-kernel-limits.html

----------------------------------------------------------------------------

Installing Caudium 1.4 from source:
+++++++++++++++++++++++++++++++++++

  1. Get the source server package.

  2. Issue the command to unpack the archive:

          .tar.gz:
               If you have GNU tar; "tar xzf Caudium-archive-name"
               If you don't have GNU tar: 
               "gunzip < Caudium-archive-name| tar xf -" 
          .tar.Z
               If you have GNU tar; "tar xzf Caudium-archive-name"
               If you don't have GNU tar: 
               "uncompress < Caudium-archive-name| tar xf -"
          .tar
               "tar xf Caudium-archive-name"

     (where "Caudium-archive-name" is the name of the Caudium archive
     file.).

  3. Type "cd <caudium_version>" to change to the new directory. This
     directory should contain at the very least four directories:
     server (Caudium server source), src (extra pike modules), extern
     (misc. programs used by Caudium) and tools (misc tools). See README
     for more information about the directory structure.

     (Where caudium_version is the name of the unarchived Caudium directory.)

 4.  Type ./configure --prefix=<wanted_base_path_for_caudium>
     (prefix is optional and defaults to /usr/local, thus placing Caudium in
     /usr/local/caudium/) followed by make and make install to build
     the binaries and copy them to the correct place.

!!!  By default, the configuration will fail if the Sablotron XSLT
!!!  library isn't found. If you are not interested in XSLT
!!!  functionality, just add the flag '--without-PiXSL' to the
!!!  configure script.

     You can later on move the 'caudium' directory that will be
     created when you type 'make install' to anywhere in your
     filesystem. Caudium does not keep any absolute paths.
     
  5. If everything worked fine and the compilation is done, type 
     cd <dir>/server.

     (Where <dir> is <wanted_base_path_for_caudium>/caudium if you used 4.)

  6. Start the install script by typing ./install. (skip this step if 
     you're upgrading from a previous version of Caudium).

  7. Answer the simple questions and wait for your client.

  9. If everything worked, configure the server, otherwise move on to the
     troubleshooting section on the Caudium WWW-pages. 

 10. In order to start your server in the future (from startup scripts, etc)
     cd to <dir>/server and run ./start-caudium. It often makes sense to 
     run this command with the --once option, so that you can see the 
     results of the startup on your terminal, making any troubleshooting 
     much simpler. Once everything is verified to be working, you can shut 
     down and restart without the --once option.

 Once you have installed the server, consider joining the Caudium
 mailing list by subscribing on the following URL :

   http://lists.oav.net/wws/subrequest/caudium-general

 For more information about Caudium, read the online documentation at
 http://caudium.net/

----------------------------------------------------------------------------
Example installation session:

bash$ tar xzf caudium-1.4.6.tar.gz
bash$ cd caudium-1.4.6
bash$ ../configure --prefix=/usr/www

<various checks...>

bash$ make 

<compilations>

bash$ make  install
bash$ cd /usr/www/caudium/server
bash$ ./install

<answer a few questions>

@


1.22
log
@upgrade notes and some enhancements to the documentation.
@
text
@d48 26
@


1.21
log
@Caudium 1.4 branch is ready.
@
text
@d8 4
d14 1
a14 1
    You will need version 7.6.7 or better. Caudium 1.4 will not be
d17 11
d98 2
a99 1
  6. Start the install script by typing ./install.
d107 5
a111 1
     cd to <dir>/server and run ./start-caudium.
d116 1
a116 1
   http://listes.oav.net/wws/subrequest/caudium-general
d124 2
a125 2
bash$ tar xzf caudium-1.4.1.tar.gz
bash$ cd caudium-1.3.1
@


1.20
log
@1.3.31
@
text
@d10 2
a11 2
    You will need version 7.6.7 or better. Caudium 1.3 will not be
    able to run with older pike (eg pike 7.5 7.2, 7.1, 7.0, 7.4 or 0.6).
d35 1
a35 1
Installing Caudium 1.3 from source:
d104 2
a105 2
bash$ tar xzf caudium-1.3.31.tar.gz
bash$ cd caudium-1.3.31
@


1.20.2.1
log
@Starting the 1.4 branch
@
text
@d10 2
a11 2
    You will need version 7.6.7 or better. Caudium 1.4 will not be
    able to run with older pike (eg pike 7.5, 7.2, 7.1, 7.0, 7.4 or 0.6).
d35 1
a35 1
Installing Caudium 1.4 from source:
d104 2
a105 2
bash$ tar xzf caudium-1.4.1.tar.gz
bash$ cd caudium-1.4.1
@


1.20.2.2
log
@RC2 is comming RSN...
@
text
@d104 2
a105 2
bash$ tar xzf caudium-1.4.4.tar.gz
bash$ cd caudium-1.4.4
@


1.20.2.3
log
@Caudium 1.4 RELEASE
@
text
@d104 2
a105 2
bash$ tar xzf caudium-1.4.6.tar.gz
bash$ cd caudium-1.4.6
@


1.20.2.4
log
@notes for installing and upgrading, etc.
@
text
@a7 4
NOTE: If you're upgrading from a previous version of Caudium, please read 
the README file, which contains a list of suggestions for ensuring a 
smooth and successful upgrade process.

d10 1
a10 1
    You will need version 7.6.112 or newer. Caudium 1.4 will not be
a12 11
    NOTE: some users have reported difficulty using the Mysql support 
    included with versions of Pike between 7.6.66 and 7.6.112. A fix for 
    this bug has been submitted to the Pike team and should be available 
    with releases of Pike after 7.6.112.

    You may apply the change directly to your existing Pike 7.6.112  
    source directory; download the latest version of mysql.c from the Pike 
    website:

    http://pike.ida.liu.se/cvs/Pike/7.6/src/modules/Mysql/mysql.c?1.93

d83 1
a83 2
  6. Start the install script by typing ./install. (skip this step if 
     you're upgrading from a previous version of Caudium).
d91 1
a91 5
     cd to <dir>/server and run ./start-caudium. It often makes sense to 
     run this command with the --once option, so that you can see the 
     results of the startup on your terminal, making any troubleshooting 
     much simpler. Once everything is verified to be working, you can shut 
     down and restart without the --once option.
d96 1
a96 1
   http://lists.oav.net/wws/subrequest/caudium-general
@


1.20.2.5
log
@some fd tuning notes
@
text
@a47 26
Tuning Notes
++++++++++++

Caudium is designed to operate with a minimum of dedicated resources. 
However, as a non-forking webserver, there are some special considerations 
you should keep in mind when deploying Caudium. 

1. Most operating systems have a default limit of 256 file 
descriptors per process. This low limit most commonly results in a "No 
more file descriptors" error. This usually happens when you have many 
virtual servers or experience a spike in traffic. Setting this value to 
2048 or more usually provides better results.

Unfortunately, every operating system has different limits and means for 
altering these limits. On many modern operating systems, the system wide 
limit is set sufficiently high that you can use the "ulimit" command 
before starting Caudium to increase these limits. 

Some useful links are provided below that may provide additional insight 
into the file descriptor limit situation for your particular OS:

Solaris: http://www.unixguide.net/sun/faq/3.48.shtml
MacOS X: http://www.amug.org/~glguerin/howto/More-open-files.html
Linux: http://bloggerdigest.blogspot.com/2006/10/file-descriptors-vs-linux-performance.html
FreeBSD: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-kernel-limits.html

@


1.19
log
@GNU Make is not more required now.
@
text
@d9 3
a11 3
  Pike 7.5:
    You will need version 7.5 or better. Caudium 1.3 will not be
    able to run with older pike (eg pike 7.2, 7.1, 7.0, 7.4 or 0.6).
a32 8
  NJS JavaScript Interpreter - HIGHLY EXPERIMENTAL!!!
    If you want to use server side Javascript support, you'll need to install
    it. You need to install NJS library before compiling Caudium. See 
    http://www.bbassett.net/njs/ for more informations. You also need to
    enable the support explicitly by modifying the src/cmods/configure.in
    file. Also, note that you need the latest CVS version of NJS for this
    module to work.

d104 2
a105 2
bash$ tar xzf caudium-1.3.23.tar.gz
bash$ cd caudium-1.3.23
@


1.18
log
@Fixes on the installation notes regarding PHP and Pike version
Added GNU make as a requirement.
@
text
@a12 3
  GNU Make: 
    Users of *BSD and Solaris need to use GNU make in order to build Caudium.

@


1.17
log
@Caudium 1.3.21... Allmost pre-RC
@
text
@d9 6
a14 3
  Pike 7.4:
    You will need version 7.4.25 or better. Caudium 1.3 will not be
    able to run with older pike (eg pike 7.2, 7.1, 7.0 or 0.6).
d34 1
a34 4
    If you want to use Caudium's PHP4 support, you'll need to install it.
    You do not need to install before caudium, but you will need to restart
    the server if you install later.  You can use PHP3, but only through
    the CGI interface.
@


1.16
log
@The ./start script is now called ./start-caudium
@
text
@d115 2
a116 2
bash$ tar xzf caudium-1.3.21.tar.gz
bash$ cd caudium-1.3.21
@


1.15
log
@Fixlet
@
text
@d102 1
a102 1
     cd to <dir>/server and run ./start.
@


1.14
log
@Now we are ready to make cleanness.
@
text
@d10 1
a10 1
    You will need version 7.2.25 or better. Caudium 1.3 will not be
@


1.13
log
@Some cosmetics before big dust cleaning process is started.
@
text
@d115 2
a116 2
bash$ tar xzf caudium-1.3.19.tar.gz
bash$ cd caudium-1.3.19
@


1.12
log
@Update Installation instructions.
@
text
@d9 3
a11 3
  Pike 7.2:
    You will need version 7.2.197 or better. Caudium 1.3 will not be
    able to run with older pike (eg pike 7.0 or 0.6).
d105 1
a105 1
 mailing list by sending a mail to:
d107 1
a107 3
    caudium-general-request@@lists.sourceforge.net

 with Subject: subscribe
d115 2
a116 2
bash$ tar xzf caudium-1.3.1.tar.gz
bash$ cd caudium-1.3.1
@


1.11
log
@some docs changes
@
text
@d9 3
a11 6
  Pike 7.0:
    You will need version 7.0.268 or better.  Do not use the official
    7.0.78 available from pike.roxen.com, as it has bugs that affect
    Caudium's stability and performance.  Grab a CVS snapshot of Pike
    from http://caudium.net/download/snapshot.html until a newer
    version is officially released.
d46 1
a46 1
Installing Caudium 1.2 from source:
d117 2
a118 2
bash$ tar xzf caudium-1.0.10.tar.gz
bash$ cd caudium-1.0.10
@


1.11.2.1
log
@Updated docs.
@
text
@d9 1
a9 1
  Pike 7.0 or 7.2:
a14 2
    However, we recommend pike 7.2 with Caudium 1.2 especialy because
    the next Caudium branch will require it...
@


1.11.2.2
log
@Cosmetics changes.
@
text
@d122 2
a123 2
bash$ tar xzf caudium-1.2.2.tar.gz
bash$ cd caudium-1.2.2
@


1.11.2.3
log
@Fixes.
@
text
@d112 1
a112 1
    general-request@@caudium.info
d122 2
a123 2
bash$ tar xzf caudium-1.2.24.tar.gz
bash$ cd caudium-1.2.24
@


1.11.2.4
log
@Preparing for Caudium 1.2.28
@
text
@d122 2
a123 2
bash$ tar xzf caudium-1.2.28.tar.gz
bash$ cd caudium-1.2.28
@


1.11.2.5
log
@Version updates
@
text
@d122 2
a123 2
bash$ tar xzf caudium-1.2.29.tar.gz
bash$ cd caudium-1.2.29
@


1.11.2.6
log
@Groumpf... Version not released...
@
text
@d122 2
a123 2
bash$ tar xzf caudium-1.2.30.tar.gz
bash$ cd caudium-1.2.30
@


1.11.2.7
log
@Preparing for a release
@
text
@d112 1
a112 1
    caudium-general-request@@caudium.net
@


1.10
log
@Updating doc information about NJS supports.
@
text
@d39 1
a39 1
  NJS JavaScript Interpreter
d42 4
a45 1
    http://www.bbassett.net/njs/ for more informations.
@


1.9
log
@Trunking to 1.2 branch
@
text
@d39 5
@


1.8
log
@Added required/optional packages and descriptions.
Fixed example install
Added note about starting server from startup scripts (./start)
@
text
@d41 1
a41 1
Installing Caudium 1.1 from source:
@


1.7
log
@Some 1.0 -> 1.1 changes.
@
text
@d1 42
a42 2
          Installing Caudium 1.1 from source:
          +++++++++++++++++++++++++++++++++++
d87 1
a87 1
     (Where <wanted_base_path_for_caudium>/caudium if you used 4.)
d96 3
d100 5
a104 3
 mailinglist (by sending a mail to
 caudium-general-request@@lists.sourceforge.net, with Subject:
 subscribe).
a113 2
bash$ mkdir build
bash$ cd build
a126 2


@


1.6
log
@Fixed mlist info
@
text
@d1 1
a1 1
          Installing Caudium 1.0 from source:
@


1.5
log
@Clarified installation instructions some
@
text
@d57 3
a59 2
 mailinglist (by sending a mail to caudium-request@@caudium.net, with
 Subject: subscribe).
@


1.4
log
@updated INSTALLING
@
text
@d35 5
d66 4
a69 4
bash$ tar xzf caudium-1.0.tar.gz
bash$ cd caudium-1.0
bash$ mkdir solaris
bash$ cd solaris
d81 1
@


1.3
log
@Changed references from "caudium.com" to "caudium.net"
@
text
@d24 1
a24 1
     server (Caudium server source), pike (the Pike intepreter), extern
d30 4
a33 9
 4a. Type "make install" to install Caudium in /usr/local/caudium.

 4b. (This is an alternative method if you want to install Caudium somewhere
      else than /usr/local/caudium, or if method 4a fails.)

     Type ./configure --prefix=<wanted_base_path_for_caudium>
     (defaults to /usr/local, thus placing Caudium in /usr/local/caudium/)
     followed by make and make install to build the binaries and copy them 
     to the correct place.
d42 1
a42 2
     (Where <dir> is /usr/local/caudium following 4a, or
      <wanted_base_path_for_caudium>/caudium if you used 4b.)
d49 1
a49 1
     troubleshooting section on the caudium WWW-pages. 
d56 1
a56 1
 http://www.caudium.net/
d59 1
a59 1
Example installation session using the 4b route:
d67 1
a67 1
<Lots and lots of checks...>
d69 1
a69 1
bash$ make install
d71 1
a71 1
<Lots and lots of compilations>
d73 2
a74 1
bash$ cd /usr/www/caudiu/server
@


1.2
log
@some changes roxen->caudium as well as a file with some history
@
text
@d58 1
a58 1
 mailinglist (by sending a mail to caudium-request@@caudium.com, with
d62 1
a62 1
 http://www.caudium.com/
@


1.1
log
@Initial revision
@
text
@d1 2
a2 2
          Installing Roxen Challenger 1.3 - the Source distribution
          +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
d9 1
a9 1
               If you have GNU tar; "tar xzf Roxen-archive-name"
d11 1
a11 1
               "gunzip < Roxen-archive-name| tar xf -" 
d13 1
a13 1
               If you have GNU tar; "tar xzf Roxen-archive-name"
d15 1
a15 1
               "uncompress < Roxen-archive-name| tar xf -"
d17 1
a17 1
               "tar xf Roxen-archive-name"
d19 1
a19 1
     (where "Roxen-archive-name" is the name of the Roxen archive
d22 1
a22 1
  3. Type "cd <roxen_version>" to change to the new directory. This
d24 2
a25 2
     server (Roxen server source), pike (the Pike intepreter), extern
     (misc. programs used by Roxen) and tools (misc tools). See README
d28 1
a28 1
     (Where roxen_version is the name of the unarchived Roxen directory.)
d30 1
a30 1
 4a. Type "make install" to install Roxen Challenger in /usr/local/roxen.
d32 2
a33 2
 4b. (This is an alternative method if you want to install Roxen somewhere
      else than /usr/local/roxen, or if method 4a fails.)
d35 2
a36 2
     Type ./configure --prefix=<wanted_base_path_for_roxen>
     (defaults to /usr/local, thus placing Roxen in /usr/local/roxen/)
d40 1
a40 1
     You can later on move the 'roxen' directory that will be
d42 1
a42 1
     filesystem. Roxen does not keep any absolute paths.
d47 2
a48 2
     (Where <dir> is /usr/local/roxen following 4a, or
      <wanted_base_path_for_roxen>/roxen if you used 4b.)
d55 1
a55 1
     troubleshooting section on the roxen WWW-pages. 
d57 2
a58 2
 Once you have installed the server, consider joining the Roxen
 mailinglist (by sending a mail to roxen-request@@roxen.com, with
d61 2
a62 2
 For more information about Roxen, read the online documentation at
 http://www.roxen.com/
d67 2
a68 2
bash$ tar xzf roxen_1.3.tar.gz
bash$ cd roxen_1.3
d79 1
a79 1
bash$ cd /usr/www/roxen/server
@


1.1.1.1
log
@Roxen 1.3 imported
@
text
@@
