Subj : Re: SSH on BBSes
To   : StormTrooper
From : Arelor
Date : Fri Apr 29 2022 18:07:26

  Re: Re: SSH on BBSes
  By: StormTrooper to boraxman on Fri Apr 29 2022 10:13 am

 >  bo> That could be because people feel that the projects are accessible, and
 >  bo> that the developers are wanting to hear ideas and will actually read an
 >  bo> take seriously feedback and reports.  Probably because they are smaller
 > 
 > For some proportion of the early adopters this might have been the case, and
 > welcome change to M$ of the era. For Joe Mugg users these days... I think
 > you're going to be in the minority with that assertion...there's probably
 > still a percentage that think like that, but it'll bet a shadow of its forme
 > self in the number of nubs out there using it now.
 > 
 > ST

Yes, the ratio of contributors to leechers is dropping down quite fast in
Linux.

Still some distributions follow a very BSD-like model in which a self-contained
base is designed by a small group and the users themselves band together and
build everything else.

Slackware comes to mind. Patrick and a small group of others build Slackware,
but then the rest of the users add 3rd party software to the Slackbuilds
quasi-port system. THe idea is that if you want something to work in Slackware,
you submit a build to Slackbuilds (or any other repo-system) and make it work
yourself.

Afaik Arch has community repositories which work in a similar fashion, and KISS
and CRUX are built so you can mix and match community repositories. In fact the
KISS dev intends you to build your own repository and chain it with other
repositories you may like to use.

The KISS approach may seem niche but it shows the will is there.

Then there are the small BSD in which the standard way of ensuring something
works is patching it and sending the feedback to the mailing lists :-)

--
gopher://gopher.richardfalken.com/1/richardfalken
--- SBBSecho 3.15-Linux
 * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

.