BJ> Let me know how things go....

 AI> I have bin/max now.. :) I tried to post a message but got an error
 AI> message and max quit. Is that normal or is that an error in my configs?
 AI> I have a lot of reading to do to get up to speed..

Ok.  Is that bin/max in the location you are running "make build"
or in /var/max/bin/max?  If it is in the "make build" location,
then max is not set up to run from there due to configuration issues.  You
will need to run "make install" (or "make max_install")
to get the exectable file into the /var/max/bin location.

Some options with Max running under Linux / Unix will cause an error
message and max to quit.  If running the code from the .tar.gz files, I
believe you can get max up and running using the ./scripts/runbbs.sh (or is
it runbbs.sh in the /var/max directory?) script.  This will start max up
and allow telnet to the port number specified on the command line used to
start max.  You should also be able to start max (while the current path is
/var/max, and the userid set to the correct  account) with "bin/max
-k".  There are known issues with "local mode" (i.e. the -k
option) that don't hit the telnet method, and vice versa.  The .tar.gz
distribution doesn't support a modem yet.  One of the successful "make
install" runs should have run max in local console mode where you
entered your name as the initial user -- and became the sysop of the
configuration.  If you didn't do this, then there is a problem with having
not set up the maximus user data base yet.  I'm not sure I remember the
command line switch for that (maybe "bin/max -C" to create the
user base, and log in on the local console as the initial user -- who
becomes the sysop).

 AI> I downloaded the source from the cvs server described in the
 AI> quickstart file. I have never used cvs before so I don't know
 AI> much about it. It looks like I can run that command and the
 AI> server will get any changed files and keep my maximus/ directory
 AI> the same as on the server.. is that so and is that the way
 AI> I should be doing it?

  If you want to keep up with Alpha testing, you can use cvs
commands to get updates from sourceforge.... 

SourceForge is currently delaying development checkins up to 24 hours
before they can be downloaded from the anonymous CVS server.  [This is a
work load / capacity issue at sourceforge that they are working on.]

If you update from CVS, the telnet option of maximus may become broken.  [I
haven't checked to see if it is fixed yet....  But my telnet option broke
after a CVS update, and I wasn't working on that part of the code....  I've
gone back to 'bin/max -k' to test what I was working on....  I believe some
of Wes's updates to attempt to get the modem working broke some of the
telnet stuff....]

Any way, if you do a CVS update from sourceforge, in about 24 hours or
less, you will be able to see the addition of the SqaFix program.  Bo also
has a QWK bug in Maximus that he has a fix for.  [Bo, is that fix checked
in to CVS yet?]  And we have some fixes to squish checked into cvs that are
needed to (a) correct the dupe checking code (see older messages in the TUB
echo) and for (b) .

For the most part, squish from cvs is working under Linux like it is for
the other platforms.  [Except for the known bug in the Linux version
dealing with paths on file attachments.]  Max still has some serious issues
to be dealt with before it is ready for prime time.  [Mex is busted,
busted, busted, busted.......]

Take care.....

Bob Jones, 1:343/41
 

--- Maximus/2 3.01