*BSD News Article 92271


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.Hawaii.Edu!news.caldera.com!enews.sgi.com!news.corp.sgi.com!news.sgi.com!su-news-hub1.bbnplanet.com!cam-news-hub1.bbnplanet.com!news.bbnplanet.com!howland.erols.net!newsxfer.itd.umich.edu!uunet!in1.uu.net!206.139.252.5!newsreader.com!not-for-mail
From: curt@kcwc.com (Curt Welch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: MS Frontpage Ext. for FreeBSD?
Date: 29 Mar 1997 22:20:32 GMT
Organization: KCW Consulting
Lines: 42
Message-ID: <I2O$A0@NewsReader.Com>
References: <333c6d86.7784747@snews2.zippo.com>
NNTP-Posting-Host: h4.kcwc.com
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:38008

stephen@lainet.com (Stephen) wrote:
> Does anybody have any experiences installing Microsoft FrontPage
> extensions on a FreeBSD 2.1.5 running Apache 1.2?

I'm doing it.  But, to be honest, I don't remember what version
of the extensions I installed.  It wasn't for FreeBSD.  It probably
was for BSDI.

If you check out the FrontPage extensions FAQ, you will find
info about FreeBSD.

I remember two problems.  The first is that FreeBSD has
a different version of crypt (using MD5 instead of the normal
Unix version).  This breaks passwords, and means that you
can't log into the server (password rejected).  This is talked
about in the FrontPage faqs.

The qucick and dirty fix, is to just cut and paste a password out of the
FreeBSD password file into the FrontPage file which stores
the user's passwords.  This allows you to log in, but you can't
change your password using FrontPage.

The real fix is to get a normal Unix version of crypt and recompile
something.  I never bothered to figure this out.  Was it the
Apache server that needed to be recompiled?  Or was it
the front page software that was dynamically linked with
the freebsd libs?    I don't know.

The other problem I had was related to the fact that I was
using the Stronghold version of the Apache server.  The
config files for Stronhold have /dev/null for some include
files and this confused FrontPage when it tried to write some
new config commands to /dev/null.  Changing those links
to real files fixed that problem.

I've never really tested all the fancy server-side features
of Frontpage with this config (because I don't really want
to use them), but all the basic site control and maintenance
works great.  I love FrontPage!

Curt Welch
http://CurtWelch.Com/