Hello Wes.

02 Jul 03 08:13, you wrote to me:

 WG> Thanks for the feedback.

Pleasure, just some things that I like with MBSE BBS, that I figured where 
worth mentioning early on in Maximus's migration to *nix land.

 WG> I'm in a bit of a hurry, so I'll address these quickly:

You too. :-)

 WG> uid/gid - Maximus really doesn't care much about this, as long as it
 WG> has the rights to create/read files, it's happy. The caveat is that
 WG> Max is currently creating files with 0600 permissions, which are only
 WG> readable by the user max runs as. This WILL be fixed, probably in the
 WG> next
 WG> release.

Understood, no problem.

 WG> Bink XE -- Binkley must have *some way* of handing off a com port to
 WG> another program, or at least exiting when a BBS caller calls. Since I
 WG> don't have a modem or Bink XE, I haven't figured out how to do this
 WG> yet. But somebody may have by the time I get maximus serial support
 WG> theoretically working.

I have run Bink XE with the Husky project utils, but without a BBS as they 
don't have one, worked very well as a point, so I cannot comment, on this 
aspect of it.

 WG> getty -- I can't see running from a getty being supported by Maximus
 WG> any time soon. There are too many problems to solve with this, trying
 WG> to separate user and sysop input.

That is understood, also as Bob mentioned Maximus has its own user 
authentication, and user data base, so this is not really a requirement, and 
I hope he is correct, in that Bink XE can handle a hot commport from mgetty 
or similar.

Russell

--- GoldED+/LNX 1.1.4.7