3 ms·
Congratulations on the 30th I am posting this from Slackware 15.0 right now, my main driver, but I do boot a BSD once in a while. If not for Slackware, I woul
by jmclnx 3y ago
Congratulations on the 30th
I am posting this from Slackware 15.0 right now, my main driver, but I do boot a BSD once in a while. If not for Slackware, I would have left Linux for a BSD years ago.
I hope Slackware can avoid all what I believe are crazy changes occurring in Linux Land. Already Slackware was forced to import PAM, but in good Slackware fashion PAM stays out of my way, so not a big deal.
- nequo 3y agoYou haven’t specified which BSD but FreeBSD[1] and NetBSD[2] have used PAM for about twenty years by now, haven’t they? [1] https://docs.freebsd.org/en/articles/pam/ https://docs.freebsd.org/en/articles/pam/ [2] https://www.netbsd.org/docs/guide/en/chap-pam.html https://www.netbsd.org/docs/guide/en/chap-pam.html
- jmclnx 3y agoYes I know :) I have used then all to test what I developed on Slackware for use in work, I like to be sure what I due can work on most "free" OSs. But their PAM, from what I understand is a different code base (bsdpam). But in these cases, PAM is invisible to me too.
- pkulak 3y agoWhat do you like about Slackware? Is it super bare bones? Have they resisted Systemd? If that’s it, why not something like Void? Are “packages” really just tarballs that you extract into /? I have so many questions! Haha
- jmclnx 3y agoThe main reason is it is very easy to set up and maintain. One big thing is I can use grep(1) to find what package a file came from, ls(1) to get a list of packages. No need to remember various obscure commands to search to query what is installed.