LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 05-19-2020, 07:13 PM   #1
DSH_NH
LQ Newbie
 
Registered: Jul 2018
Posts: 15

Rep: Reputation: Disabled
Samba & Including libpam.so.0 in /usr/lib64


I recently installed the official Slackware package of Samba (samba-4.12.2-x86_64-2.txz) and the installation went smoothly. The first time I ran it, I had a hiccup that said it needed libicuuc.so.67. I solved that problem fairly easily installing icu4c-compat-67.1-x86_64-1alien.txz. The next hiccup was more of a roadblock. When I next ran Samba, it now indicated that it could not find libpam.so.0.

After considerable time looking for libpam.so.0, I stumbled across the drumz’s post of 2017 in these forums on how to extract that one file from the libpam package. That solved my problem.

Since Samba is a major and often used package, and at least one other package needs it as well, Matlab, is there any reason why this one file could not be included in /usr/lib64 with the full Slackware -current install? I am not interested in PAM, and if it were not for drumz’s post, I would probably still be floundering or trying to install a lot of files on a trial and error basis that might not work and definitely would not be needed.

I did read the post about “PAM about to be merged in –current” so perhaps this is a short time problem, but I for one do not know that for sure, and as a strictly command line server user of Slackware, I am not sure I would want a full install of PAM to obtain that one file.
 
Old 05-19-2020, 08:11 PM   #2
ehartman
Senior Member
 
Registered: Jul 2007
Location: Delft, The Netherlands
Distribution: Slackware
Posts: 1,631

Rep: Reputation: 845Reputation: 845Reputation: 845Reputation: 845Reputation: 845Reputation: 845Reputation: 845
Quote:
Originally Posted by DSH_NH View Post
I recently installed the official Slackware package of Samba (samba-4.12.2-x86_64-2.txz) and the installation went smoothly. The first time I ran it, I had a hiccup that said it needed libicuuc.so.67.
Did you notice this in the official ChangeLog?
Code:
n/samba-4.12.2-x86_64-2.txz:  Rebuilt.
  Rebuilt to add PAM support.
  Recompiled against icu4c-67.1.

l/icu4c-67.1-x86_64-1.txz:  Upgraded.
  Shared library .so-version bump.
So this samba package needs both icu4c-67.1 (another recent update in -current) AND it needs PAM support as all of -current has now been recompiled against PAM

If you would have updated icu4c-67.1 as well, you wouldn't have needed icu4c-compat for samba (but maybe other packages would, it is a well-known update-breaker).

BTW: even text mode will need PAM for a lot of utils (like login and passwd, from the PAMified shadow package), so do a full update because the merge to PAM support has now taken place, in fact your samba was already one.

Last edited by ehartman; 05-20-2020 at 02:05 AM. Reason: remark about text mode
 
Old 05-19-2020, 09:42 PM   #3
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,962

Rep: Reputation: 4643Reputation: 4643Reputation: 4643Reputation: 4643Reputation: 4643Reputation: 4643Reputation: 4643Reputation: 4643Reputation: 4643Reputation: 4643Reputation: 4643
PAM is already a part of -current. samba from -current should not need icu4c-compat as it should be built against the icu4c included in -current.

It sounds like you might've been mixing packages. Maybe you started with 14.2 and installed some packages from -current, maybe at different times. If you install the samba from -current right now along with icu4c, it will require PAM as that is now included in -current.

If you want to stay PAM free, you'd want to stick with 14.2.
 
Old 05-20-2020, 01:04 AM   #4
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,012

Rep: Reputation: 6743Reputation: 6743Reputation: 6743Reputation: 6743Reputation: 6743Reputation: 6743Reputation: 6743Reputation: 6743Reputation: 6743Reputation: 6743Reputation: 6743
If your machine is running slackware-current, you must at all times avoid hand-picking packages you think you want. Always do an upgrade of all available packages.
On the other hand, if you tried installing a slackware-current package on Slackware 14.2, then that is usually a recipe for disaster. You would be better off downloading the sources for that package and then compiling it yourself on Slackware 14.2.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
slackware64 /usr/lib /usr/lib64 question disturbed1 Slackware 29 02-14-2010 08:05 AM
/usr/local/lib or /usr/local/lib64 rigelan Slackware 9 07-24-2009 06:32 PM
/usr/lib vs /usr/lib64 Johncc330 Slackware 2 07-01-2009 01:04 AM
Location of libraries in /usr/lib/ or /usr/lib64/ in Slackware64 niels.horn Slackware 2 06-24-2009 04:25 AM
Relocat /usr/lib and /usr/lib64 to a different path schokshi Fedora 3 08-30-2005 09:14 PM

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

All times are GMT -5. The time now is 03:27 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration