BJ>> There are pieces of
 BJ>> the max bbs code hard coded to expect (sysop) console support in
 BJ>> addition to the user's terminal.

 BS> ?

 MK> Waiting for caller screen.  I still say it is unneeded. 
 MK>  It's a hangover from snoopy DOS sysops who couldn't 
 MK> multitask or network.  I think it's useless on any Unix system myself.

Depends on your view......

It isn't snoopy DOS sysops, it was a natural outgrowth of the (MS or PC)
DOS environment.  The only way to control the BBS in that environment was
through the system console, via the program running from the (single)
command shell.  Even intial multi-taskers for DOS systems were just
switchers between command shells....  

Wes and I have had some discussions about this area of the code.  I've made
some assumptions about what might be doable, and Wes has told me where I
was wrong (concerning quick and dirty ways to convert the code to some 
Unix or multi-tasking OS style thinking).....  Part of the reason the code
currently runs the way it does is because of the desire to at least get the
code running in a Linux / Unix environment.....  I think Wes has some ideas
of how he would like to proceed in the future on this.  I suspect that if
we can get the maxpipe code running, the sysop console issue may be solved
along those lines....  If so, we might be able to bit bucket most of the
current sysop console I/O and start Max with a master process that then
spawns what is needed for each user as they log on to the BBS.  This would
be similiar to how Adept is coded under the OS/2 operating system.

Now a Unix based system (which could also be setup for OS/2 and now newer
Windows based systems) wouldn't need the console that Maximus was built
around.  And if a redesign was done with the intention of Max being started
from either inetd or (m)getty, then the wait for caller screen is not
needed.  Unfortunately, we are not that far along on this project....  Has
anyone attempted to run Maximus / Linux with a Binkley front end yet?

Now one thing your are forgetting, is that a sysop could help a new user
when they first start using the BBS.  I am sure there are many users that
were not familiar with a given BBS interface when they first called one (or
more) BBS(es).  This is where it was usefull for the Sysop to see what was
going on with his system.....

Any way.....

Take care.....

Bob Jones, 1:343/41



--- Maximus/2 3.01