• Compiling Huskybse

    From Avon@21:1/101 to All on Sun Jan 10 15:23:47 2021
    Hi folks

    I am trying to install the Husky Project software on my Debian 10 box.

    My plan is to run a current copy of HPT and HTick along with whatever I need
    to work with these. I understand the components / files I need to compile are

    areafix
    fidoconf
    hpt
    htick
    huskybse
    huskylib

    I have cloned these from a git repo so they sit as subdirs under a holding folder called huskyproject

    once all compiled I *think* I need to either place all the complied stuff in one 'husky' working directory or locate complied stuff in sub dirs off a
    husky dir?

    I'm trying to suss how best to start compiling and it looks like for huskybse there's a config file called huskymak.cfg that needs some attention.

    I'm a tad lost to know what should/should not be changed in this file, especially in relation to directories and filenames?

    Any tips on how to compile and install / shift files to desired locations
    once installed are appreciated.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Rick Smith@21:1/190.1 to Avon on Sat Jan 9 18:27:14 2021
    Greetings Avon!

    Sunday January 10 2021 15:23, you wrote to All about an urgent matter!:

    Hi folks

    I am trying to install the Husky Project software on my Debian 10 box.

    My plan is to run a current copy of HPT and HTick along with whatever
    I need to work with these. I understand the components / files I need
    to compile are

    areafix
    fidoconf
    hpt
    htick
    huskybse
    huskylib

    I have cloned these from a git repo so they sit as subdirs under a
    holding folder called huskyproject

    The way I did it was have all those directories from git in src/husky.. go in huskybse and copy the make file into src/husky (or wherever you have it) then you go into each folder ie /hpt or whatever and do I believe make install all and repeat until you have them all installed.. as far as using any of it, its on the path for the most part so you can run any of it from the command line from anywhere.. Ive set it up a bunch and it was easy, and I am no expert..





    ----
    Regards,


    Rick Smith (Nitro)

    ... BBSing is a terminal experience
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: ----> Abacus Sysop Point --->>>>bbs.abon.us:2323 (21:1/190.1)
  • From Al@21:4/106.1 to Avon on Sat Jan 9 18:44:36 2021
    Re: Compiling Huskybse
    By: Avon to All on Sun Jan 10 2021 03:23 pm

    My plan is to run a current copy of HPT and HTick along with whatever I need to work with these. I understand the components / files I need to compile are

    areafix
    fidoconf
    hpt
    htick
    huskybse
    huskylib

    It's important that you build huskylib, smapi and fidoconf before any others, and also, areafix before hpt.

    once all compiled I *think* I need to either place all the complied stuff in one 'husky' working directory or locate complied stuff in sub dirs off a husky dir?

    after getting huskymak.cfg in place run "make" in each directory followed by "sudo make install". By default your binaries will be put in /usr/local/bin but you can change that in huskymak.cfg if you want.

    I'm trying to suss how best to start compiling and it looks like for huskybse there's a config file called huskymak.cfg that needs some attention.

    Yes, put that in the root husky dir and make any changes if needed, make will use that each time it is called.

    I'm a tad lost to know what should/should not be changed in this file, especially in relation to directories and filenames?

    I only change one thing IIRC, I change etc/lib to etc/lib64 since I need to do that on slackware.

    Any tips on how to compile and install / shift files to desired locations once installed are appreciated.

    Just the order, you need to start with huskylib, smapi, fidoconfig and areafix. That's all in my case anyway.. but we are here if you need us.. :)

    Ttyl :-),
    Al

    ... Press to test... <Click> Release to detonate...
    --- SBBSecho 3.12-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Michael Pierce@21:2/145 to Avon on Sat Jan 9 18:52:08 2021

    Hello Avon!

    10 Jan 21 15:23, you wrote to all:

    Hi folks

    I am trying to install the Husky Project software on my Debian 10 box.

    My plan is to run a current copy of HPT and HTick along with whatever
    I need to work with these. I understand the components / files I need
    to compile are

    areafix
    fidoconf
    hpt
    htick
    huskybse
    huskylib

    I have cloned these from a git repo so they sit as subdirs under a
    holding folder called huskyproject

    once all compiled I *think* I need to either place all the complied
    stuff in one 'husky' working directory or locate complied stuff in sub dirs off a husky dir?
    normal recomendations would be to create a husky folder, then cd into that folder, and run git clone on the modules you need.. then goto the huskybse folder and cp huskymak.cfg ../
    then follow the install instructions in huskybse


    I'm trying to suss how best to start compiling and it looks like for huskybse there's a config file called huskymak.cfg that needs some attention.

    I'm a tad lost to know what should/should not be changed in this file, especially in relation to directories and filenames?

    Any tips on how to compile and install / shift files to desired
    locations once installed are appreciated.


    Michael


    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Mike's Mansion - Portland, OR - mansion.dynv6.net:2323 (21:2/145)
  • From deon@21:2/116 to Avon on Sun Jan 10 14:54:17 2021
    Re: Compiling Huskybse
    By: Avon to All on Sun Jan 10 2021 03:23 pm

    My plan is to run a current copy of HPT and HTick along with whatever I need
    to work with these. I understand the components / files I need to compile are
    I have cloned these from a git repo so they sit as subdirs under a holding folder called huskyproject
    once all compiled I *think* I need to either place all the complied stuff in one 'husky' working directory or locate
    complied stuff in sub dirs off a
    husky dir?
    I'm a tad lost to know what should/should not be changed in this file, especially in relation to directories and filenames?
    Any tips on how to compile and install / shift files to desired locations once installed are appreciated.

    One of the good things with docker, is application builds are build like a receipe - here is the receipe I use to build the Hub 3 container.

    http://dev.leenooks.net/bbs/fidohub/-/blob/master/Dockerfile

    You'll get an idea of what I do to install husky.

    ...лоеп

    ... I reserve my abuse for lower life forms, like Civil Servants.
    --- SBBSecho 3.11-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From Avon@21:1/101 to Al on Sun Jan 10 17:09:19 2021
    It's important that you build huskylib, smapi and fidoconf before any others, and also, areafix before hpt.

    do I need smapi if I plan to to run JAM bases? Or is it best to have this as
    an option even if not used?

    What of huskybse - when to compile that? Assume I need it to?

    after getting huskymak.cfg in place run "make" in each directory

    By in place you mean copy it from huskybse to the root dir huskyproject?
    Do I need to do the same for each other program as well before compiling?

    huskybse there's a config file called huskymak.cfg that needs some attention.

    Yes, put that in the root husky dir and make any changes if needed, make will use that each time it is called.

    Deon seems to have set PERL=1 so perl support enabled?
    I also see USE_HPTZIP=1 in Deon's script, what's the merits of that one guys?

    Can someone comment on the CFGDIR=$(PREFIX)/etc/fido option in huskymak.cfg do I need to alter that or be locked into using that? Or best to go with this default?

    Just the order, you need to start with huskylib, smapi, fidoconfig and areafix. That's all in my case anyway.. but we are here if you need us..

    huskybse - when to do that one?

    Thanks!

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Michael Pierce on Sun Jan 10 17:10:39 2021
    On 09 Jan 2021 at 06:52p, Michael Pierce pondered and said...

    normal recomendations would be to create a husky folder, then cd into
    that folder, and run git clone on the modules you need.. then goto the huskybse folder and cp huskymak.cfg ../
    then follow the install instructions in huskybse

    Thanks, have done most of this now, just looking at huskymak.cfg and yet to move a copy of it to my parent huskyprojects folder.. which I think is what I need to do.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to deon on Sun Jan 10 17:13:25 2021
    On 10 Jan 2021 at 02:54p, deon pondered and said...

    One of the good things with docker, is application builds are build like
    a receipe - here is the receipe I use to build the Hub 3 container.
    You'll get an idea of what I do to install husky.

    Thanks :) Yep looking at it now.

    Looks like you're pulling down an compiling a few more Husky project repos
    than I have so far...

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to deon on Sun Jan 10 17:27:08 2021
    On 10 Jan 2021 at 02:54p, deon pondered and said...

    You'll get an idea of what I do to install husky.

    Questions on a few of the git repos you pull in / use...

    htpzip - so this is used to offer zip/unzip within HPT without the need to install infozip or similar? It would also explain the switch change you make
    in your config file for huskybse.

    hptutl - this looks like the jam packer, purge etc. tools, I'm picking I
    should get these as part of this 'standard' build?

    htpkill - what do you use this for? Do I need it?

    areastat / fidostat / nltools - I take it are all worth getting for the info they offer?

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Rick Smith@21:1/190.1 to Avon on Sat Jan 9 22:16:34 2021
    Greetings Avon!

    Sunday January 10 2021 17:09, you wrote to Al about an urgent matter!:

    It's important that you build huskylib, smapi and fidoconf before
    any others, and also, areafix before hpt.

    do I need smapi if I plan to to run JAM bases? Or is it best to have
    this as an option even if not used?

    What of huskybse - when to compile that? Assume I need it to?

    You dont actually compile huskybse, just the ones mentioned in the message from Al.. I left mine default, I use a different directory for all my config files and just use a symlink to that dir..



    ----
    Regards,


    Rick Smith (Nitro)

    ... BBSing ... time's blackhole.
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: ----> Abacus Sysop Point --->>>>bbs.abon.us:2323 (21:1/190.1)
  • From Al@21:4/106.1 to Avon on Sat Jan 9 22:27:00 2021
    Re: Re: Compiling Huskybse
    By: Avon to Al on Sun Jan 10 2021 05:09 pm

    What of huskybse - when to compile that? Assume I need it to?

    No, you just need to grab the huskymac.cfg from there and put in the root directory along with all the hpt, htick etc. directories.

    By in place you mean copy it from huskybse to the root dir huskyproject?

    Yes.

    Do I need to do the same for each other program as well before compiling?

    No, you just need to switch to each directory and run make in them, then sudo make install.

    Deon seems to have set PERL=1 so perl support enabled?
    I also see USE_HPTZIP=1 in Deon's script, what's the merits of that one guys?

    Yes, I have both of those options enabled although I don't use them. If I use hptzip then htick can't get file descriptions from the file_id.diz when tossing files, so I just use zip and unzip.

    Can someone comment on the CFGDIR=$(PREFIX)/etc/fido option in huskymak.cfg do I need to alter that or be locked into using that? Or best to go with this default?

    You can go with the default. If you leave it alone the husky stuff will look for a file called /usr/local/etc/fido/config for it's config file.

    I use /usr/local/etc/config but that is a choice you make. You can also call the file something other than config if you like, but it'll work as it is.

    huskybse - when to do that one?

    Yes, you just need the huskymak.cfg from there, copy it down a directory to your husky root, edit it to your needs and go.

    Ttyl :-),
    Al

    ... A diamond is just coal that has been under a lot of pressure!
    --- SBBSecho 3.12-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Avon@21:1/101 to Al on Sun Jan 10 19:42:56 2021
    On 09 Jan 2021 at 10:27p, Al pondered and said...

    Deon seems to have set PERL=1 so perl support enabled?
    I also see USE_HPTZIP=1 in Deon's script, what's the merits of that o guys?

    Yes, I have both of those options enabled although I don't use them. If
    I use hptzip then htick can't get file descriptions from the file_id.diz when tossing files, so I just use zip and unzip.


    OK I'll use them then but may need a hand to bypass should I hit the same issues.

    Can someone comment on the CFGDIR=$(PREFIX)/etc/fido option in huskymak.cfg do I need to alter that or be locked into using that? Or to go with this default?

    You can go with the default. If you leave it alone the husky stuff will look for a file called /usr/local/etc/fido/config for it's config file.

    I use /usr/local/etc/config but that is a choice you make. You can also call the file something other than config if you like, but it'll work as it is.

    it seems a pain to have the config there if I am putting the rest of the
    files in a dir called husky, I'm wondering if I should change that link. Hmm

    huskybse - when to do that one?

    Yes, you just need the huskymak.cfg from there, copy it down a directory to your husky root, edit it to your needs and go.

    OK thanks :)

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Rick Smith on Sun Jan 10 19:43:05 2021
    On 09 Jan 2021 at 10:16p, Rick Smith pondered and said...

    You dont actually compile huskybse, just the ones mentioned in the
    message from Al.. I left mine default, I use a different directory for
    all my config files and just use a symlink to that dir..


    Thank you :)

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Al on Sun Jan 10 20:30:29 2021
    On 09 Jan 2021 at 06:44p, Al pondered and said...

    I'm a tad lost to know what should/should not be changed in this file especially in relation to directories and filenames?

    I only change one thing IIRC, I change etc/lib to etc/lib64 since I need to do that on slackware.

    I ran the make and sudo make install and found a ton of compiled programs in /usr/local/bin with root group/owner privs.

    1) can I move them to my dir of choice and change them to my user group and ownership?

    2) I think I duffed up a setting in the huskymak.cfg and set CFGDIR=$(PREFIX)/hub/husky

    I was wanting the config to go to hub/husky but forgot about the prefix variable which was /usr/local

    /usr/local/hub/husky does not seem to be created nor does there seem to be a config file in there, should I have expected to see a default one there?

    3) If I were to start over now by making a change to the config file, am I
    safe to remove the compiled files from /usr/local/bin (do I do that first?) then run the make and make install process again thereafter?

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Al@21:4/106.1 to Avon on Sat Jan 9 23:35:19 2021
    Re: Re: Compiling Huskybse
    By: Avon to Al on Sun Jan 10 2021 07:42 pm

    Yes, I have both of those options enabled although I don't use them.
    If I use hptzip then htick can't get file descriptions from the
    file_id.diz when tossing files, so I just use zip and unzip.

    OK I'll use them then but may need a hand to bypass should I hit the same issues.

    Yep, it's good to have both enabled in case you need them. hptzip only comes into play if you set your config to use it in the archiver setup. If you use it hpt can compress and decompress with the need of zip and unzip.

    it seems a pain to have the config there if I am putting the rest of the files in a dir called husky, I'm wondering if I should change that link. Hmm

    The huskymak.cfg should be in your husky root directory, all your husky builds will use it.

    I saw you were using huskyutil, that software was buggy at one time so I switched to using sqpack. Those bugs may have been resolved in the mean time, I don't know but sqpack works with Squish, JAM and *.MSG areas. I have always used sqpack with good results.

    Ttyl :-),
    Al

    ... This message has been UNIXized for your protection.
    --- SBBSecho 3.12-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Al@21:4/106.1 to Avon on Sat Jan 9 23:49:21 2021
    Re: Re: Compiling Huskybse
    By: Avon to Al on Sun Jan 10 2021 08:30 pm

    2) I think I duffed up a setting in the huskymak.cfg and set CFGDIR=$(PREFIX)/hub/husky

    You can take the $(PREFIX) out and put your own path if you like.

    CFGDIR=/path/to/my/husky/directory

    I was wanting the config to go to hub/husky but forgot about the prefix variable which was /usr/local

    Yes, you can change that to whatever you are comfortable with.

    /usr/local/hub/husky does not seem to be created nor does there seem to be a config file in there, should I have expected to see a default one there?

    No, you will need to create that directory along with a config of your own.

    There are examples to start you off in hpt/config and htick/misc. There are examples in other directories too.. you'll need to work through that.

    I can send you my configs in a zip if you'd like to have a look.

    3) If I were to start over now by making a change to the config file, am I safe to remove the compiled files from /usr/local/bin (do I do that first?) then run the make and make install process again thereafter?

    Yes, you can just delete them and start fresh. I like the binary files in /usr/local/bin since that directory is on the path. You can put them anywhere but if they are not on the path you have to use ./hpt or ./htick to run them.

    Ttyl :-),
    Al

    ... Wars are not fought to decide who is right - only who is left
    --- SBBSecho 3.12-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Avon@21:1/101 to Al on Sun Jan 10 20:56:11 2021
    On 09 Jan 2021 at 11:35p, Al pondered and said...

    The huskymak.cfg should be in your husky root directory, all your husky builds will use it.

    Thanks, yep all understood :)

    I saw you were using huskyutil, that software was buggy at one time so I switched to using sqpack. Those bugs may have been resolved in the mean time, I don't know but sqpack works with Squish, JAM and *.MSG areas. I have always used sqpack with good results.

    I pulled down a copy of hptutil from Git as I saw Deon was using it in his build. I'm not sure what Dan uses but think it's the same.

    When I built it, I ran the executable and it came back with this

    hptutil/lnx 1.9.0-cur 2011-03-09

    Usage: hptutil [options]
    Options: sort - sort unread messages by time and date
    link - reply-link messages
    purge - purge areas
    pack - pack areas
    fix - fix base (hptutil fix -? for more help)
    -j - link Jam areas by CRC (great speed-up)
    -k - keep import.log file
    -q - quiet mode (no screen output)
    -i <filename> - alternative import.log

    So it looks like it's old circa 2011... Hmmm..

    I'll grab sqpack and compile it also... but I'm going to wait until I read
    your advice about my cfg gaffe and the best way for me to recompile (delete files already created? etc.)

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Al@21:4/106 to Avon on Sat Jan 9 23:52:04 2021
    Hello Avon,

    I ran the make and sudo make install and found a ton of compiled
    programs in /usr/local/bin with root group/owner privs.

    I forgot #1.

    1) can I move them to my dir of choice and change them to my user
    group and ownership?

    Yes, they can go anywhere. /usr/local/bin is convenient since that dir is on your path, you can run those commands from any directory.

    Yes, you can change owner/group privs and they'll work as long as they stay executible.

    There will be files in your /usr/local/lib or lib64 directory also. Your husky builds depend on them.

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Avon@21:1/101 to Al on Sun Jan 10 21:03:10 2021
    On 09 Jan 2021 at 11:49p, Al pondered and said...

    2) I think I duffed up a setting in the huskymak.cfg and set CFGDIR=$(PREFIX)/hub/husky

    You can take the $(PREFIX) out and put your own path if you like. CFGDIR=/path/to/my/husky/directory

    OK thanks

    /usr/local/hub/husky does not seem to be created nor does there seem a config file in there, should I have expected to see a default one t

    No, you will need to create that directory along with a config of your own.

    OK cool, thanks I wasn't sure if it was going to create a default cfg file
    for me.

    There are examples to start you off in hpt/config and htick/misc. There are examples in other directories too.. you'll need to work through that.

    I can send you my configs in a zip if you'd like to have a look.

    Thanks yes please, I did have some from you ages ago but it wouldn't hurt to see them now, so thanks.

    3) If I were to start over now by making a change to the config file, safe to remove the compiled files from /usr/local/bin (do I do that first?) then run the make and make install process again thereafter?

    Yes, you can just delete them and start fresh. I like the binary files in /usr/local/bin since that directory is on the path. You can put them anywhere but if they are not on the path you have to use ./hpt or
    ./htick to run them.

    You make a good point about pathing. I may do the same then. If I do move
    I guess I need to change the group:owner to me and find a way to add the dir
    I move them to the path

    So because I compiled the first attempt of all my binaries with the wrong pathing to my intended config file, those compiled binaries need to be
    deleted and recompiled else they will always look to the wrong location for config info - is that right?

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Al@21:4/106 to Avon on Sun Jan 10 00:14:04 2021
    Hello Avon,

    When I built it, I ran the executable and it came back with this

    hptutil/lnx 1.9.0-cur 2011-03-09

    Usage: hptutil [options]
    Options: sort - sort unread messages by time and date
    link - reply-link messages
    purge - purge areas
    pack - pack areas
    fix - fix base (hptutil fix -? for more help)
    -j - link Jam areas by CRC (great speed-up)
    -k - keep import.log file
    -q - quiet mode (no screen output)
    -i <filename> - alternative import.log

    So it looks like it's old circa 2011... Hmmm..

    Yes, it's hasn't been maintained in a while.

    The link option above is available in hpt. When tossing run "hpt toss link".

    I never used hptutil based on something I read at one time so I don't know what the problems were or if they have been corrected.

    sqpack only maintains message bases. It does a purge and pack all at once. One area at a time or all areas. It does not have a -fix option. I have never had to fix a hpt message base in all these years.. so.. :)

    I'll grab sqpack and compile it also... but I'm going to wait until I
    read your advice about my cfg gaffe and the best way for me to
    recompile (delete files already created? etc.)

    Better advice must come from someone who uses hptutil, or someone who writes/maintains it.

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Avon@21:1/101 to Al on Sun Jan 10 21:34:12 2021
    On 10 Jan 2021 at 12:14a, Al pondered and said...

    Better advice must come from someone who uses hptutil, or someone who writes/maintains it.

    Thanks for the all info today. I'm going to head to bed now but will carry on tomorrow :)

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Al@21:4/106 to Avon on Sun Jan 10 00:27:32 2021
    Hello Avon,

    Thanks yes please, I did have some from you ages ago but it wouldn't
    hurt to see them now, so thanks.

    OK, I'll zip them up and put them in your inbound in a minute here.

    You make a good point about pathing. I may do the same then. If I do
    move I guess I need to change the group:owner to me and find a way to
    add the dir I move them to the path

    Yep, that is a good place for them. Everything I build myself goes into /usr/local/bin so after a time it can get busy in there.. :)

    So because I compiled the first attempt of all my binaries with the
    wrong pathing to my intended config file, those compiled binaries need
    to be deleted and recompiled else they will always look to the wrong location for config info - is that right?

    Yes, or you can run hpt with the -c option and point it to another location..

    hpt -c /some/other/directory/config toss link

    You can also set a FIDOCONFIG environment variable, but it's simpler if you build the husky stuff with a good config path and filename at build time, then you never need to worry about that.

    Remember, tparser is your friend when putting your config togther.

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Avon@21:1/101 to Al on Sun Jan 10 21:58:29 2021
    On 10 Jan 2021 at 12:27a, Al pondered and said...

    So because I compiled the first attempt of all my binaries with the wrong pathing to my intended config file, those compiled binaries nee to be deleted and recompiled else they will always look to the wrong location for config info - is that right?

    Yes, or you can run hpt with the -c option and point it to another location..

    I logged into the file manager as root and removed the compiled files from /usr/local/bin

    Then I made the change to the cfg file then went into huskylib folder and ran make again... this time make just says 'nothing to be done for all' so it's like I can rerun the make process... am I missing something?

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Al on Sun Jan 10 21:59:49 2021
    On 10 Jan 2021 at 09:58p, Avon pondered and said...

    I logged into the file manager as root and removed the compiled files
    from /usr/local/bin

    Then I made the change to the cfg file then went into huskylib folder
    and ran make again... this time make just says 'nothing to be done for all' so it's like I can rerun the make process... am I missing something?

    That should read 'I can't rerun make'

    Do I need to do another git clone of each repo to reset the original files first?

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Black Panther@21:1/186 to Avon on Sun Jan 10 02:50:54 2021
    On 10 Jan 2021, 09:59p, Avon said the following...

    That should read 'I can't rerun make'

    Do I need to do another git clone of each repo to reset the original filesfirst?

    Try running:
    make clean

    Then retry make.


    ---

    Black Panther(RCS)
    aka Dan Richter
    Castle Rock BBS
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    http://github.com/DRPanther
    The sparrows are flying again...

    --- Mystic BBS v1.12 A47 2021/01/05 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com - (21:1/186)
  • From Avon@21:1/101 to Black Panther on Sun Jan 10 23:09:59 2021
    On 10 Jan 2021 at 02:50a, Black Panther pondered and said...

    Try running:
    make clean

    Then retry make.

    thanks, ive shutdown the pc for tonight but will give that a go tomorrow morning :-)

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From deon@21:2/116 to Avon on Sun Jan 10 22:34:12 2021
    Re: Re: Compiling Huskybse
    By: Avon to deon on Sun Jan 10 2021 05:27 pm

    Howdy,

    Questions on a few of the git repos you pull in / use...
    htpzip - so this is used to offer zip/unzip within HPT without the need to install infozip or similar? It would also explain
    the switch change you make
    in your config file for huskybse.

    Yes, I dont recall why I added hptzip - because my image also has zip/unzip installed anyway. There was something I was doing with husky and it complained about no hptzip, so I added it.

    hptutl - this looks like the jam packer, purge etc. tools, I'm picking I should get these as part of this 'standard' build?

    Yes, I believe so.

    htpkill - what do you use this for? Do I need it?
    areastat / fidostat / nltools - I take it are all worth getting for the info they offer?

    Actually, when I built the container, I would have built it for all the "husky" tools - hence why they are added. I dont necessarily use them, but I added them to the container in case somebody else also used it.

    Remember, docker container images represent "an application", and are by definition, "ready, installed for use". They are also a starting point for somebody who wants to add onto the image, or use the image in their personal/customised environment "as is".

    So my "fidohub" container is just that, tools to be a fido hub. So if I discover a tool (of value) that is missing, I'll most likely add it...

    When you get sick of compiling and configuring and installing, just pull my container and you'll save all that time ;)

    ...лоеп

    ... You don't have to think too hard when you talk to teachers.
    --- SBBSecho 3.11-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From Al@21:4/106.1 to Avon on Sun Jan 10 06:33:18 2021
    Re: Re: Compiling Huskybse
    By: Avon to Al on Sun Jan 10 2021 09:59 pm

    Do I need to do another git clone of each repo to reset the original files first?

    You can just delete them an reclone, but you just need to run "make clean" and run make again.

    Ttyl :-),
    Al

    ... "Keyboard? How quaint!" - Scotty
    --- SBBSecho 3.12-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Avon@21:1/101 to deon on Mon Jan 11 09:55:36 2021
    On 10 Jan 2021 at 10:34p, deon pondered and said...

    Yes, I dont recall why I added hptzip - because my image also has zip/unzip installed anyway. There was something I was doing with husky
    and it complained about no hptzip, so I added it.

    OK thanks, I have done the same.

    hptutl - this looks like the jam packer, purge etc. tools, I'm pickin should get these as part of this 'standard' build?

    Yes, I believe so.

    Do you use this tool?

    When you get sick of compiling and configuring and installing, just pull my container and you'll save all that time ;)

    :)

    For now I want to learn by doing, so will likely keep what I set up running
    on my computer but will play with docker as well.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Al on Mon Jan 11 09:56:09 2021
    On 10 Jan 2021 at 06:33a, Al pondered and said...

    You can just delete them an reclone, but you just need to run "make
    clean" and run make again.

    Thanks, Dan also let me know too :) I'm playing again now.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From deon@21:2/116 to Avon on Mon Jan 11 15:57:49 2021
    Re: Re: Compiling Huskybse
    By: Avon to deon on Mon Jan 11 2021 09:55 am

    Howdy,

    hptutl - this looks like the jam packer, purge etc. tools, I'm pickin should get these as part of this 'standard'
    build?
    Yes, I believe so.
    Do you use this tool?

    I havent yet - but I probably should soon.

    The hub has been running for 9 months or so, so the message bases are not that big. I'll probably start playing with that util when I get a free moment.

    ...лоеп

    ... Think like a man of action, act like a man of thought.
    --- SBBSecho 3.11-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From Black Panther@21:1/186 to deon on Mon Jan 11 00:51:16 2021
    On 11 Jan 2021, 03:57p, deon said the following...

    Do you use this tool?

    I havent yet - but I probably should soon.

    The hub has been running for 9 months or so, so the message bases are
    not that big. I'll probably start playing with that util when I get a
    free moment.

    I haven't even looked at that either... I still need to do something with the log files too... They grow fast!


    ---

    Black Panther(RCS)
    aka Dan Richter
    Castle Rock BBS
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    http://github.com/DRPanther
    The sparrows are flying again...

    --- Mystic BBS v1.12 A47 2021/01/05 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com - (21:1/186)
  • From deon@21:2/116 to Black Panther on Mon Jan 11 19:58:00 2021
    Re: Re: Compiling Huskybse
    By: Black Panther to deon on Mon Jan 11 2021 12:51 am

    Howdy,

    I haven't even looked at that either... I still need to do something with the log files too... They grow fast!

    They do!

    I actually have logrotate in the image, and cron - so I map in a cron.daily into the image that rotates the logs and stores them in an "old" directory.

    Yell out if you want more detail...

    ...лоеп

    ... File not found, I'll load something *I* think is interesting.
    --- SBBSecho 3.11-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From Black Panther@21:1/186 to deon on Mon Jan 11 02:31:00 2021
    On 11 Jan 2021, 07:58p, deon said the following...

    I actually have logrotate in the image, and cron - so I map in a cron.daily into the image that rotates the logs and stores them in an "old" directory.

    Yell out if you want more detail...

    AHHHHH! ;)

    Yes, any detail you could send would be great. I've been moving them manually, when I notice they're getting close to 100MB...

    I've never used logrotate, but I did notice you had it in there. :)

    Thanks,


    ---

    Black Panther(RCS)
    aka Dan Richter
    Castle Rock BBS
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    http://github.com/DRPanther
    The sparrows are flying again...

    --- Mystic BBS v1.12 A47 2021/01/05 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com - (21:1/186)
  • From Oli@21:3/102 to Avon on Mon Jan 11 12:26:19 2021
    Avon wrote (2021-01-10):

    do I need smapi if I plan to to run JAM bases? Or is it best to have this as an option even if not used?

    Maybe it has been already been answered in another reply...

    smapi is the Squish API with added JAM support. So you need smapi for JAM bases.

    ---
    * Origin: (21:3/102)
  • From deon@21:2/116 to Black Panther on Tue Jan 12 10:15:29 2021
    Re: Re: Compiling Huskybse
    By: Black Panther to deon on Mon Jan 11 2021 02:31 am

    Yes, any detail you could send would be great. I've been moving them manually, when I notice they're getting close to 100MB...

    OK...

    1) map in a cron.daily (or cron.weekly/hourly, etc) directory into the container
    docker run .. -v ${SRC}/cron/cron.daily:/etc/cron.daily

    2) In cron.daily I have a logrotate, nodelist (running makenl daily) and a queuestatus - that posts the hub queue to the stats echo. logrotate is:

    #---START
    #!/bin/sh

    # skip in favour of systemd timer
    if [ -d /run/systemd/system ]; then
    exit 0
    fi

    # this cronjob persists removals (but not purges)
    if [ ! -x /usr/sbin/logrotate ]; then
    exit 0
    fi

    /usr/sbin/logrotate /etc/logrotate.conf
    EXITVALUE=$?
    if [ $EXITVALUE != 0 ]; then
    /usr/bin/logger -t logrotate "ALERT exited abnormally with [$EXITVALUE]"
    fi
    exit $EXITVALUE
    #---END

    3) Inside the container, I already have a /etc/logrotate.d/fido, which assumes the logs are all in /var/log/fido, and will rotate them to /var/log/fido/old/.
    My /var/log/fido is a mount with -v ${SRC}/log:/var/log/fido - so on my host they are all in ${SRC} (/srv/docker/fidohub)

    If your logs are in a different place, or want to use a different /etc/logrotate.d/fido, you can map in your replacement with -v /src/to/your/fido:/etc/logrotate.d/fido

    You should be good to go...



    ...лоеп

    ... A self-starting oscillator won't.
    --- SBBSecho 3.11-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From Black Panther@21:1/186 to deon on Mon Jan 11 16:57:38 2021
    On 12 Jan 2021, 10:15a, deon said the following...

    3) Inside the container, I already have a /etc/logrotate.d/fido, which assumesthe logs are all in /var/log/fido, and will rotate them to /var/log/fido/old/.My /var/log/fido is a mount with -v ${SRC}/log:/var/log/fido - so on my hostthey are all in ${SRC} (/srv/docker/fidohub)

    You should be good to go...

    Great! Thank you so much.

    When does this execute? Is it a midnight when systemd will run it?

    Thanks again.


    ---

    Black Panther(RCS)
    aka Dan Richter
    Castle Rock BBS
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    http://github.com/DRPanther
    The sparrows are flying again...

    --- Mystic BBS v1.12 A47 2021/01/05 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com - (21:1/186)
  • From deon@21:2/116 to Black Panther on Tue Jan 12 12:16:33 2021
    Re: Re: Compiling Huskybse
    By: Black Panther to deon on Mon Jan 11 2021 04:57 pm

    When does this execute? Is it a midnight when systemd will run it?

    This is controlled by /etc/crontab (inside the container) - so the cron.daily runs at 6.25am.

    You probably want to set your timezone (/etc/localtime) - which will be Australia/Melbourne, unless you have overridden it.

    If you want, you can "extend" the image that you get from me - I can give you some tips (if you arent already doing that) - instead of mapping in the overrides with -v on the command line. Both work...

    ...лоеп

    ... WWhhaatt ddooeess dduupplleexx mmeeaann??
    --- SBBSecho 3.11-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From Black Panther@21:1/186 to deon on Mon Jan 11 18:56:24 2021
    On 12 Jan 2021, 12:16p, deon said the following...

    This is controlled by /etc/crontab (inside the container) - so the cron.dailyruns at 6.25am.

    Awesome! I'm looking forward to not having to remember to back up the logs! ;) Thanks again!

    You probably want to set your timezone (/etc/localtime) - which will be Australia/Melbourne, unless you have overridden it.

    We've already overridden it.

    If you want, you can "extend" the image that you get from me - I can
    give yousome tips (if you arent already doing that) - instead of mapping in theoverrides with -v on the command line. Both work...

    Everything seems to be running smoothly by using the overrides. I'll just keep it going that way.


    ---

    Black Panther(RCS)
    aka Dan Richter
    Castle Rock BBS
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    http://github.com/DRPanther
    The sparrows are flying again...

    --- Mystic BBS v1.12 A47 2021/01/05 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com - (21:1/186)