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.
Not having time? Sorry, but that's nothing more than an excuse if you ask me. If you don't have time, you make time.
So, do you have time to make your own car, house, clothes? How about your motherboard, hard drives or monitor? Why don't you make time so you can do those?
Truth is, we don't have time to do everything, which is why we have a society where we do what we can, but we also have to rely on others. There's an interesting video where someone took the time to literally make his own sandwich. It cost him $1500 and took six months. How to Make a $1500 Sandwich in Only 6 Months The fact is, someone took the time to develop and build the initial Linux kernel. Someone took the time to develop the GNU utilities. Someone took the time to learn how to put these all together and form distributions. We don't all have the time to code this from scratch, or to package it all up. Telling people to learn how a slackbuild works is trivial. Telling someone to replace half of their core packages with PAM enabled packages and then tell them to keep up with all the security updates (and in your opinion, they should be willing to make packages available so others can use slackpkg+ to install them because they don't have to make time to do it themselves) is a major undertaking, and I think you can guess how many people have actually attempted it.
I administrate my own systems, 1 server and 1 laptop, and I have my own packages I use on my system that are different from the defaults used by Slackware. What I publish on SlackWorks is a derivative of my work I make public. As far as users I have four.
So you have absolutely no idea of the needs and constraints of people who administrate hundreds of servers and users. Thanks for confirming my assumption.
Last edited by Didier Spaier; 10-13-2015 at 10:46 PM.
Telling someone to replace half of their core packages with PAM enabled packages and then tell them to keep up with all the security updates (and in your opinion, they should be willing to make packages available so others can use slackpkg+ to install them because they don't have to make time to do it themselves) is a major undertaking, and I think you can guess how many people have actually attempted it.
Ooh, I shouldn't want to tell someone that (especially if that someone is Patrick Volkerding).
So, do you have time to make your own car, house, clothes? How about your motherboard, hard drives or monitor? Why don't you make time so you can do those?
Truth is, we don't have time to do everything, which is why we have a society where we do what we can, but we also have to rely on others. There's an interesting video where someone took the time to literally make his own sandwich. It cost him $1500 and took six months. How to Make a $1500 Sandwich in Only 6 Months The fact is, someone took the time to develop and build the initial Linux kernel. Someone took the time to develop the GNU utilities. Someone took the time to learn how to put these all together and form distributions. We don't all have the time to code this from scratch, or to package it all up. Telling people to learn how a slackbuild works is trivial. Telling someone to replace half of their core packages with PAM enabled packages and then tell them to keep up with all the security updates (and in your opinion, they should be willing to make packages available so others can use slackpkg+ to install them because they don't have to make time to do it themselves) is a major undertaking, and I think you can guess how many people have actually attempted it.
Are you seeing your hypocrisy?
No, I see an empty argument trying to compare apples to lettuce. Of course you can't make everything, and what kind of nitwit would believe that? However, when it comes to learning and education, you have to make time and develop your skill set, or you don't. There's no excuse for lack of education and learning. Hypocrisy? Please...
If you don't have time then install a distro that doesn't expect you to take responsibility for your own os, like ubuntu. It has pam!
in certain environments you have to do this, thanks to the lack of PAM in Slackware, and it's a pity.
But you have explained already that you have no clue what kind of environments that are and that you never had to deal with this situation.
so if you do not run Slackware in an environment that needs central authentication, than please stop sharing you expert knowledge, you just produce a painful impression by telling others what they should do.
No, I see an empty argument trying to compare apples to lettuce. Of course you can't make everything, and what kind of nitwit would believe that? However, when it comes to learning and education, you have to make time and develop your skill set, or you don't. There's no excuse for lack of education and learning. Hypocrisy? Please...
so why do you not follow your own advice and learn something. deal with a environment that's a bit more than your mini home setup, and show use how you deal with network, users and apps that need central authentication, so that we can see you talk from something practical.
A , you do not do this with Slackware at the moment, hmmmmmm
in certain environments you have to do this, thanks to the lack of PAM in Slackware, and it's a pity.
But you have explained already that you have no clue what kind of environments that are and that you never had to deal with this situation.
so if you do not run Slackware in an environment that needs central authentication, than please stop sharing you expert knowledge, you just produce a painful impression by telling others what they should do.
PAM is not going to make Slackware a corporate level operating system by itself. Slackware still doesn't have SELinux and various hardening and other security patches required for a corporate environment. There is no pity here to be had.
If you don't have time then install a distro that doesn't expect you to take responsibility for your own os, like ubuntu. It has pam!
Here's for "taking responsibility for my own OS". I'm running a business based 100 % on Slackware. My own third-party package repository for servers and desktops currently counts more than 600 packages. I've written hundreds of pages of Slackware-specific documentation. And I'm maintaining a couple hundred machines (LAN servers, public servers, desktop clients, workstations) for clients here in South France.
So please stop the "PAM proponent = lazy n00b" nonsense.
PAM proponent thinking PAM is magic package to cure all ailments without looking at lack of security patches and hardening, but refuses to do work thinking others will do it for them if they cry long enough about it = lazy n00bz
I've been watching you work Kiki and honestly it's commendable. It's developers like you who found the time to learn, refused to be lazy, and gave back to the community that do things the right way. If only more people...
If you don't have time then install a distro that doesn't expect you to take responsibility for your own os, like ubuntu. It has pam!
This is a sad statement at a couple of levels, in particular the suggestion that people who aren't satisfied with the way things are should get out i.e. suggestions for improvement not welcome here. What if I wanted to include zathura as a pdf reader; would you dismiss the suggestion and recommend I install another distro that already has it?
PAM is not going to make Slackware a corporate level operating system by itself. Slackware still doesn't have SELinux and various hardening and other security patches required for a corporate environment. There is no pity here to be had.
Looks like Caitlyn Martin hacked ReaperX7's account.
PAM proponent thinking PAM is magic package to cure all ailments without looking at lack of security patches and hardening, but refuses to do work thinking others will do it for them if they cry long enough about it = lazy n00bz
those who would need PAM are talking about central authentication, not more, not less, to solve one thing, only you made a bridge between PAM and the rest you are talking about.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.