Hello Bo.

30 May 03 23:27, you wrote to Wes Garland:

 BS> -- mgetty issue --

 WG>> The important thing is that the getty/calling program has to
 WG>> pass
 WG>> off a device filename (which is NOT the controlling terminal) to
 WG>> Maximus,
 WG>> and I need to modify max_args.c to support this (Scott changes
 WG>> everything
 WG>> over to ints as quickly as possible, where 0=COM1: -- I reused
 WG>> the ints  to mean port numbers in the tcp/ip driver)

 BS> Oh, so you'll make a fake device file, maximus is communicating with
 BS> mgetty over?

 BS> We need to find a way, to solve the mailer problem, because most of
 BS> the people who will run maximus at linux, would also be a fidonode.

Yes.

 WG>>  - Starting from a mailer -- I don't see any point to this in
 WG>> tcp/ip mode. Again, the mailer can't pass around the socket as
 WG>> stdin/stdout for the reasons mentioned above.

 BS> I think Roy ment from a POTS mailer like Binkleyterm whitch is running
 BS> under Linux too, and it doesn't use getty/mgetty afaik.

BinklyTerm does not use a getty, it controls the port directly, used it and 
it worked great, had trouble compiling it tho.



 WG>> I also have no intention of adding ftp/gopher/http/finger
 WG>> into Maximus, if people want to use that stuff, they should use
 WG>> the internet. A BBS should be a BBS, dammit. Doors *out* to the
 WG>> internet are fine, but making a BBS look like a mini-internet
 WG>> always struck me as being totally counter-productive. :)

 BS> That's good enought to me.

No complaints either.

Russell

--- GoldED+/LNX 1.1.4.7