home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   SLACKWARE      Discussions about Slackware Linux      85 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 85 of 85   
   Richard Falken to Dan Clough   
   Re: Hello Slackers!   
   19 May 25 14:38:06   
   
   TZUTC: -0500   
   MSGID: 14.fido_slackwar@1:135/115 2c90beac   
   REPLY: 13.fido_slackwar@1:135/115 2c906973   
   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: ASCII 1   
   FORMAT: flowed   
   NOTE: FSEditor.js v1.105   
     Re: Re: Hello Slackers!   
     By: Dan Clough to Andrew Leary on Mon May 19 2025 08:34 am   
      
    > 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   
      
   Heh, Patrick's comunity management is abysmal. Thankfully, Slackers pick   
   Slackware for other reasons than Patrick's PR skills.   
      
   In practical terms you can use Slackware -release for servers and Slackware   
   -current for workstations and 95% of the times you will be fine. I think the   
   current release model is built on this asumption. It is lame because it means   
   Slackware is de facto a rolling distribution when used for desktops, but at   
   least -current is well maintained.   
      
   Really, reason #1 why I moved from Slackware into OpenBSD is that OpenBSD has   
   a clear release model and technical changes and goals are discussed in the   
   open. Since it is not prone to be infected by the new shiny-thing of the day   
   the Linux world generates it means it won't have weird stuff inserted into its   
   ecosystem from one day to the next.   
      
   IO and hardware support suck, though.   
      
    >   
    > Somebody tell Patrick we're getting impatient...  ;-)   
      
   He knows.   
      
      
   --   
   gopher://gopher.richardfalken.com/1/richardfalken   
   --- 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   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca