Subj : Re: NetBSD 10
To   : Arelor
From : Gamgee
Date : Wed Apr 03 2024 07:43:00

-=> Arelor wrote to Gamgee <=-

 Ar>   Re: Re: NetBSD 10
 Ar>   By: Gamgee to Arelor on Tue Apr 02 2024 08:06 pm

 >  Ar> Everything else is either too effort intensive to run
 >  Ar> reliably, serves a too specific niche (ie. special distributions
 >  Ar> for special tasks) or has unpredictable development paths.

 > I think that's a little too broad.  Slackware has none of those drawbacks,
 > except possibly the variable devel/release cycles.

 Ar> Slackware is the Linux distribution I like the most, mainly
 Ar> because it has a bit of a BSD feel. Still it suffers a bit from a
 Ar> mix of "too effort intensive to run" and "unpredictable
 Ar> development paths".

 Ar> I mean, if you want to use it for anything semi-serious and base
 Ar> Slackware does not have you covered, you will end up compiling
 Ar> any third-party component from source alongside its dependencies
 Ar> yes or yes. Slackware fans have lots of automated tools for doing
 Ar> this and most work great, but having to recompile every single
 Ar> updated package sucks balls. If you have a fleet of computers it
 Ar> gets tedious very fast. There are nice projects that let you
 Ar> build and use your own binary package repositories (look up my
 Ar> article about Slackrepo in Linux Magazine) but at this point you
 Ar> are in the "too effort intensive to run" category.

Okay, no argument with any of that, I guess.  I think we are envisioning 
and talking about two different ways of using Slackware (or BSD), 
though.  I was not talking about commercial or large-fleet-of type use.  
For me, behind my simple home LAN, none of the above is an issue.



.... Gone crazy, be back later, please leave message.
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
 * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

.