The package comparison comes up from to time, keep in mind that Debian's 50,000+ packages is not a true number, because most of those packages are split from the main package. Take for example claws-mail, in Debian it has many packages, in Slackware it is one package. Also, Slackware does not strip out/split out dev packages, in Slackware you get the program/package exactly how the original developer(s) intended it. Patches are from the original dev.'s, not package maintainers, not distro maintainers.ruffwoof wrote:
For me it distils down to the cost of giving up on the all-encompassing Debian model/framework in order to not run systemD ... simply isn't viable unless the Slacko or Salix (or whatever) packages model/framework were better than Debians.
With Debian I can run any sub-set combination of 40,000+ pre-built programs that are fixed (frozen) for typically 4 year (through stable and oldstable), that are security updated if/when necessary, all sourced from a single provider and that have been strongly vetted (and perhaps even tweaked) before being admitted to that 'library', and then absorbed (maintained) by that single provider. And in so doing induce great stability (low risk of having to down-tools to investigate and fix the tool (desktop system)). Can Slackware/Salix/whatever provide a similar model/framework? FreeBSD most certainly doesn't.
When you do a full install of Slackware, you have everything you need for whatever purpose you choose to use Slackware. As soon as you log in, you can start building, modifying, running whatever, no assumptions are made about what you want to use it for. A default Slackware setup on install does not even boot into X, you are there at the terminal and the system is waiting for your instructions. Would you like to startx, run from tty, whatever....of course you can enable a DM to automatically start x if you like that better. Salix defaults to GDM, was Slim in the past.
One benefit is it helps to increase security, again recall the openssl disaster, where a package maintainer felt he knew more then the openssl dev.'s and decided to make a "small change". Slackware was never affected by this massive security hole. Its packages are pure vanilla, you get what the program developers intended, and the program works and looks how they intended. Also, services are not started unless you specifically tell it to start, auto starting services before they are configured is another security nightmare.
But I digress, the purpose of this thread is to highlight other options for those currently using Debian that would like not to use systemd, not get into a pissing contest of which is better, longer, or who spells their name better in the snow.
BTW, for those interested, Gnome is not officially supported with Slackware, you will have to add a repo for gnome, PV gave up on Gnome a long time ago. I see that as a benefit, others may not. Slackware works closely with Xfce and KDE dev.'s as well.
PS: further reflection on security: Slackware was used in International Space Station and it is still used by many in corporations and various government(s). Quite popular for development purposes, workstations and servers etc....
Ref: https://www.linuxjournal.com/article/3024?page=0,1