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.
I have tried to install an ubuntu server just for fun on vm and tried the minimal settings for webserver and as you said, it was minimal at first, but after few weeks, i ran apt-get update and upgrade, there comes the nightmare where new version if the same apps required a mass of new deps...
I don't know if the same happened on debian, but that's what i got on Ubuntu, which is/was based on Debian.
Hey Willy, here's one of the lesser-known distinctions of the Debian/Ubuntu world. Upgrade system and eventually install new dependencies:
Code:
# apt-get dist-upgrade
Update system without installing new dependencies:
Code:
# apt-get upgrade
That being said, Ubuntu Server LTS has a feature freeze like the other distros. I'm running a handful of Ubuntu servers both locally and public, and I haven't noticed any mysterious dependency tsunami. On the contrary, the installations are quite lightweight.
Brian Q Public here. As I've explained in my LQ blog, I was a late starter as far as interest in and use of computers is concerned. I'm interested in just about anything that can be done with Linux, and a full install of Slackware (+ a few more bits and pieces) gives me the software to do it. OOTB, without apt-getting or yuming for hours on end. So, to me, it's not bloated. If some Slackers need PAM, let 'em have it. I don't know how, or where, I'll leave that to Pat & the Team.
I am surprised indeed. First hint in 2.900+ messages that you actually do something with your system.
Yeah, and there's no need for you to be rude either. I do plenty with my system, including a lot of R&D for a project I work at with diligence. Sorry, if I'm just one more "stupid American" you act like you can look down on.
Yeah, bro, I see how it is... just because I'm not a system or network admin, you look down on me? Go read every post I've ever made! Quote something from each and every single one where I didn't do least something. Put your money where your mouth is or pipe down and be silent!
I'm not a pam lover, but I think tha the next stable release (14.2 or 15.0) should be linked to pam.
Slackware already contains pam, in /extra, but is only for additional packages. I can't use ssh with pam.
Really, I don't like pam, but some authentication schema (ldap for example) does not work without it
It would be nice to have a little update and/or statement from the BDFL himself about the subject.
Distribution: slack 7.1 till latest and -current, LFS
Posts: 368
Rep:
As most of you know me by a dropline gnome dev. and from the systemd slackbuilds.
I am using PAM for a long time.
My opinions on this matter.
1. Does Slackware need PAM
A. NO
2. Would PAM be nice to have, and what would be minimal to be rebuild ?
A. Yes, shadow only.
Personally it would be handy to have PAM, but it is not to much hassle to build and install PAM, and rebuild shadow in order to have PAM functionality for the software you need.
The only reason why I would like to see PAM in Slackware is to make my life easier.
2. Would PAM be nice to have, and what would be minimal to be rebuild ?
A. Yes, shadow only.
Are you sure about that? Vincent Batts has an experimental PAMified package repo, and on the latest count, it contains no less than 22 (twenty-two) rebuilt packages.
Yeah it really depends what you want to accomplish. I would say rebuild su, sudo, and ssh as well as shadow though so that all the normal login methods work as expected.
Well, what can a poor boy say? Thank you very much for that clarification! That's great news!
I think this points out one of the subtle problems that tends to make problems for threads of this nature.
You ask the same question and two people can still understand it in different ways.
PAM? Heck no! says person 1 who interprets the question as 'rebuild everything to rely on PAM and look just like CoreBuntu.
PAM? Why not? says person 2 who interprets the question as 'build one package that provides PAM exclusively other packages which require it.'
They could both actually be in total agreement if you gave them more specific, detailed proposals rather than the more general question, we just dont know.
At any rate despite some painful-to-read moments of heat I think some interesting arguments have been posted and I feel like I am learning something.
@bartgymnast - can you expand a little particularly in regards to how you use PAM, if you do in fact use it?
They could both actually be in total agreement if you gave them more specific, detailed proposals rather than the more general question, we just dont know.
My specific need being LDAP authentication working on a Slackware server with mixed clients (Slackware, Ubuntu, Elementary OS).
My specific need being LDAP authentication working on a Slackware server with mixed clients (Slackware, Ubuntu, Elementary OS).
My problem is getting openldap up and running with the correct security constraints (SASL and TLS). I haven't gotten to the libnss_ldap portion yet.
This part of configuring openldap correctly has nothing to do with PAM.
If you want SASL to use ldap for authentication information, you'll have to rebuild cyrus-sasl as well as modify /etc/rc.d/rc.saslauthd to use the ldap authentication mechanism.
Last edited by Richard Cranium; 08-01-2014 at 11:44 AM.
Reason: Added clarifying comment about PAM, to increase the S/N ratio of the thread.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.