Roy J. Tellason wrote to Maurice Kinal about ''OS/2-native twit filter'':


 RJT>> In my case it's (currently) handled by a fossil driver and the 
 RJT>> connection is handed off from binkley.  How does that work under 
 RJT>> linux?

 MK>> First off there is no need for a fossil driver

 RJT> I didn't think so.  But I have *no* idea how the serial port stuff
 RJT> is handled under linux.

Well I did program the modem support for maximus, so I should be the right
one to tell you. ;)

Modem thing under Linux works like working with files.. You just open a
"file" which is /dev/ttySx, and then you use read()/write()
commands, to send and recieve data from the modem.

There is some libery functions (tios, man tcgetattr), to lower/raise DTR
and so on. Like ioctl() also serves some usefull functions..

And a lucky news I did do a successfully session yesterday with my modem. I
let binkley answer the call and then binkley spawned the BBS (under linux
ofcause), and it did work out.

I still have some problems about if the user lost carrier and so on, but it
take some time.

 MK>> but I am not sure about the Linux version of bink.

 RJT> Neither am I.  I remember somebody saying that he got it to
 RJT> compile,  but that there were some hassles.  Maybe I oughta take
 RJT> it up in the LINUXBBS echo once I decide to start moving on this.

BTXE works very well and it's very stable!

 RJT> Yep,  that's what I have bink doing now.  Note that it doesn't
 RJT> have to exit, necessarily.  The OS/2 version "spawns" the bbs
 RJT> program instead,  and doesn't exit.  I think that may have some
 RJT> advantages,  though I'm not quite 100% sure of what they are as I
 RJT> never did get things going under OS/2 here. 

Yes you need the "os/2" way under Linux, but "BBS
Spawn" in binkley.cfg together with a spawnbbs shell script.

Bo

---