All of this is found on the MSDN site. And should be included in the TAR that is available for download.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservext/h tml/fpse02win.asp To download the UNIX version of the FrontPage Server Extensions 2002 Open your browser and navigate to the Microsoft FrontPage Server Extensions 2002 for UNIX download page. Click Download Now! Select the platform and language you want to download, and then click the download file name to begin the download. Features that are installed FrontPage Server Extensions 2002 are installed in /usr/local/frontpage by default. If you install them in another location, you must provide a link from /usr/local/frontpage to the installation area. (The installation script creates this link for you.) If you do not install FrontPage Server Extensions 2002 in /usr/local, the directory must still exist. The installation script creates this directory if it is not on your server. Along with FrontPage Server Extensions 2002, the following features are installed: The program owsadm.exe, a tool for administrating FrontPage Server Extensions 2002 and FrontPage-extended webs, in /usr/local/frontpage/version5.0/bin/owsadm.exe. The HTML Administration Forms, used to administer server extensions from any computer connected to the Internet that has access to the server, in /usr/local/frontpage/version5.0/admin/<LCID>. LCID is the locale ID; for example, 1033 for US English. The FrontPage Apache patch, which makes it possible to install a single copy of FrontPage Server Extensions 2002 without installing stub versions of the FrontPage Server Extensions 2002 executable files in each FrontPage-extended web. The FrontPage Apache patch binaries and source files are installed in /usr/local/frontpage/version5.0/apache-fp. Other server extensions files, such as message and configuration files. Using the Setup script The FrontPage Server Extensions 2002 installation on the UNIX platform consists of four steps (you might not perform all the steps): FrontPage Server Extensions 2002 and other files are uncompressed, untarred, and saved to their locations on the server computer. If your Web server has an earlier version of the server extensions, it is upgraded. If your Web server has never had the server extensions before, the extensions are installed. If you have one or more virtual servers, FrontPage Server Extensions 2002 are optionally installed on those servers. The FrontPage Server Extensions 2002 installation script is fp_install.sh. You must be logged on as "root" to run this script. To untar FrontPage Server Extensions 2002 Run fp_install.sh. When prompted, back up the installation directory, the server configuration file directory, and any content before installing FrontPage Server Extensions 2002. When prompted, enter a server extensions directory. By default, FrontPage Server Extensions 2002 are installed in /usr/local/frontpage/. You can accept the default location or specify another location. If you select another location, a symbolic link is created from /usr/local/frontpage/ to the directory you choose. The installation directory must be on a local partition, and the partition must not be mounted NOSUID. When prompted, untar and uncompress the FrontPage Server Extensions 2002 tar file, fp50.platform.tar.Z. If the tar file is not in the current directory, you are prompted for its location. Upgrading earlier versions After upgrading all servers to FrontPage Server Extensions 2002, you can set up the security of your FrontPage-extended webs interactively, or have fp_install.sh generate a script to perform the operation. If you choose the interactive option, fp_install.sh prompts you for the UNIX user name and group name of each root web and subweb that you have upgraded. For each FrontPage-extended web, fp_install.sh then performs the change ownership (chown) operation on the content in each Web to be owned by the specified user and group. If you choose the script option, a Bourne shell script is generated and performs all the necessary chown operations by using owsadm.exe. Before running the script, however, you must edit it by entering the UNIX user identifiers and group identifiers you want to associate with each web. Installing a root web and subwebs for the first time To install a root web and add subwebs, you perform the following steps: Untar FrontPage Server Extensions 2002 and install them on the root web of the Web server. Before installing, you are prompted for a web administrator name and password. You will need this name and password when you administer or author the web from a FrontPage client. After installing the root web, you are prompted for your computer's local character encoding and default language. Create subwebs within the root web, and enter the administrator user name and password for each subweb you create. During installation of the stub FrontPage Server Extensions 2002 on a subweb, you are prompted for the subweb name. If the name is of the form ~webname (a "per-user" web), then "webname" is used as the name of the subweb's owner in the UNIX file system. If the name is not in this form, you are prompted for the name of the owner. You are also prompted for the name of the group owner. For each FrontPage-extended web, fp_install.sh will then perform the chown operation on the content in the Web to be owned by the specified UNIX user and group. FrontPage Server Extensions 2002 then do the following for each root web or subweb: Expand FrontPage-based components, such as Include and Substitution components. Create a hyperlink map of the FrontPage-extended web. Extract page titles. Extract base URLs. Installing on virtual servers After you have installed to a root web and subwebs, you are prompted to install FrontPage Server Extensions 2002 on any additional virtual servers. If you choose to install on another virtual server, you are prompted for your server configuration file. Based on this file, the script displays a list of virtual servers. Before installing, you are prompted for a web administrator name and password. You will need this name and password when you administer or author the Web from a FrontPage client. After installing the root web, you are prompted for your system's local character encoding and default language. After you have installed to the virtual server, you are prompted to create subwebs below the root web. When a subweb is being created, you are asked for a name for the subweb. If the name is of the form ~webname (a "per-user" web), then "webname" is used as the name of the subweb's owner in the UNIX file system. If the name is not in this form, you are prompted for the name of the owner. You are also prompted for the name of the group owner. For each subweb that you choose, you are also prompted for the administrator's name and password. For each FrontPage-extended web, fp_install.sh will then perform the chown operation on the content in each Web to be owned by the specified UNIX user and group. FrontPage Server Extensions 2002 then do the following for each root web or subweb: Expand FrontPage-based components, such as Include and Substitution components. Create a hyperlink map of the FrontPage-extended web. Extract page titles. Extract base URLs. Installing the FrontPage Apache patch On the Apache Web server, FrontPage Server Extensions 2002 need to modify the Web server's configuration file to mark directories containing the FrontPage Server Extensions 2002 as executable. Because creating a subweb by using the FrontPage client requires the client to write to the Web server's configuration file on these servers, which the Web server process owner usually does not have permissions to do, administrators cannot create FrontPage-extended subwebs in this way. On these servers, the owsadm.exe utility or fp_install.sh must be manually run as "root" on the host computer to modify the Web server's configuration file and create subwebs. For the Apache Web server, FrontPage supplies a patch to overcome this limitation. With this patch, copies of FrontPage Server Extensions 2002 executable files are not stored in each FrontPage-extended web, but are stored in one centralized location. This centralization of executable files makes it unnecessary to mark directories in each Web as executable, and makes it possible for the FrontPage client to create new FrontPage-extended webs without modifying server configuration files. You can convert your current Apache Web server to the FrontPage-patched Apache Web server in two ways: You can install one of the precompiled patched executables included in the FrontPage Server Extensions 2002 tar file. That method is described in this section. You can manually compile-in the provided patch source files into your current Apache server. That method is described below, under "Compiling and installing your own version of the Apache patch." The fp_install.sh script also upgrades your Apache server to the FrontPage-patched Apache server, and upgrades any FrontPage-extended Apache webs to use the FrontPage patch. Important Before you install the FrontPage Apache patch, back up your current Apache server, FrontPage installation directory, server configuration file directory, and all Web content. When you run the script, it performs the following functions: Checks to make sure the current server has not already been upgraded. Moves the old Apache daemon to the file httpd.orig. Copies the new FrontPage-patched Apache Web server to the correct directory. Creates a default custom key file as /usr/local/frontpage/version5.0/apache-fp/suidkey. This file undergoes chown and chmod operations to become only readable and writable by "root." The default custom key value is dynamically generated, but for the best protection this key value should be changed on a regular basis and the server restarted. Next, you are prompted to upgrade any FrontPage-extended Apache servers to use the new, patched server. If you choose to upgrade, the script: Modifies the FrontPage configuration files in /usr/local/frontpage so that they refer to the new server. Calls the owsadm.exe utility to upgrade each Web content area. Sets up your security. You can choose to set up the security of your FrontPage-based webs interactively, or you can have fp_install.sh generate a script (fp_chown.sh) to set up security. If you choose the interactive option, the script will prompt you for the UNIX user ID and group ID of each root web and subweb that you have upgraded. For each FrontPage-extended web, fp_install.sh will perform the chown operation on all the FrontPage-created directories and content in each Web to be owned by the specified user and group. If you choose the script option to set up security, fp_install.sh will generate the script. Before running the script, however, you must fill in the UNIX user IDs and group IDs you want to associate with each web. Finally, you are prompted to set the default permissions. If you choose "y," the script set_default_perms.sh is invoked. This script sets permissions on /usr/local/frontpage/version5.0 and all directories below it to the defaults. For a complete listing of default FrontPage Server Extensions 2002 permissions, see Files and Permissions on Apache. For FrontPage Server Extensions 2002 to work once the new server is installed, the FrontPage Apache stub, in /usr/local/frontpage/version5.0/apache-fp/_vti_bin/fpexe, must be owned by, and user ID set to, "root"; fp_install.sh does this for you. After installing the FrontPage Apache patch, you must restart Apache. Compiling and installing your own version of the Apache patch Microsoft makes the source code of the FrontPage Apache patch file available. To compile an Apache Web server with any custom or nonstandard modules along with the FrontPage Apache patch, follow the directions in this section. If you do not want to compile your own Apache Web server, follow the directions under "Installing the FrontPage Apache patch" to install the precompiled FrontPage Apache patch. Before compiling and installing the FrontPage Apache patch, you must first uncompress and untar the FrontPage Server Extensions 2002 file, a process which fp_install.sh does for you. When this is completed, the FrontPage Apache patch source file, fp-patch-apache_1.3.X, will be located in a directory underneath where the original file was untarred. This patch must be compiled and the new Apache daemon installed before installation of the FrontPage Server Extensions 2002 can continue. To compile and install your own version of the FrontPage Apache patch Copy fp-patch-apache_1.3.x into your Apache server directory (usually /usr/local/apache). If you have compiled an Apache Web server using a previous version of the FrontPage Apache patch source file, use the GNU version of the patch utility to remove the previous version of the FrontPage Apache patch from your Apache server: %patch -p0 -R < previous_FrontPage_patch_file Using the GNU version of the patch utility, run the patch command on the FrontPage Apache patch source file: %patch -p0 <fp-patch-apache_1.3.x Create the makefile for the patched server. For a server that uses the 1.3.0 or later directory structure: % configure --add-module=mod_frontpage.c Build the Apache server: %make Replace the old Apache server. Run the script fp_install.sh as described in "Installing the FrontPage Apache patch." This will upgrade FrontPage-extended webs and set permissions properly on content. Start the new Apache server. -----Original Message----- From: Robin Cook [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 16, 2002 1:52 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [expert] mod_frontpage and frontpage extensions. Does anyone have the exact installation steps and any other software needed to get the frontpage server extensions working on Linux with Apache?
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
