REPLY: 635.fido_echolist@1:124/5016 28b6a099
MSGID: 2:250/1@fidonet 645192ab
CHRS: UTF-8 2
TZUTC: 0100
TID: MBSE-FIDO 1.0.8.3 (Linux-x86_64)
Hello Nigel and Rob!
Tuesday May 02 2023 14:44, you wrote to me:
> On Tue, 2 May 2023 17:01:56 +0100
> "Vincent Coen" (2:250/1) wrote:
>> Hello All!
>>
>> Right well no one has expressed an interest in taking over the Elist
>> service along with the Pi it is running on.
> What is involved and what sort of time commitment? I don't think I'd
> want a Pi but since I use Synchronet on Linux, anything is possible.
> It depends on the involvement.
A few scenarios here :
1. If you have a running Linux system say with a mailer / bbs running and use
Router for your broadband connection then the following options :
A. Set up BBS system two running on same kit with router port forwarding set
for say port 24555 (can be another) to point to system two running mbse with
the elist system in operations using fixed IP address.
This doing :
1. Installing bbs mbse to it and compiling the system
2. Loading the elist system from archive to the correct directory.
3. Re install mbse ( make install etc).
4. Install from your Linux distro's software service the Cobol compiler and
secondary tools as per the manual.
5. Compile the Elist software and copy the elist programs to the mbse bin
folder.
6. Start mbse, log in as user mbse via a terminal program.
change to the correct folder and start the elist service.
Note that the fact that you are running two system that pass echos and archive
files between this will work as if they are different systems in different
locations etc - can even go between the systems using your broadband
connection. It will make it easier if your system connects toyour router via a
LAN cable but wi-fi would also work.
Job done for option A.
This not a lot different except you are using a baby computer system to run
the
Elist system :
B. Take over the Raspberry Pi with port 24555 again with your router set for
port forwarding for 24555 (can be another) to connect to fix IP address.
The Pi runs a Debian OS from Raspberry service as a 64 bit version with auto
updating services turned on BUT does not auto reboot as that must be done
manually - I do so every 30 - 90 days or when I think about it.
The Pi then needs to be logged in to,
1. Reboot and
2. start the Elist service (but could be auto started) when needed.
Both above can assume that you operate your current system with fixed IP
address or using DCHP service.
The port forwarding service needs to know the IP address so that is the reason
for a Fixed address, for example the Pi is using address 192.168.1.75 (could
be
another one though).
If running the system along with your existing service - this would not be an
issue as the mbse bbs/mailer system is a light resource system.
The Elist system regardless of where running will need to be changed so that
its uplink is changed to your primary system ( or could be your current uplink
- but this way keep it all tight ).
Currently the Elist system uses fido address 2:25/21 but this could be changed
to match to your country as needed such as 1:1/21 ( which it was I think when
Ben Rickley was running it - subject to Nick Andre zone 1 co-ordinator.
I have written a detailed document as a .pdf file that goes in to more precise
details of the when what evers etc.
There is no reason why a second system cannot be in operation as a back up
initially until being fully operational over some weeks etc.
Time requirements :
OK, apart from fixing any reported or seen bugs in the Elist software and
updating the two programs as needed then copying the executables to the mbse
bin folder and restarting the elist service (yes I can still do this and pass
the fixes to you).
It is around one hour a month or less and that mostly to check that the Pi has
been updated - or run the distro update service and some times rebooting it
but I don't very often.
That more or less it.
Most of the work is setting the system up for the change of primary fido
address, uplink address, make sure the uplink system get echos : ELIST,
ECHOLIST and file area ECHOLIST as your primary system will act as the uplink
for these out to the world via your uplink. I am going to assume here that the
Echos you get already so it is just the one file area that the Elist system
produces an archive monthly and will send out to its uplink (your primary
system) who in turn asses it onwards.
I cannot give a time for this but allow for 1 - 3 hours depending on how happy
you are with computers. Fido services and your uplink etc.
It would help if you have compiled the odd program etc, using gcc or similar.
Let me know you addresses and I will send a copy of my get it all working
manual - if nothing else it will help me proof read the document to make sure
have answered all possible questions - well I always can live in hope :)
I can send via fido mailer etc or via email as the pdf file is under 1 MB.
I must read it again to check it looks complete.
Vincent
--- Mageia Linux v8 X64/Mbse v1.0.8.3/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
SEEN-BY: 1/120 123 15/0 18/0 25/0 90/1 103/705 105/81 106/201 116/116
SEEN-BY: 120/616 123/0 10 25 115 131 160 170 180 200 755 3001 124/5016
SEEN-BY: 129/305 135/300 153/757 7715 154/10 30 40 50 700 203/0 218/700
SEEN-BY: 220/90 221/0 1 6 222/2 226/18 30 227/114 201 229/110 112
SEEN-BY: 229/113 200 206 307 317 400 426 428 470 664 700 240/1120
SEEN-BY: 240/5832 250/0 1 2 3 4 5 6 8 11 12 13 261/1466 263/0 266/512
SEEN-BY: 275/1000 280/464 5003 282/1038 292/789 854 8125 299/6 301/1
SEEN-BY: 317/3 320/219 322/757 335/364 341/66 234 342/200 396/45 423/120
SEEN-BY: 460/58 467/4 633/280 712/848 1321 770/1 2320/105 3634/0 12
SEEN-BY: 3634/24 27 56 57 119 5020/1042
PATH: 250/1 3634/12 154/10 280/464 292/854 229/426
|
