SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
A lot of packages have been recompiled to support pam (32, not including the pam package itself), but so far they've been tucked away into testing/packages/PAM: ftp://ftp.osuosl.org/pub/slackware/s.../packages/PAM/
Presumably at some point these packages will be moved out of testing/, but we'll see.
I'm more getting at, will every binary on the system including your own have to be recompiled when pam comes out?
Last edited by redneonglow; 02-28-2020 at 05:35 PM.
Reason: executable->binary
No, I don't think so. If you want to change the way your program authenticates, you would recompile it, but traditional auth should continue to jfw.
Most packages are auth-agnostic, so wouldn't need to be rebuilt. All of my personal projects fall in this category as well. Whether yours do is something only you can say.
No, I don't think so. If you want to change the way your program authenticates, you would recompile it, but traditional auth should continue to jfw.
Most packages are auth-agnostic, so wouldn't need to be rebuilt. All of my personal projects fall in this category as well. Whether yours do is something only you can say.
when I use to install standard slack 14.2 then upgrade system to current via the mirrors. now whenever I install slack I use Bobs current iso, open the mirror to a current sight then upgrade it, sbotools to install my whatever's, and it has a sboupgrade option for when I need it for some apps.
I have always been a fan of, if it aint broke, don't fix it mentality. Upgrading for the sake of upgrading has never made any sense to me. Update or upgrade when it fixes a security issue, improves performance, implements a new feature that is lacking in the version you are using or the software is unsupported in some way - which effectively becomes a security issue.
I upgraded to current because I had issues with openssl and some programs using it. In the end,simply updating openssl did not fix it, presumably because there were other dependencies. So I upgraded to current and I just plan to update every quarter or something unless there is a critical security concern. Updating current daily, weekly or monthly doesn't make any sense to me as everything works, Slackware is only used as an Internet Filtering Server (so nobody logs on for weeks at a time) and Slackware is pretty damn secure.
I would recommend upgrading to current because a lot of software with 14.2 stable is actually years out of date - like openssl. So for me it becomes a security issue.
I would recommend upgrading to current because a lot of software with 14.2 stable is actually years out of date - like openssl. So for me it becomes a security issue.
I wasn't aware of that about 14.2's OpenSSL, but the included versions of MariaDB and PHP are both out of date and unmaintained as well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.