Symlink ifcico -> husky or husky -> ifcico ... ?
it's been awhile, & don't recall for sure; basically, I don't
think they create/name zone outbound directories quite the same.
Think I basically let hpt create the outbound directories the way it
thought it should, then created symlinks as neccessary to ensure that
binkd & ifcico could see the same directories...
Hmmm .... you don't happen to have a cut down version of the config file handy
do you? <grin>
Hmmm .... you don't happen to have a cut down version of the config
file handy do you? <grin>
For ifcico, you mean? Rather depends on what you mean by "cut down"...<g>
I do have examples of a single config file I use for ifcico by
itsself (for pots, IFC, & ITN calls), which I normally name
ifcico.conf. it's not exactly short (the version I'm looking at is
249 lines) but that's because it's got a lot of the original
configuration remarks in it... Don't think I have a copy of it
online publically right now, but I could make it or something like it available for freq (and/or ftp, http); and/or available via email or something...
It has also just occured to me that if I use ifcico, I have no need to use
BinkD as MBSE BBS can handle ifcico protocol ...
crashmail.perf file, but the way the routing in crashmail works still
It has also just occured to me that if I use ifcico, I have no
need to use
BinkD as MBSE BBS can handle ifcico protocol ...
mbcico, started as a modified clone of ifcico, so of course it can
handle ifcico connections. It's just better now....
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,044 |
Nodes: | 15 (0 / 15) |
Uptime: | 61:07:52 |
Calls: | 236,243 |
Calls today: | 3 |
Files: | 67,658 |
D/L today: |
115 files (67,272K bytes) |
Messages: | 290,417 |