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
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.
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.
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.
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.
deon wrote to Sparky <=-
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.
It's the configuration file that throws most people off. I know my way around a config file, or two, but trying to set up htick from scratch was daunting at best.
deon wrote to Sparky <=-
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.
It's the configuration file that throws most people off. I know my way around a config file, or two, but trying to set up htick from scratch was daunting at best.
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.
It's the configuration file that throws most people off. I know my way around a config file, or two, but trying to set up htick from scratch
was daunting at best.
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.
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.
It's the configuration file that throws most people off. I know my way around a config file, or two, but trying to set up htick from scratch
was daunting at best.
Not sure if you're even interested in this topic any more, but it shouldn't be as big a deal as you're making it out to be. It's possible you pulled the git repo while there was a bug, or you didn't install the prerequisites first, which could create issues for you.
just use it - then you are welcome to use my docker container.Hi Deon, I may just take you up on that. Let me get docker set up and then I will email you with any questions I may have if that
SPARKY(21:1/192) wrote to All <=-I had a Husky Win32 install when I was running Mystic before I ran Winserver as my bbs.
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.
since Avon also runs husky there are at least 3 of us here that can help you with the configuration side of it.
Your right in that it shouldn't be a big issue but it did...First I started with a gzip/tar file that I uploaded to my debian box and decompressed into a home-fido-husky. Then edited husky.cfg to fit my use and edited fidoconfig.conf. I started the make process as you listed husky.lib, smapi.lib and both went fine then fidoconf kept giving me an error. So I am going to start from scratch and see what happens. As I have said earlier that lack of good docs has not made this any easier...
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.
huskymak.cfg is the file you edit and put in the root husky directory
That said, I have no idea what fidoconfig.conf is, unless you've renamed
it is the fidoconfig file, I have it named config.
make: *** [makefile.inc:27: common.o] Error 1"
First question, what were you trying to compile here? Can I assume this
is the same as you previously mentioned, where huskylib and smapi compiled fine, but now fidoconf is giving you problems? If this is the case, did 'make install' on
Again thanks for your time and help, since I am no rush to get this running I am taking my time to make sure I get thigns right and UNDERSTAND what I am doing. One step forward, do some more reading.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,038 |
Nodes: | 15 (0 / 15) |
Uptime: | 147:18:00 |
Calls: | 500,200 |
Calls today: | 1 |
Files: | 95,197 |
D/L today: |
384 files (42,005K bytes) |
Messages: | 465,979 |