TZUTC: -0500
MSGID: 13.fido_slackwar@1:135/115 2c906973
REPLY: 1:320/219@fidonet 682aab4b
PID: Synchronet 3.21a-Linux master/97e1d3922 May 08 2025 GCC 14.2.0
TID: SBBSecho 3.25-Linux master/97e1d3922 May 08 2025 GCC 14.2.0
BBSID: PALANTIR
CHRS: CP437 2
FORMAT: flowed
-=> Andrew Leary wrote to Dan Clough <=-

 DC> Well, going on three years now since the last post here.  Not sure why
 DC> this echo doesn't get any attention.  I know there are other Slackers
 DC> still out there.  Let's hear something from ya!

 AL> I'm running Slackware 15.0 on my main BBS system.  I have updated it
 AL> several times with security patches that came out after 15.0 was
 AL> released.

Yep always a good idea to keep up with the security updates.  I 
certainly do that too with my remaining Slackware systems.

 AL> I also have a Devuan Linux 5/daedalus system running that I use for
 AL> testing MBSE BBS with Debian derived distributions.  I chose Devuan
 AL> because it is one of the few Debian type distributions that doesn't
 AL> force using systemd.

I also generally try to avoid systemd.  About a year ago I've started 
using "MX Linux" as my daily driver OS.  It's derived from MEPIS/AntiX 
and was (the last time I looked) the "leading" Linux distro on 
Distrowatch.com.  I know that doesn't mean a whole lot...  But it is 
very nice, with some nice "tools" to make some tasks easier, and it's 
Debian-based so you get the apt stuff, but no systemd.  I've really come 
to like it a lot.

 DC> I'm thinking 15.1 can't be more than 6 months away now...  ;-)

 AL> We can certainly hope...

And unfortunately that's about all we CAN do.  Getting any actual "news" 
is just not gonna happen.  I've always thought Patrick could/should do 
better with "marketing" his product, but I guess he doesn't care much 
about that side of things.  As I said in a post yesterday, my BBS is 
running on -current at the moment, as it's newer hardware and X will not 
run on it with 15.0.  Kernel support for the video hardware, I'm pretty 
sure, and of course it could be overcome with a newer custom-compiled 
kernel.  While I used to do that all the time, it's been years and I 
just don't want to remember how to mess with that any more.  I don't 
update it because it's quite likely something will break as a result, so 
I'm hoping to use 15.1 eventually and get on a normal security/update 
schedule again.

Somebody tell Patrick we're getting impatient...  ;-)



... Backup not found: (A)bort (R)etry (P)anic
=== MultiMail/Linux v0.52
--- SBBSecho 3.25-Linux
 * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
SEEN-BY: 1/120 18/0 50/22 105/81 106/201 123/0 25 180 755 3001 3002
SEEN-BY: 124/5016 128/187 135/0 115 205 220 240 363 366 385 390 391
SEEN-BY: 153/7715 154/30 110 203/0 218/700 220/6 221/0 222/2 226/30
SEEN-BY: 227/114 229/110 114 206 317 400 426 428 470 550 664 700 705
SEEN-BY: 240/1120 1634 5832 8001 8002 8005 250/1 266/512 280/464 291/111
SEEN-BY: 292/8125 301/1 320/219 322/757 341/66 234 342/200 371/0 396/45
SEEN-BY: 460/58 256 1124 5858 467/888 633/280 712/1321 770/1 902/26
SEEN-BY: 2320/105 3634/0 12 56 57 60 119 5020/400 8912 5054/30 5058/104
SEEN-BY: 5075/35
PATH: 135/115 3634/12 240/1120 280/464 460/58 229/426