LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 02-28-2020, 05:35 PM   #16
redneonglow
Member
 
Registered: Feb 2020
Location: PA
Distribution: Gentoo, Slackware
Posts: 75

Original Poster
Rep: Reputation: 24

Quote:
Originally Posted by ttk View Post
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
 
Old 02-28-2020, 05:46 PM   #17
ttk
Senior Member
 
Registered: May 2012
Location: Sebastopol, CA
Distribution: Slackware64
Posts: 1,038
Blog Entries: 27

Rep: Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484
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.
 
1 members found this post helpful.
Old 02-28-2020, 06:15 PM   #18
redneonglow
Member
 
Registered: Feb 2020
Location: PA
Distribution: Gentoo, Slackware
Posts: 75

Original Poster
Rep: Reputation: 24
Talking

Quote:
Originally Posted by ttk View Post
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.
OK, that's good to know, thank you!
 
Old 02-28-2020, 09:51 PM   #19
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (15 current), Slack15, Ubuntu studio, MX Linux, FreeBSD 13.1, WIn10
Posts: 10,342

Rep: Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242
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.
 
Old 03-01-2020, 05:10 AM   #20
dalacor
Member
 
Registered: Feb 2019
Distribution: Slackware
Posts: 170

Rep: Reputation: Disabled
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.
 
1 members found this post helpful.
Old 03-01-2020, 03:53 PM   #21
redneonglow
Member
 
Registered: Feb 2020
Location: PA
Distribution: Gentoo, Slackware
Posts: 75

Original Poster
Rep: Reputation: 24
Exclamation

Quote:
Originally Posted by dalacor View Post
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.
 
  


Reply

Tags
headless, slackware, slackware-14.2, slackware-current



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Thinking in moving to Debian Davh Debian 31 02-10-2012 02:30 PM
Thinking about moving to Slackware, what do I need to know? swalker23 Slackware 11 05-19-2010 09:08 AM
Thinking of moving from RH to Ubuntu 10.04, what is your opinion? hockeycoach Linux - Software 20 05-04-2010 01:51 AM
I'm thinking of moving to a new distro Cyberman Linux - Distributions 4 12-26-2009 03:16 AM
Thinking of moving to SuSE 8.1 from Redhat 8 shart121 Linux - Distributions 13 10-31-2003 10:59 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:09 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration