Well I have to give my hat off to all of you that have set up Husky, I have spent close to a month trying to get it set up and running and have now decided it is too complex/not enough clear documentation for me so I am scrapping my linux box and just going to continue running Mystic on win32. Some of my major issues with Husky was trying to compile Fidoconf and getting an error I could not find an answer for, Running tparser and have switches autoAreaCreate on/autoFileCreate on cause errors and not being able to find documentation that describes those switches.

--- Mystic BBS v1.12 A47 2021/06/19 (Windows/32)
* Origin: commconnbbs.net (21:1/192)

On 14 Jul 2021, Sparky said the following...

Well I have to give my hat off to all of you that have set up Husky, I have spent close to a month trying to get it set up and running and have now decided it is too complex/not enough clear documentation for me

Yeah, I was in the same boat. Thought about playing with that when I was running Telegard but it was way over my head.

If there were some "Husky Guy" videos out there like there are for Mystic I may give it another try one day.


Jay

... Anyone who lives within his means suffers from a lack of imagination.

--- Mystic BBS v1.12 A47 2021/07/06 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

Re: Setting up Husky
By: Sparky to All on Wed Jul 14 2021 06:06 am

Howdy,

Well I have to give my hat off to all of you that have set up Husky, I have spent close to a month trying to get it set up and running and have now decided it is too complex/not enough clear documentation for me so I am scrapping my linux box and
just going to continue running Mystic on win32. Some of my major issues with Husky was trying to compile Fidoconf and getting an error I could not find an answer for, Running tparser and have switches autoAreaCreate on/autoFileCreate on cause errors
and not being able to find documentation that describes those switches.

Well, if you want to be able to skip the "compiling/installing" part and get to just use it - then you are welcome to use my docker container.

My container runs Hubs 3 & 4 (so it has husky and a couple of other tools), and since Avon also runs husky there are at least 3 of us here that can help you with the configuration side of it.

...ëîåï

... A modest man is usually admired - if people ever hear of him.
--- SBBSecho 3.14-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Re: Setting up Husky
By: Warpslide to Sparky on Thu Jul 15 2021 08:51 am

Yeah, I was in the same boat. Thought about playing with that when I was running Telegard but it was way over my head.

If there were some "Husky Guy" videos out there like there are for Mystic I may give it another try one day.

What I said to Sparky... :)

...ëîåï

... Chuck Norris put the "fist" in "pacifist".
--- SBBSecho 3.14-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Well I have to give my hat off to all of you that have set up Husky, I have spent close to a month trying to get it set up and running and have now decide it is too complex/not enough clear documentation for me so I am scrapping my linux box and just going to continue running Mystic on win32.

When I first setup the husky tools I found the same thing. I must have spent six months just playing with it before it all started making sense to me.

Then husky 1.9 changed a lot of keywords and I spent another few months getting that straight. Be sure you are looking at current documentaion. The web is chalk full of 1.4 husky setup.

Some of my major issues with Husky was trying to compile Fidoconf and getting an error I could not find an answer for, Running tparser and have switches autoAreaCreate on/autoFileCreate on cause errors and not being able to find documentation that describes those switches.

Back in the 1.4 days I used those keywords. They are related to auto adding areas as they arrive for nodes that you give that access to.

My area configuration is fairly static these days and if I need to add any areas I just do that myself so those keywords don't exist in my config now. It can be done but you'll need husky 1.9 documentaion since some of those keywords are the ones that changed with 1.9.

I spent a lot of time discussing my issues with others to get past issues I was having. We could do that here, there are at least a few in fsxNet that run the husky tools and could help you along the way.

Mystic has a pretty good and easy to use tosser also. It has always been my hope that it would get past the issues that exist there like the busy nodes issue that happen periodically. g00r00 still works on these things so I am sure that will happen given time.

--- BBBS/Li6 v4.10 Toy-5
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.2)

Try installing git on your debian box, and cloning the repo. That will give you the latest version of the husky project. Older gzipped or tar packages may not work with newer compilers any more.

Working on that now. Got git installed and working on cloning the husky repo (another new process to learn...)

huskymak.cfg is the file you edit and put in the root husky directory

Got that and edited accordingly.

That said, I have no idea what fidoconfig.conf is, unless you've renamed

it is the fidoconfig file, I have it named config.

"/usr/local/include/smapi/typedefs.h:42:23: error: conflicting types for dword typedef unsigned long dword;
In file included from ../huskylib/compiler.h:1155,
from src/common.c:45:
../huskylib/UNIX.h:192:22: note: previous declaration of dword was here
typedef unsigned int dword;
^~~~~
In file included from /usr/local/include/smapi/msgapi.h:28,
from src/common.c:76:
/usr/local/include/smapi/typedefs.h:43:21: error: conflicting types for sdword typedef signed long sdword;
^~~~~~
In file included from ../huskylib/compiler.h:1155,
from src/common.c:45:
../huskylib/UNIX.h:193:22: note: previous declaration of sdword was here
typedef signed int sdword;
^~~~~~
In file included from /usr/local/include/smapi/msgapi.h:29,
from src/common.c:76:
/usr/local/include/smapi/stamp.h:34:8: error: redefinition of struct _stamp
struct _stamp
^~~~~~
In file included from ../huskylib/huskylib.h:42,
from src/common.c:71:
../huskylib/cvtdate.h:40:8: note: originally defined here
struct _stamp
^~~~~~
In file included from /usr/local/include/smapi/msgapi.h:29,
from src/common.c:76:
/usr/local/include/smapi/stamp.h:61:7: error: redefinition of union stamp_combo
union stamp_combo
^~~~~~~~~~~
In file included from ../huskylib/huskylib.h:42,
from src/common.c:71:
../huskylib/cvtdate.h:57:7: note: originally defined here
union stamp_combo
^~~~~~~~~~~
In file included from /usr/local/include/smapi/msgapi.h:29,
from src/common.c:76:
/usr/local/include/smapi/stamp.h:68:27: error: conflicting types for SCOMBO typedef union stamp_combo SCOMBO;
^~~~~~
In file included from ../huskylib/huskylib.h:42,
from src/common.c:71:
../huskylib/cvtdate.h:63:27: note: previous declaration of SCOMBO was here
typedef union stamp_combo SCOMBO;
^~~~~~
In file included from src/common.c:76:
/usr/local/include/smapi/msgapi.h:112:8: error: redefinition of struct _netaddr
struct _netaddr
^~~~~~~~
In file included from ../huskylib/huskylib.h:46,
from src/common.c:71:
../huskylib/ftnaddr.h:37:16: note: originally defined here
typedef struct _netaddr
^~~~~~~~
In file included from src/common.c:76:
/usr/local/include/smapi/msgapi.h:413:26: error: conflicting types for GenMsgId
SMAPI_EXT dword _XPENTRY GenMsgId(char *seqdir, unsigned long max_outrun);
^~~~~~~~
In file included from src/common.c:71:
../huskylib/huskylib.h:110:25: note: previous declaration of ‘GenMsgId’ was here
HUSKYEXT dword _XPENTRY GenMsgId(char * seqdir, unsigned long max_outrun);
^~~~~~~~
In file included from src/common.c:76:
/usr/local/include/smapi/msgapi.h:414:26: error: conflicting types for GenMsgIdEx
SMAPI_EXT dword _XPENTRY GenMsgIdEx(char *seqdir, unsigned long max_outrun, dword (*altGenMsgId)(void), char **errstr);
^~~~~~~~~~
In file included from src/common.c:71:
../huskylib/huskylib.h:111:25: note: previous declaration of GenMsgIdEx was here
HUSKYEXT dword _XPENTRY GenMsgIdEx(char * seqdir, unsigned long max_outrun, dword (* altGenMsgId)(
^~~~~~~~~~
make: *** [makefile.inc:27: common.o] Error 1"

Jeff

--- Mystic BBS v1.12 A47 2021/06/19 (Windows/32)
* Origin: commconnbbs.net (21:1/192)