Part 2: How the FrontPage extensions are setup on Unix.

Wait, I thought that we were already talking about FrontPage extensions.

Well, in a way we were, but like all popular technologies that have limited technical documentation and catch on too quickly, people are confused and there is a gray line. The original FrontPage extensions for Apache came with a patch to the Apache source code that added the mod_frontpage module. At that time I guess you could say that the whole tarball and everything it contained where the "FrontPage extensions". The module itself started to become a little more separated when companies began integrating just the module into their own Apache setups, but still required you to download the rest of the extensions.

With the release of Improved mod_frontpage, the module and fpexec program where completely separate of the extensions kept in /usr/local/frontpage. In this instance, the extensions now refer to the programs that are installed in the document root on your web server and also in /usr/local/frontpage. This is where the server side FrontPage configuration files and installation programs are kept.

After untarring the tarball from Microsoft into /usr/local/frontpage, we wind up with the following hierarchy:

/usr/local/frontpage/
`-- version4.0/
    |-- _vti_bin/
    |   |-- _vti_adm/
    |   `-- _vti_aut/
    |-- admin/
    |   `-- scripts/
    |-- apache-fp/
    |   `-- _vti_bin/
    |-- bin/
    |-- exes/
    |   `-- _vti_bin/
    |       |-- _vti_adm/
    |       `-- _vti_aut/
    |-- nls/
    |-- serk/
    `-- srcs/