From 79036ec190dcebdd2071083bfd783f579670f3da Mon Sep 17 00:00:00 2001 From: Bradley Nicholes Date: Fri, 9 May 2003 17:40:44 +0000 Subject: [PATCH] Updated the NetWare platform documentation to reflect changes to the NetWare OS environment and build process. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@99745 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/platform/netware.xml | 262 +++++++++++++------------------ 1 file changed, 106 insertions(+), 156 deletions(-) diff --git a/docs/manual/platform/netware.xml b/docs/manual/platform/netware.xml index 1e641f04ce..5cba65263a 100644 --- a/docs/manual/platform/netware.xml +++ b/docs/manual/platform/netware.xml @@ -10,7 +10,7 @@

This document explains how to install, configure and run - Apache 2.0 under Novell NetWare 5.1 and above. If you find any bugs, + Apache 2.0 under Novell NetWare 6.0 and above. If you find any bugs, or wish to contribute in other ways, please use our bug reporting page.

@@ -36,17 +36,21 @@ Requirements -

Apache 2.0 is designed to run on NetWare 5.1 and above.

- -

If running on NetWare 5.1 you must install Service - Pack 4 or above.

- -

If running on NetWare 6 you must install Service - Pack 1 or above.

+

Apache 2.0 is designed to run on NetWare 6.0 service pack 3 + and above. If you are running a service pack less + than SP3, you must install the latest + NetWare Libraries + for C (LibC).

NetWare service packs are available here.

+

Apache 2.0 for NetWare can also be run in a NetWare 5.1 environment + as long as the latest service pack or the latest version + of the NetWare Libraries + for C (LibC) has been installed . WARNING: Apache 2.0 + for NetWare has not been targeted for or tested in this environment.

+
@@ -58,7 +62,9 @@ href="http://www.apache.org/">http://www.apache.org/. This will list the current release, any more recent alpha or beta-test releases, together with details of mirror web and - anonymous ftp sites.

+ anonymous ftp sites. Binary builds of the latest releases of + Apache 2.0 for NetWare can be downloaded from + here.

@@ -66,10 +72,9 @@ Installing Apache for NetWare -

There is no Apache install program for NetWare currently. You - will need to compile apache and copy the files over to the - server manually. An install program will be posted at a later - date.

+

There is no Apache install program for NetWare currently. If you + are building Apache 2.0 for NetWare from source, you will need to + copy the files over to the server manually.

Follow these steps to install Apache on NetWare from the binary download (assuming you will install to @@ -81,8 +86,8 @@

  • Edit the httpd.conf file setting ServerRoot and ServerName to reflect your correct server - settings
    • + module="core">ServerName along with any file path values + to reflect your correct server settings
  • Add SYS:/APACHE2 to the search path, for example: SEARCH ADD SYS:\APACHE2 @@ -92,16 +97,22 @@

    Follow these steps to install Apache on NetWare manually from your own build source (assuming you will install to - sys:/apache):

    + sys:/apache2):

    • Create a directory called Apache2 on a NetWare volume
      • -
    • Copy APACHE2.NLM, APRLIB.NLM, - HTDIGEST.NLM, HTPASSWD.NLM +
    • Copy APACHE2.NLM, APRLIB.NLM to SYS:/APACHE2
      • +
    • Create a directory under SYS:/APACHE2 + called BIN
      • + +
    • Copy HTDIGEST.NLM, HTPASSWD.NLM, + HTDBM.NLM, LOGRES.NLM, ROTLOGS.NLM + to SYS:/APACHE2/BIN
      • +
    • Create a directory under SYS:/APACHE2 called CONF
      • @@ -109,8 +120,8 @@ SYS:/APACHE2/CONF directory and rename to HTTPD.CONF -
    • Copy the MIME.TYPES and MAGIC - files to SYS:/APACHE2/CONF directory
      • +
    • Copy the MIME.TYPES, CHARSET.CONV and + MAGIC files to SYS:/APACHE2/CONF directory
    • Copy all files and subdirectories in \HTTPD-2.0\DOCS\ICONS to SYS:/APACHE2/ICONS
      • @@ -144,6 +155,12 @@

      Apache may be installed to other volumes besides the default SYS volume.

      +

      During the build process, adding the keyword "install" to the makefile command line + will automatically produce a complete distribution package under the subdirectory + DIST. Install Apache by simply copying the distribution that was produced + by the makfiles to the root of a NetWare volume (see: Compiling Apache for + NetWare below).

      +
      @@ -159,7 +176,7 @@ load address space = apache2 apache2 -

      This will load Apache into an address space called apache. +

      This will load Apache into an address space called apache2. Running multiple instances of Apache concurrently on NetWare is possible by loading each instance into its own protected address space.

      @@ -242,8 +259,8 @@

      Apache 2.0 for NetWare includes a set of command line directives that can be used to modify or display information about the running instance of the - web server. Each of these directives must be preceded by the keyword - APACHE2:

      + web server. These directives are only available while Apache is running. Each + of these directives must be preceded by the keyword APACHE2.

      RESTART
      @@ -264,23 +281,31 @@
      SETTINGS
      Enables or disables the thread status display - on the console. When enabled, a status of the number of running threads - is displayed along with their status.
      + on the console. When enabled, the state of each running threads is displayed + on the Apache console screen.
      SHUTDOWN
      Terminates the running instance of the Apache web server.
      + +
      HELP
      +
      Describes each of the runtime directives.
      +

      By default these directives are issued against the instance of Apache running + in the OS address space. To issue a directive against a specific instance running + in a protected address space, include the -p parameter along with the name of the + address space. For more information type "apache2 Help" on the command line.

      +
      Configuring Apache for NetWare -

      Apache is configured by files in the conf - directory. These are the same as files used to configure the - Unix version, but there are a few different directives for +

      Apache is configured by reading configuration files usually stored + in the conf directory. These are the same as files used + to configure the Unix version, but there are a few different directives for Apache on NetWare. See the Apache documentation for all the available directives.

      @@ -289,11 +314,11 @@

      • Because Apache for NetWare is multithreaded, it does not - use a separate process for each request, as Apache does in some Unix + use a separate process for each request, as Apache does on some Unix implementations. Instead there are only threads running: a parent - thread, and a multiple child threads which handle the requests.

        + thread, and multiple child or worker threads which handle the requests.

        -

        So the "process"-management directives are different:

        +

        Therefore the "process"-management directives are different:

        MaxRequestsPerChild - Like the Unix directive, this controls how many requests @@ -327,12 +352,12 @@

      • -

        The directives that accept filenames as arguments now - must use NetWare filenames instead of Unix ones. However, - because Apache uses Unix-style names internally, you must - use forward slashes, not backslashes. It is recommended that all rooted - file paths begin with a volume name. If omitted, Apache will - assume the SYS: volume.

        +

        The directives that accept filenames as arguments must use + NetWare filenames instead of Unix names. However, because Apache + uses Unix-style names internally, forward slashes must be used + rather than backslashes. It is recommended that all rooted file paths + begin with a volume name. If omitted, Apache will assume the + SYS: volume which may not be correct.

      • @@ -343,8 +368,7 @@ To activate these, or other modules, the LoadModule directive must be used. For example, to active the status module, use - the following (in addition to the status-activating - directives in access.conf):

        + the following:

        LoadModule status_module modules/status.nlm @@ -381,17 +405,18 @@ Compiling Apache for NetWare -

        Compiling Apache requires MetroWerks CodeWarrior 6.x or higher to - be properly installed. Once Apache has been built, it needs to be - installed on a NetWare volume's root directory. The default is the - sys:/Apache2 directory.

        +

        Compiling Apache requires MetroWerks CodeWarrior 6.x or higher. Once + Apache has been built, it can be installed to the root of any NetWare + volume. The default is the sys:/Apache2 directory.

        Before running the server you must fill out the conf directory. Copy the file HTTPD-STD.CONF from the distribution conf directory and rename it to HTTPD.CONF. Edit the HTTPD.CONF file searching for all @@Value@@ markers and replacing them with the appropriate setting. Copy over - the conf/magic and conf/mime.types files as well.

        + the conf/magic and conf/mime.types files as well. + Alternatively, a complete distribution can be built by including the keyword + install when invoking the makefiles.

        @@ -408,11 +433,12 @@
      • NetWare Libraries for C (LibC)
        • -
      • WinSock 2 - Developer Components for NetWare
        • +
      • LDAP Libraries + for C
        • -
      • To build using either the project file or the make files, requires an - AWK utility (awk, gawk or similar). AWK can be downloaded from +
      • ZLIB Compression Library source code
        • + +
      • AWK utility (awk, gawk or similar). AWK can be downloaded from http://developer.novell.com/ndk/apache.htm. The utility must be found in your windows path and must be named awk.exe.
        • @@ -422,93 +448,6 @@
        -
        - - Building Apache using the Metrowerks Project Files: - -

        All major pieces of Apache and APR are built using the - ApacheNW.mcp and LibAprNW.mcp project files. - This includes modules such as status, info, proxy, etc.

        - -
          -
        • Set the environment variable NovellLibC to the - location of the NetWare Libraries for C SDK, for example: - Set NovellLibC=c:\novell\ndk\libc -
          • - -
        • Make sure that the path to the CodeWarrior command line tools - (MWCCNLM.exe, MWLDNLM.exe) has been - included in the system's PATH environment variable.
          • - -
        • Make sure that the path to the AWK utility has been included in the - system's PATH environment variable.
          • - -
        • Download the source code and unzip to an appropriate directory on - your workstation.
          • - -
        • Change directory to \httpd\srclib\apr\build and run the - batch file prebuildnw.bat. The batch file will setup the build - environment for building the APR libraries. It will also run 2 AWK scripts - that will generate the export files for APR.
          • - -
        • Change directory to \httpd\srclib\apr and extract the project - file LIBAPRNW.mcp from the LIBAPRNW.mcp.zip file.
          • - -
        • Open the LIBAPRNW.mcp project file in the Metrowerks IDE.
          • - -
        • Select the target "Build Util - Gen URL Delim" and build the target. - This target will produce the NLM GENURI.nlm
          • - -
        • Copy the file GENURI.nlm to the SYS: volume - of a NetWare server and run using the following command: -
            -
          • SYS:\genuri > sys:\uri_delims.h
            • -
          -
          • - -
        • Copy the file uri_delims.h to the directory - \httpd\srclib\apr-util\uri on the build machine.
          • - -
        • Select the target "APR Debug NLM" or "APR Release NLM" in the IDE and build. - This will produce the file APRLIB.nlm. -
            -
          • [Optional] Select any of the LIB targets to produce a - statically linkable libraries.
            • -
          -
          • - -
        • Change directory to \httpd\build and run the batch file - prebuildnw.bat. This batch file will setup the build environment - for building the APACHE.nlm. It will also run several AWK scripts - that will generate the export files for APACHE.
          • - -
        • Change directory to \http and extract the project file - ApacheNW.mcp from the ApacheNW.mcp.zip file.
          • - -
        • Open the ApacheNW.mcp project file in the Metrowerks IDE.
          • - -
        • Select the target "Build Utility - DFTables" and build the target.
          • - -
        • Select the target "Build Util - Gen Test Chars" and build the target.
          • - -
        • Copy the files GENCHARS.nlm and DFTABLES.nlm - to the SYS: volume of a NetWare server and run using the following commands: -
            -
          • SYS:\genchars > sys:\test_char.h
            • -
          • SYS:\dftables > sys:\chartables.c
            • -
          -
          • - -
        • Copy the files test_char.h and chartables.c - to the directory \httpd\os\netware on the build machine.
          • - -
        • Select the target "Apache Full Debug" or "Apache Full Release" in - the IDE and build. This will produce the file APACHE2.nlm - along with all of the external module NLMs.
          • -
        - -
        -
        Building Apache using the NetWare makefiles: @@ -526,11 +465,22 @@ If you installed to the default location C:\Program Files\Metrowerks\CodeWarrior, you don't need to set this.
        • +
      • Set the environment variable LDAPSDK to the + location where you installed the LDAP Libraries for C, for example: + Set LDAPSDK=c:\Novell\NDK\cldapsdk\NetWare\libc +
        • + +
      • Set the environment variable ZLIBSDK to the + location where you installed the source code for the ZLib Library, + for example: + Set ZLIBSDK=D:\NOVELL\zlib +
        • +
      • Set the environment variable AP_WORK to the full path of - the \httpd directory.
        • + the \httpd-2.0 directory.
      • Set the environment variable APR_WORK to the full path of - the \httpd\srclib\apr directory.
        • + the \httpd-2.0\srclib\apr directory.
      • Make sure that the path to the AWK utility and the GNU make utility (gmake.exe) have been included in the system's @@ -539,7 +489,7 @@
      • Download the source code and unzip to an appropriate directory on your workstation.
        • -
      • Change directory to \httpd\srclib\apr-util\uri and build +
      • Change directory to \httpd-2.0\srclib\apr-util\uri and build GENURI.nlm by running "gmake -f nwgnumakefile".
      • Copy the file GENURI.nlm to the SYS: volume @@ -548,15 +498,15 @@
      • Copy the file uri_delims.h to the directory - \httpd\srclib\apr-util\uri on the build machine.
        • + \httpd-2.0\srclib\apr-util\uri on the build machine. -
      • Change directory to \httpd\srclib\apr and build APR +
      • Change directory to \httpd-2.0\srclib\apr and build APR by running "gmake -f nwgnumakefile"
        • -
      • Change directory to \httpd\srclib\pcre and build +
      • Change directory to \httpd-2.0\srclib\pcre and build DFTABLES.nlm by running "gmake -f nwgnumakefile"
        • -
      • Change directory to \httpd\server and build +
      • Change directory to \httpd-2.0\server and build GENCHARS.nlm by running "gmake -f nwgnumakefile"
      • Copy the files GENCHARS.nlm and DFTABLES.nlm @@ -569,9 +519,9 @@
      • Copy the files test_char.h and chartables.c - to the directory \httpd\os\netware on the build machine.
        • + to the directory \httpd-2.0\os\netware on the build machine. -
      • Change directory to \httpd and build Apache by running +
      • Change directory to \httpd-2.0 and build Apache by running "gmake -f nwgnumakefile". You can create a distribution directory by adding an install parameter to the command, for example: gmake -f nwgnumakefile install @@ -585,26 +535,26 @@ Additional make options
          -
        • gmake -f nwgnumakefile
          Builds release versions of all of the - binaries and copies them to a \release destination directory.
          • +
        • gmake -f nwgnumakefile

          Builds release versions of all of the + binaries and copies them to a \release destination directory.

          • -
        • gmake -f nwgnumakefile DEBUG=1
          Builds debug versions of all of the - binaries and copies them to a \debug destination directory.
          • +
        • gmake -f nwgnumakefile DEBUG=1

          Builds debug versions of all of the + binaries and copies them to a \debug destination directory.

          • -
        • gmake -f nwgnumakefile install
          Creates a complete Apache +
        • gmake -f nwgnumakefile install

          Creates a complete Apache distribution with binaries, docs and additional support files in a - \dist\Apache2 directory.

          • + \dist\Apache2 directory.

          -
        • gmake -f nwgnumakefile installdev
          Same as install but also creates a +
        • gmake -f nwgnumakefile installdev

          Same as install but also creates a \lib and \include directory in the destination directory - and copies headers and import files.

          • + and copies headers and import files.

          -
        • gmake -f nwgnumakefile clean
          Cleans all object files and binaries +
        • gmake -f nwgnumakefile clean

          Cleans all object files and binaries from the \release or \debug build areas depending on whether - DEBUG has been defined.

          • + DEBUG has been defined.

          -
        • gmake -f nwgnumakefile clobber_all
          Same as clean and also deletes - the distribution directory if it exists.
          • +
        • gmake -f nwgnumakefile clobber_all

          Same as clean and also deletes + the distribution directory if it exists.