pulseaudio was made popular by ubuntu
it was put in to solve one thing and one thing only, plugging in an hdmi cable after you started playing a movie and having it work without editing an .asoundrc and restarting the video player
everything else about it is bad design, very very bad design
even its creator stated that he doesn't know shit about digital audio and it clearly shows

as shown by this topic all the requests for PAM mostly come from the desire to solve one thing, AD
(and one login thing, that is not really a problem IMO)

redhat is not the same as fedora, that much should be clear
the devs from one another are not the same and the redhat devs actually know how computers work
most of the crap that is being pushed comes from fedora, or more precisely gnome
(see "free"desktop.org lately)
including systemd
systemd only got popular in general because of "faster booting", that was never even benchmarked properly
almost all the other "features" it brings are useless

so don't blame redhat, blame fedora
even though redhat is also overrated and a company that only does things for money, at least they also do good things in the process

/rant
that's what you get for going off topic, a stupid rant

I actually don't blame Fedora, and really nobody can blame them, Canonical Inc., Red Hat Inc., or any other company, even Microsoft and Apple.

I blame a bunch of trend wanting hipsters who don't know the first thing about UNIX development, design, structuring, and purposing only looking to be cool, trendy, and make GNU/Linux exciting to make a quick buck or get a quick thrill and then move on to the next thing and leave things a disastrous mess all in an effort to not use Windows because they feel it's not cool enough.

Things don't have to be perfect, like udev for example, but they need to work, and work well, but only for that one particular purpose. Like fish in a school, every fish knows it's role and does it's purpose to the school, but separate from the school, the fish is still a fish and can be independent. People want fish, not a grumpy kraken grabbing everything with it's tentacles.

Folks, please. This topic is about PAM and the possibilities it offers. Please don't turn this into a rant about Syslinux, Pulseaudio, Systemd, Red Hat or Ubuntu.

4 members found this post helpful.

I think if Slackware 15.0 is to be considered at this point, a full roadmap to consider things like Wayland support, KDE/Plasma 5, and any other possible updates or considerations to discuss need to include things much more than PAM. Really, there are more important things that could be discussed. We have no idea what new convoluted hipster fadware what could come between now and then to work around as best as possible.

To be discussed elsewhere then. What Nicolas reminded us (me included) is the sane rule: in a any given thread, only discuss about the topic set by its first post, so that it be properly addressed. If one want to discuss another topic, just open a new thread.

Then please let us discuss our less important stuff here and open a different thread for your more important stuff.

I just have to laugh at Wayland.

2 members found this post helpful.

Then please create a separate thread "Why I think Wayland is funny" and discuss this technology's respective merits and entertainment potential with fellow forum member ReaperX7.

6 members found this post helpful.

To be fair pulseaudio has gotten a lot better over the past two years, i have to use it that or edit my asoundrc, every ten minutes. I think the problems with Pottering, and a lot of developers these days. is what i call the "C++/Java ate my brain", effect, The OOP Model advanced by the C++, and Java people, thus taught in most CS programs over the past ~15 years tends to encourages overcomplicated and bloated design. Just look at writing a file in java for the stereotypical example. Newer devs don't know any other design philosophy, or at least newer devs who weren't taught C by an 73 year old who complained constantly about the university administration axing the PDP-11, so they design crap by default. We just happen to be unlucky in recent years that the greybeards are dying out, or are loosing influence.

Now that's a rant for you

As it should be!

1 members found this post helpful.

If a magic spell that makes AD login work on stock Slackware, has been revealed to you by BOB, please let us know.

So far all I can do is to apply the methods from the real world. Unfortunately in the fantasy world of Slackware these methods resemble jumping through fire hoops.


Cheers

2 members found this post helpful.

yes of course it should be that way
that's a basic thing an OS should do

problem comes from the solution to the problem being really shitty

1 members found this post helpful.

The same could be said of any and all software.

So... it looks like it is Kerberos, not PAM, that PV opposes strongly.

My question: is PAM without Kerberos enough to support the flat file authentication (ie. passwd/shadow/group) we have now?

If so, then adding PAM on these terms (no kerberos + default config to flat file auth) would still be of tremendous usefulness.
In this scenario, a framework would be in place that would allow any user to expand it to his/her needs (that is in tune with Slackware's philosophy, is it not?).
ie. compile Kerberos + recompile PAM = samba that integrates with AD
ie. all slackbuilds from SBo that can get PAM support would get it.

5 members found this post helpful.

Could a moderator kindly close this thread?

1 members found this post helpful.