Okay, playing around a little... Raspbary Pi and SynchroNET. I have a few questions.
I really don't know much about Linux, whatever flavour, the docs to get SynchroNET to install on my Pi box was easy as 3.14... There are a few issues, one being that the ports seem to complain a lot. Even if I move them... ie ftp=2121 or whatever. Is there a simple way to get the BBS to bind and listen to ports in the higher range??
Binkit, how do I get this to run/work??
I see there an INI or a CFG file??
Is it auto loaded or do I have to run it in a different process??
I really don't know much about Linux, whatever flavour, the docs to get SynchroNET to install on my Pi box was easy as 3.14... There are a few issues, one being that the ports seem to complain a lot. Even if I move them... ie ftp=2121 or whatever. Is there a simple way to get the BBS to bind and listen to ports in the higher range??
Binkit, how do I get this to run/work?? I see there an INI or a CFG file?? Is it auto loaded or do I have to run it in a different process??
Lets just say I can make the BBS work in Pi, I see there is a lot of activity going on with the programming updates how easy/hard is it to update my Pi box??
Lets just say I can make the BBS work in Pi, I see there is a lot of activity going on with the programming updates how easy/hard is it to update my Pi box??
I update almost daily but if your BBS is working as you like there is no need to update. I find the process takes about 5 minutes here but you
may need more build time on a Pi.
On linux only root can bind ports <=1024. If your ports are above that they should bind ok.
You can change the port numbers in your ctrl/sbbs.ini and services.ini files (if you prefer to use different port numbers) - but you don't have to use high port numbers if you don't want.
I'lllook into these files, I may just seek some help how to run the BBS logged in under the root.... or whatever that's called.
Al wrote to IB Joe <=-
I would leave the ports standard whenever possible. In your
ctrl/sbbs.ini if you uncomment and change the user and group to the
user and group you are running as you can start sbbs with sudo and it
will bind the ports and run as that user. In my sbbs directory I run
"sudo exec/sbbs" and my BBS seems to run well like that.
... Tact: knowing how far to go too far.
Nightfox wrote to Al <=-
I looked up reasons why only root can use ports >1024, but even after reading what I found, I'm still not sure there's a clear reason why
that was done. I'd think you'd want to run your public-facing servers
as a non-root user to reduce the possibility of someone gaining root access to your system.
What is the process to update it on a Pi/Linux box??I don't need to be current all the time... but if I were to do it what is the process??
BTW, how many users have you had on at one time with your Pi Box??
I looked up reasons why only root can use ports >1024, but even
after reading what I found, I'm still not sure there's a clear
reason why that was done. I'd think you'd want to run your
public-facing servers as a non-root user to reduce the possibility
of someone gaining root access to your system.
I think it goes back to the days when you had many (human) non root users on Unix systems with shell accounts logged in remotely. You obviously wouldnn't have wanted some random user setting up a mail server or DNS server, for example. So, the restriction would have ensured that only the administrator had that privilege. Linux was written to be a Unix clone on the 80386 (and later) processors at the time, so it initially inherited the characteristics of Unix for the most part. But times have changed. Ordinary shell users are now fairly rare. Non root users are now mostly for running low privilege processes (basically everything that doesn't need full access to the system), or they may have limited (FTP for exampe) access to upload files to a webhost on a shared host.
Nightfox wrote to Tony Langdon <=-
I think it goes back to the days when you had many (human) non root users on Unix systems with shell accounts logged in remotely. You obviously
I suppose that makes sense. I remember when ISPs used to offer shell access and some user space on their host machine. I never really knew what to do with the shell access, but one time (when I was still using
dialup), I noticed that I could sometimes download a file faster by
first downloading it to my ISP space via FTP or wget (on the command line), as the file would download there reqlly quick, and then I'd download the file from my ISP account space via FTP (which would go
fairly fast). I used to also use my ISP space for hosting small web
pages that I'd want to share with people, and sometimes I'd use my ISP space for photo hosting, so I'd have links to the photos that I could paste on web forums online, etc.. I suppose now people can use things like Photobucket, etc. But services like that may need to charge
money if you have more than a certain amount of content on their
server..
I'lllook into these files, I may just seek some help how to run the BBS logged in under the root.... or whatever that's called.
Re: Re: SynchroNET & Pi
By: IB JOE to Digital Man on Mon Mar 12 2018 13:29:09
Umm, afaik its easier running sbns under root than it is any other user.
Umm, afaik its easier running sbns under root than it is any other
user.
Tried the root thing and it didn't work out too well for me. I missing a few things... my complete lack of understanding is getting in the way.
sudo ~/sbbs/exec/sbbs and it craps out... environment issues does not know where the ~/sbbs/ctrl directory is. In synchronet wiki page on how to install Synchronet on a Pi stated that I should use an export command... export SBBSCTRL=~/sbbs/ctrl ... doesn't help me too much here.
I am missing the fundimentals.... frustrating!!!
way.Umm, afaik its easier running sbns under root than it is any other
user.
Tried the root thing and it didn't work out too well for me. I missing a few things... my complete lack of understanding is getting in the
sudo ~/sbbs/exec/sbbs and it craps out... environment issues does not know where the ~/sbbs/ctrl directory is. In synchronet wiki page on how to install Synchronet on a Pi stated that I should use an export command... export SBBSCTRL=~/sbbs/ctrl ... doesn't help me too much here.
Re: Re: SynchroNET & Pi
By: KK4QBN to IB JOE on Mon Mar
12 2018 10:30 pm
Re: Re: SynchroNET & Pi
By: IB JOE to Digital Man on Mon Mar 12 2018 13:29:09
Umm, afaik its easier running sbns under root than it is any other user.
Tried the root thing and it didn't work out too well for me. I missing a few things... my complete lack of understanding is getting in the way.
sudo ~/sbbs/exec/sbbs and it craps out... environment issues does not know where the ~/sbbs/ctrl directory is.
In synchronet wiki page on how to
install Synchronet on a Pi stated that I should use an export command... export SBBSCTRL=~/sbbs/ctrl ... doesn't help me too much here.
I am missing the fundimentals.... frustrating!!!
| Sysop: | MCMLXXIX |
|---|---|
| Location: | Prospect, CT |
| Users: | 325 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 09:41:08 |
| Calls: | 510 |
| Messages: | 220574 |