You can grab the scripts from my homepage,
I've been working on a script that downloads and installs Magicka and BinkD and sets it all up with fsxnet as a new node on 21:1/999. It's
meant for raspberry pi, but should work on debian jessie too.
Richard Menedetter wrote to Apam <=-
Can you add Magicka to an existing standard fido system?
Eg. use existing JAM messagebases, tosser, ticer and let the BBS do the BBS part, and _ONLY_ the BBS part.
Hi Apam!
06 Apr 2017 04:05, from apam -> All:
I've been working on a script that downloads and installs Magicka and BinkD and sets it all up with fsxnet as a new node on 21:1/999. It's meant for raspberry pi, but should work on debian jessie too.
Hmmm ... very interesting.
Can you add Magicka to an existing standard fido system?
Eg. use existing JAM messagebases, tosser, ticer and let the BBS do the BBS part, and _ONLY_ the BBS part.
I haven't taken a look.
Is it compiled by the script?
I hope not that it only downloads ARMv7 code ... will not work on x86 ;))
Hi
I've been working on a script that downloads and installs Magicka and BinkD and sets it all up with fsxnet as a new node on 21:1/999. It's
meant for raspberry pi, but should work on debian jessie too.
I hope to play with this tonight (my time) just got to get to the end of the day.
I hope to play with this tonight (my time) just got to get to the end of day.
If you do get time, you might want to grab the version from the website rather than the one(s) I emailed you. I didn't want to spam you
everytime I fixed something, so the latest one is on the website.
(version 4)
If you do get time, you might want to grab the version from the website rather than the one(s) I emailed you. I didn't want to spam you
everytime I fixed something, so the latest one is on the website.
(version 4)
(version 4)
On 04/07/17, apam pondered and said...
(version 4)
I've run this and it seems to have built things and yet when I try to run the runbbs.sh from within the directory I'm not able to run it. I even set the executable permissions to everyone. Is there a log somewhere I can confirm the software was compiled and built correctly?
Maybe a silly question but are you running with ./ in front of the runbbs.sh so like
if there is a magicka executable in the MagickaBBS folder it should have been built. if the runbbs.sh still doesnt work and the magicka binary is there you can run with
./magicka config/bbs.ini
compilation terminated.
Makefile.raspbian:39: recipe for target 'main.o' failed
make: *** [main.o] Error 1
been built. if the runbbs.sh still doesnt work and the magicka binary is
No I'd say there is no executable there :(
On 04/08/17, apam pondered and said...
been built. if the runbbs.sh still doesnt work and the magicka binary is
Building MagickaBBS and Utilities...
cc -c -o deps/aha/aha.o deps/aha/aha.c -std=gnu99 -I/usr/local/include -I./deps/ -I./deps/libb64-1.2/include -DENABLE_WWW=1 -Ilibmicrohttpd-0.9.52/src/include
cc -c -o inih/ini.o inih/ini.c -std=gnu99 -I/usr/local/include -I./deps/ -I./deps/libb64-1.2/include -DENABLE_WWW=1 -Ilibmicrohttpd-0.9.52/src/include
cc -c -o bbs.o bbs.c -std=gnu99 -I/usr/local/include -I./deps/ -I./deps/libb64-1.2/include -DENABLE_WWW=1 -Ilibmicrohttpd-0.9.52/src/include
cc -c -o main.o main.c -std=gnu99 -I/usr/local/include -I./deps/ -I./deps/libb64-1.2/include -DENABLE_WWW=1 -Ilibmicrohttpd-0.9.52/src/include
main.c:13:27: fatal error: libssh/libssh.h: No such file or directory
#include <libssh/libssh.h>
Can you do
sudo apt-get install libssh-dev
Hi
I've been working on a script that downloads and installs Magicka and BinkD and sets it all up with fsxnet as a new node on 21:1/999. It's meant for raspberry pi, but should work on debian jessie too.
The idea is to make it easier to get Magicka up and running quickly by doing lot of the initial configuration for you.
There are two scripts, one magickapi.sh does all the hard work of downloadin installing and configuring as 21:1/999. There is also updatefsx.sh which can be used to update fsxnet to use an actual node number if you've applied and got one. (It only works with node numbers, not points)
It also creates a few scripts you can use,
* runbbs.sh runs the BBS, this should be run from screen or something like that as it doesn't detach (you can configure it to, but that's for advanced users).
* runbinkd.sh runs BinkD, again run from screen.
* updatebbs.sh pulls the latest from github and builds it
* ftn/magitoss.sh this tosses mail into message bases, it's run automatical by binkd.
* ftn/magiscan.sh this scans for mail in the message bases and sends them t binkd to send out. You can run this manually, via a cronjob or set up inotify-tools to watch for semaphores (this is a bit more complicated).
The BBS will be listening on port 2023 for telnet and port 8080 for HTTP. Ft SSH and magichat servers are not configured by default.
You can grab the scripts from my homepage, http://andrew.pamment.id.au/ or directly here: http://andrew.pamment.id.au/downloads/magickapi4.tar.gz
Andrew
--- MagickaBBS v0.6alpha (Linux/x86_64)--- SBBSecho 2.12-Linux
* Origin: Cauldron BBS - Magicka Test BBS (21:1/125)
Good afternoon,
Tried this on a debian jessie machine. It worked up to just past the point where it obtained the desired packages, including git. After that point, it was not able to install any of them, and then it got a bunch of permission denied and "not found in PATH or not executable" errors.
*
* On Saturday 08 Apr 2017 098 at 01:29 PM,
* Dumas Walker said to apam,
* about Re: Magicka Turn Key ...
*
Pardon my ignorance, what is Magicka? {chuckle}
*
* On Saturday 08 Apr 2017 098 at 01:29 PM,
* Dumas Walker said to apam,
* about Re: Magicka Turn Key ...
*
Pardon my ignorance, what is Magicka? {chuckle}
Good afternoon,
Tried this on a debian jessie machine. It worked up to just past the point where it obtained the desired packages, including git. After that point, it was not able to install any of them, and then it got a bunch of permission denied and "not found in PATH or not executable" errors.
It then tried to change to some directories that did not exist, and tried to compile some things in a directory I was surprised it went looking in (an SB source directory) that were not there.
I did some inspection before attempting to run the script. One thing I noticed is that, after each call to git, it was set up to cd into a director that the script had not created beforehand. I assumed that git would create them but since git never finished installing, it did not.
Not sure why your apt-get failed to install anything, but it did. I have never tried running it from 'sudo', I always su and then run it, so maybe there is something odd on this end for that reason.
Hi
I've been working on a script that downloads and installs Magicka and Bin and sets it all up with fsxnet as a new node on 21:1/999. It's meant for raspberry pi, but should work on debian jessie too.
The idea is to make it easier to get Magicka up and running quickly by doing lot of the initial configuration for you.
There are two scripts, one magickapi.sh does all the hard work of downloadin installing and configuring as 21:1/999. There is also updatefsx.sh which can be used to update fsxnet to use an actual node number if you've applied and got one. (It only works with node numbers, n points)
It also creates a few scripts you can use,
* runbbs.sh runs the BBS, this should be run from screen or something li that as it doesn't detach (you can configure it to, but that's for advanc users).
* runbinkd.sh runs BinkD, again run from screen.
* updatebbs.sh pulls the latest from github and builds it
* ftn/magitoss.sh this tosses mail into message bases, it's run automatical by binkd.
* ftn/magiscan.sh this scans for mail in the message bases and sends the t binkd to send out. You can run this manually, via a cronjob or set up inotify-tools to watch for semaphores (this is a bit more complicated). The BBS will be listening on port 2023 for telnet and port 8080 for HTTP. Ft SSH and magichat servers are not configured by default.
You can grab the scripts from my homepage, http://andrew.pamment.id.au/ o directly here: http://andrew.pamment.id.au/downloads/magickapi4.tar.gz
Andrew
--- SBBSecho 2.12-Linux--- MagickaBBS v0.6alpha (Linux/x86_64)
* Origin: Cauldron BBS - Magicka Test BBS (21:1/125)
*
* On Saturday 08 Apr 2017 098 at 01:29 PM,
* Dumas Walker said to apam,
* about Re: Magicka Turn Key ...
*
Pardon my ignorance, what is Magicka? {chuckle}
An update... I ran the apt-get before running the script and everythingseemed
to work this time. However, both the script to run the bbs, as well as the following, caused nothing to happen:
Dumas Walker said....seem
An update... I ran the apt-get before running the script and everything
ed
to work this time. However, both the script to run the bbs, as well as the following, caused nothing to happen:
Can you add Magicka to an existing standard fido system?Not really.
Eg. use existing JAM messagebases, tosser, ticer and let the BBS do
the BBS part, and _ONLY_ the BBS part.
Yeah nothing is displayed when it's running, so you should be able to telnet to port 2023 when it's running. I guess I should put some output
to let you know it's running as that has come up a couple of times now.
I've just pushed a commit that will display what ports magicka is
running on when you start it up.
You should in theory be able to update with ./updatebbs.sh but that
hasn't been tested yet :)
PS thanks for giving it a go :D
Also, I thought maybe it was because I was installing it on an x86 and not an ARM. :) Tried it on my Pi this morning. It appeared to compile correct, but now I am getting a "Couldn't create socket" error on the Pi. The Pi runs raspbian jessie.
I'm working on Magicka now for the next 30-45 mins, just pulled down script version 5 and running it now, I can see my Rpi did have a dependency that needed updating even just 2 days after running the last update so that inclusion to the script was a good idea.
I've just pushed a commit that will display what ports magicka is running on when you start it up.
You should in theory be able to update with ./updatebbs.sh but that hasn't been tested yet :)
Hmm, that's odd. I wonder if it's because of my IPv6 changes. It's odd becau it runs on both my PI and Paul's PI. So I wonder what is different about you PI. Have you totally disabled IPv6? I'm a newbie with IPv6 I just set it up use dual stack so it listens on both IPv6 and IPv4 but I wonder if it's disabled maybe it wont work.
I have not knowingly disabled it, just as I have not knowingly enabled it on the x86 machine. :) I wonder how would I determine if it was disabled?
I have not knowingly disabled it, just as I have not knowingly enabled it on the x86 machine. :) I wonder how would I determine if it was disabled?
Hmm, I'd say if you didn't specifically disable it it would be enabled.
The problem must be somewhere else, I should really catch the errno
there and print it out.
Something else that may, or may not, matter... it is a 2B and not the newer 3 series of Pi.
Sysop: | Weed Hopper |
---|---|
Location: | Clearwater, FL |
Users: | 12 |
Nodes: | 6 (0 / 6) |
Uptime: | 09:53:08 |
Calls: | 67 |
Calls today: | 1 |
Files: | 50,165 |
D/L today: |
66 files (6,777K bytes) |
Messages: | 279,530 |