Maurice Kinal wrote in a message to Roy J. Tellason:

 MK> Hey Roy!

 MK> Apr 07 04:07 04, Roy J. Tellason wrote to Maurice Kinal:

 MK>> Less not more.

 RJT> 

 MK> Wow!  Somebody out there actually understands this concept!!!  One
 MK> thing for sure is it is a totally alien way of thinking to the
 MK> pointy-clicky crowd.

Yeah,  well,  you oughta know darn well by now that we're on the same
wavelength when it comes to this sort of thing...

 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

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

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

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

 MK> However binkd should work fine once you have your connection 
 MK> established with the network to the outside world, in your case 
 MK> ppp, so providing drivers for that would only serve to complicate 
 MK> things.

Ok,  and that's a protocol that I can use to deal with my uplink,  or if
not him directly then _an_ uplink,  how do I handle incoming calls?  Right
now it's bink that watches the phone line,  answers it when it rings,  and
hands off to the bbs when that's necessary.  I'd need something to do the
same thing under linux.

 MK> If you want your machine to answer a ring then you either have to 
 MK> provide a ppp login or use something like a frontend mailer that 
 MK> can exit with an errorcode dependent on the incoming call (voice 
 MK> or data).

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

 MK> In other words there is no or little difference except that Linux 
 MK> natively provides a whole slew of networking options to you and 
 MK> all that needs to be established is you setting them up to work 
 MK> for your needs.  Serial stuff for the mostpart.

Yep.  But I haven't got a clue as to where to start with that stuff.

---