Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 40 |
Nodes: | 6 (0 / 6) |
Uptime: | 06:46:42 |
Calls: | 180 |
Calls today: | 4 |
Files: | 118 |
Messages: | 64,351 |
Posted today: | 1 |
Sean Dennis wrote to Dan Clough <=-
Understood. I do have an /etc/inetd.conf on my Slackware boxes, but was trying this MBSE experiment on one running "MX Linux", which I actually like quite a bit. A Debian descendent (via Mepis/AntiX) which doesn't
use 'systemd'. There is no inetd.conf (or xinetd.con) in /etc there... I've done some searching, and it seems it can be installed but isn't
there by default. Interesting. I may give that another try tomorrow.
That may be part of the problem: the initialization script may not have seen MX Linux as a distro and didn't stop to warn you to install
xinitd. If you look closely at SETUP.sh in /mbsebbs-code, you'll see
that MX Linux is not one of the "known" distros and that is why you
have had so many issues.
At a terminal, try running "cat /etc/os-release" and let us know what
it says in MIN_BBS, please. We need all the help we can get.
Understood, and appreciate both of your efforts. I'm interested in this BBS software, as I'm getting a little bored with Synchronet and might start up a second BBS. Don't want to use Mystic and would prefer something Linux-native. I'll update if I can get it going. Thanks for the reply and the info!
Admittedly, MBSE has a learning curve, but once you've mastered it, it
is reliable and functions well.
Let's move this over to MIN_BBS.