...
 WG> Thanks -- looks like Bink XE handles and passes off a 
 WG> plain serial port (this is good) and Synchronet uses a 
 WG> TTY.
 WG>  
 WG> This works out well, because Maximus is not going to 
 WG> work under a getty-style environment any time soon, 
 WG> because the max sysop console is handled through 
 WG> curses, which talks to the  controlling pseudo tty 
 WG> (long story short, max can't tell the sysop from the 
 WG> user under a getty right now).

I figured unix's (and assume Linux's) way of using a controlling console
and the way Maximus is written would bite in this area.....  It's been a
while since I've had to deal with this issue.....  

 WG> So, handing off to max should be pretty straightforward 
 WG> from Bink XE once I get the serial module running -- 
 WG> something like this would need to run from the mailer:
 WG>  
 WG> cd /var/max && bin/max -b38400 -n1 -pserial:/dev/ttyS1 -xc
 WG>  
 WG> "serial:" instructs the new comm driver stub to load 
 WG> serialcomm.so and open port /dev/ttyS1. "-n1" forces us 
 WG> to node number one (-n0 is for dynamic ports, i.e. for 
 WG> the ip driver). -b38400 provides the baud rate, I 
 WG> forget if this is the fixed DTE/DCE rate or not (pretty 
 WG> sure it is), and -xc tells max to not check DCD, just 
 WG> flip right to the user login.

The -b38400 is the baud rate.  Under OS/2, I handled the locking of the com
port was handled external to Maximus, via SIO.....  It could also be via
Binkley.  As such, when max is handed an already connectec modem, a locked
or unlocked com port shouldn't matter....

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01