| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Maximus UNIX port |
Hello Bo.
04 Jun 03 02:02, you wrote to me:
BS>>> He can use his max and squish configurations file, and if he
BS>>> would like to run BT he could use them too..
BS>>> He only needs to find a ticker, and some nodelist tools, that he
BS>>> can get from the husky project.
>> Yep, they worked very well here, that was before I made the move to
>> MBSE BBS.
BS> Then my fileticker tosses, it would automatic call the nodelist
BS> updater if a diff is recieved, and after that fastlst runs and qico -n
BS> :) So i'm automatically up to date with nodelist.
That is the idea, yes ...
RT>>>> Just got my first messages in this echo after being cut off for
RT>>>> more than a few days.
BS>>> Ok, i your hub not able to do a rescan? Or did he just
BS>>> subscribed the echo?
>> Nope, rescan does not work. :-(((
BS> Hmm.. stoneage system?
Yes, unfortunately ...
RT>>>> Seems I missed a lot. :-(
BS>>> I really don't know the most of the last days did we just
BS>>> discuss about maximus and mgetty issues.
>> Well, I support the use of mgetty for answering the phone and
>> deciding what to dowith the incoming call, works here, and I am not
>> using all the abilities that it allows. Other getty's do not work
>> as well.
BS> I've tested it on ISDN, and it detects fidonet calls fine, it works
BS> like:
BS> if(CALL == FIDO)
BS> {
BS> system("qico -a {at}");
BS> }
BS> else if(CALL == PPP)
BS> {
BS> ...
BS> }
BS> else
BS> {
BS> system("BBS");
BS> }
BS> If somebody didn't know it :)
Works great with POTS as well. :-))
Russell
--- GoldED+/LNX 1.1.4.7
* Origin: Rusty's BBS - Bloemfontein, Free State, South Africa (5:7105/1)SEEN-BY: 633/267 270 @PATH: 7105/1 7106/22 7102/1 140/1 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.