libpam.so.0
 

Hi,
Have just installed Matlab 2017 on Slackware64 14.2. When starting the program I get the error "missing libpam.so.0. Have tried to search for solution, but it is difficult to find anything useful. It seems that Slackware up to 14.0 had PAM in /extra which I have tried to compile on 14.2, but that failed.

Can someone point me in the right direction ?

Thanks.

You can give http://www.slackware.com/~vbatts/pam/ try.

Most likely NOT.

Because this project is intended for PAMification of Slackware. Read: a Slackware with a functional PAM authentication.

Same is https://github.com/Dlackware/pam but this one is well maintained. ;)

IF our OP chose the PAMification way to run Matlab, would be interesting to report back how the things work.

BUT, a BIG FAT WARNING: going the system PAMification could render the system unusable on smallest errors, as it plays with the authentication.

PS. Talking about the Slackware PAMification, the curious people can take a look on https://github.com/Dlackware/pam and see that for a minimal implementation is only need to add FIVE packages (including even the Kerberos) and to modify ONE (shadow). That's all, folks!

It is nothing about removing half of Slackware shipped packages, and to add over 500 new ones, like in the case of adopting Plasma 5 and removing KDE4, about which you guys talk with serenity! ;)

5 packages aren't that hard to do oneself if you require that functionality. Plasma 5 is coming, coming someday. Plasma 5 has new krita :D

Octave can do a lot of the things that Matlab can do and its open source:
http://slackbuilds.org/repository/14.2/academic/octave/

I don't want to break my system, but it is important for me to be able to run matlab so I have to try it out.

What happens when I have compiled and installed the packages? What do I need to configure ?

Yet, the old good excuse against PAM. In fact, why you are against PAM? You can explain what damages do to your system?

I tell you in few words: you can not! Because over years around PAM happened to grown layers and layers of false information, spread by no ones, for a mere moment of glory in a public forum. ;)

And like was explained multiple times, adding PAM and Kerberos would be essentially a fork of Slackware, as they spread like a cancer over dependencies.

So, you suggest that thousands guys to FORK the Slackware, every one on his own, just because some lies?

To be honest, I think that the Plasma 5 is simply too big to be included in a moderate sized distribution like Slackware.

Plasma 5 is so big, that IF it will be adopted, there would be no Slackware anymore, but some Plasmaware. Just like the Android: a "rich" and huge desktop environment in the top of a (minimal) Linux system.

IF you want this Plasmaware, feel free to use thirdly-party repositories, BUT, I for one I want my Slackware, not the Plasmaware!

And I hope that Patrick Volkerding would see the trap set by Plasma 5, and when KDE4 would not compile anymore, would replace it eventually with some more lightweight desktop environment, even it is based on Qt.

In that moment you will get something which is not Slackware anymore, but your own Dauerware, where if you build something, it probably will fail because unresolved PAM and/or Kerberos dependencies...

And you will have to take the duty to maintain it, instead of Patrick Volkerding. ;)

BUT, that's theoretical, at the end of day, would be interesting to research and report back the very impact of PAMification of a Slackware installation... :D

Our dear BDFL of Slackware doesn't seem to like PAM. As long as it doesn't get in my way I don't care either way, and having said that I don't like things that obfuscate what is going on (not saying PAM does or does not do this because I never looked into it). Its one of the reasons I use Slackware with its KISS philosophy. If he isn't going to use Plasma 5 then he should just drop KDE because Current is the development branch of the next Slackware. Why waste time supporting something that will be dropped in the next release and conflicts with Plasma 5 packages? Plasma 5 is like where Firefox and rust was. Its on the to-do list but not yet from what I gather based on what our dear BDFL of Slackware has said. Also there are several versions of Slackware available for the Plasma 5 phobics.

haha, so basically I am screwed :)

So I guess I have to decide whether to use matlab and find another distribution or live without it.

If I needed PAM I would use Dlackware's PAM.

Okay, I will back up my system and see what happens :)

Compiled and installed all the pam files. Matlab is running :)

Let us see what problems I run into later.

You installed only the LinuxPAM (aka pam) package, or all of those packages?

How did you determine that your claim holds truth?
Let me give you my view of sizes:

Slackware current's KDE plus KDEI (64bit):
Plasma5, its language files and its deps:
In order to understand why Plasma5's language files (the kdei section) is so small if you compare ith with KDE4 you need to know that those language files are just for the remaining kdelibs4 applications. All Plasma5 applications have their localizations inside the binary packages. This means you won't be able to selectively install just one or two languages - you get them all by default.

But apart from that fact, what you see above is that the sum of all packages for Plasma 5 (1184 MB) is just 146 MB larger than the KDE4 package set (1038 MB). And just the Qt5 plus the Noto TTF font packages are 153 MB in size. I would not consider Plasma5 to be "too big" for Slackware compared to KDE4.
But that's just my biased opinion.

There is no problem in installing pam in slackware, although relatively pointless because nothing supplied with the slackware distribution uses pluggable authentication modules. If it satisfies a dependency of a pre-compiled binary you don't have the source for, installing it might be sensible - such as with google-chrome in earlier slackware versions - but if that pre-compiled binary intends to use pam for authentication it is likely to be disappointed because the particular module it is looking for may be missing, and even if it is there its configuration file might be incomplete.

I have one slackware64-current computer which has systemd and pam installed: it gives the option of either booting slackware's standard SysV-derived boot-up, or booting with systemd (you can pass the init as a kernel parameter). The only packages that really needed to be recompiled for this were shadow, dbus, polkit and wpa-supplicant. You also need to prune eudev, because systemd supplies pretty much everything except udevd (and is ABI compatible with eudev), which is still required for a SysV boot-up.

I installed all the files in https://github.com/Dlackware/pam

Eric, you use 'la méthode coué' for 'Darth Vader' ;)

https://en.wikipedia.org/wiki/Émile_Coué

That is somewhat extreme. You replaced your slackware shadow package with a pam enabled one just to run Matlab: does Matlab actually require that?

I am not limited by knowledge :)

I tried to replace the shadow package with the slackware original and removed all the other packages except for the linux-pam package. Matlab still runs so it is only necessary to install the pam package.

I know you already solved it, but in case you don't want the libpam package actually installed on your system:

I ran into the same problem. This is what I did:

1. Mirror https://github.com/Dlackware/pam

2. Build pam using the supplied SlackBuild.

3. explodepkg your newly built pam package to grab libpam.

4. Copy libpam.so.0.84.2 to (e.g.) /opt/MATLAB/R2017a/bin/glnxa64/libpam.so.0.84.2

5. Make a link so libpam.so.0 points to libpam.so.0.84.2 (ln -s libpam.so.0.84.2 libpam.so.0)

I'm pretty sure I sent a message to The MathWorks detailing all this in the hopes that they'd document it, but they simply replied "Slackware is not a supported Linux OS." I also asked that they not link against libpam, because as far as I can remember, MATLAB isn't actually using libpam to do anything.

It's too bad they didn't at least say "Thank you for your interest in our software"
Or
" and by the way thanks for helping someone else use our software, at no expense to us."
Or
"We really enjoy working the open source community"

Dream on, I guess

There used to be the same issue with google-chrome in times past, which is why slackware used to include pam in extras. pam in slackware didn't actually do anything except satisfy a linking dependency (it didn't do any authentication unless you installed your own modules). However, google fixed the need for this.

Permit me to disagree! For example, the lack of a functional PAM authentication make (almost?) impossible the usage of iTALC, a software used heavily on schools... ;)

The thing is something like a remote control, and the teacher can see and act on any of student computers.

So, for lack of PAM, on at least three schools the kids learn Ubuntu instead of Slackware. Trust me, there. ;)

Read the story of those three schools as about 5000 of possible future Slackware users was, well... lost. Every year.

But this is a old story, from 8 years ago...

Would you care to read again what I (and others) have written, which is about how to run Matlab under slackware? What you say may or may not be true, I don't care to take the time to find out. However it has nothing to do with the point to which you think you are replying.

@chrisVV

Well, I just replied to your questioning of the general PAM utility in Slackware, nothing more... ;)

The point you continue to miss is that my post had nothing to do with questioning the general utility of having PAM in slackware. It commented only on why for a time earlier slackware versions had it in extra, as a matter of fact. That was to satisfy a linking dependency of google-chrome.

Since you want to continue this, on a more on-topic point and as an entirely separate issue, your advice about substituting a load of dlackware stuff on the OP's system to run matlab was way wide of the mark.

Let me lastly add that I have nothing particularly against pam or systemd. As I mentioned, I have both running with slackware64-current on one of my computers, on a much less intrusive basis than dlackware achieves. I also have gnome-3.24 running on it.

You are kind to read the previous posts again? ;)

In fact, while Richard Cranium happens to advice the usage of http://www.slackware.com/~vbatts/pam/ , myself I warned the OP that this project is about an eventual PAMification of Slackware, and how I know that it is still relative old stuff, I suggested https://github.com/Dlackware/pam as more viable alternative for, IF the OP wants to go this path for real. Read: I explained the context of what OP is ready to go.

Yet, I issued another warning about the possible dramatic consequences of this choice and the risk to render the system unusable on slightest mistake, like you seen. ;)

Finally, while after my warnings about the eventual consequences the OP being still undecided, guess who go forth? RadicalDreamer

Finally, later happens that drumz suggested what I see a proper way to deal with this particular issue of the Matlab usage on Slackware. ;)

Sorry, this is unintelligible drivel. And still misses the point.

I believe that Darth Vader would attempt to out-stubborn a cat.

It was my belief that the OP just wanted Matlab to work and really didn't give a damn about installing PAM to handle authentication on his/her system. I believed the OP would have simply grabbed the libpam package, looked inside it, and install the shared library that he asked about in the first message.

If it will make you shut up, of course you saved the day, Darth Vader.

I think that Darth Vader viewed my reply as "Hey, OP, install all this stuff and it will solve your problem". I thought that I meant "OP, you can find your missing shared library somewhere in here."

Darth Vader's point that package set I pointed to might not actually work if you installed it all and actually leave you with a severely borked system is not without merit.

However, PAM has been a bee in Darth's bonnet for a few years now. I start to wonder if our BDFL doesn't include PAM simply to tweak Darth's nose.

If he wanted to do that he would move Current to Plasma 5 XD

seriously? I hope it will not become a pain like MS where you want a different language that does not fit to the locale and date formats
simply not installing languages files gave me this until now in KDE, I c
But apart from that fact, what you see above is that the sum of all packages for Plasma 5 (1184 MB) is just 146 MB larger than the KDE4 package set (1038 MB). And just the Qt5 plus the Noto TTF font packages are 153 MB in size. I would not consider Plasma5 to be "too big" for Slackware compared to KDE4.
But that's just my biased opinion.ould have my german/swedish , whereever I am date formating, units and other settings, but having a english user interface.
hope this will not change with KDE5

Thanks a lot. I will try this.

It works :) PAM package removed.

is is as like MS now,
just setting the regional settings changes the language,
but a little bit more easy to fix
one more verschlimmbesserung (a German word that talks about improvements that not only improve)

Not to revive a closed thread, but, for those setting up MATLAB R2019a on slackware-current, I just wanted to report that this solution still works. Very helpful, thanks.