Slackware 15 update, Pam/Kerberos

[ChuangTzu]

FYI, it looks like whenever Slackware 15 arrives it may include Pam/Kerberos...

PV: Good to hear that there will be interest in testing this

https://www.linuxquestions.org/question ... ost6056858

PV:
Quote:
If we do the krb5/PAM, don't expect any support for not running it. It'll be mandatory unless you wish to figure out what and how to recompile and reconfigure everything needed to get rid of it.

That said, if it is added I expect to make it so that you won't even notice that it's there. So unlike PA, for example, there shouldn't really be any scenarios where certain things do not work as well because the system has krb5/PAM.

https://www.linuxquestions.org/question ... ost6057301

[gapan]

I was guessing that this might be one of the reasons that is delaying a 15.0 release. From the moment pam hits current, I don't expect a final 15.0 release for at least a few months, so we probably still have a long way to go.

[ChuangTzu]

It's arrived in -current /testing
https://www.linuxquestions.org/question ... 175669418/

ivandi's configs to play with:
https://www.linuxquestions.org/question ... 175669451/

[DidierSpaier]

Hello,

So unlike PA, for example, there shouldn't really be any scenarios where certain things do not work as well because the system has krb5/PAM.

I have still to find a scenario where certain things do not work as well because the system has PA. Can you please describe one?

Best,

Didier

[ChuangTzu]

Didier, I was quoting Pat V. there, so you would have to check with him.

[DidierSpaier]

Hello ChangTzu,

Didier, I was quoting Pat V. there, so you would have to check with him.

Well, I assumed that you had first hand evidence. I now assume that you quoted the ChangeLog for -current:
https://mirrors.slackware.com/slackware ... ngeLog.txt that I also quote below (emphasis mine):

+--------------------------+
Thu Apr 26 01:34:12 UTC 2018
Don't like PulseAudio? Well... I hear you. Personally, it works for me, and it
makes it easier to switch between multiple audio inputs and outputs compared
to using plain ALSA. PulseAudio got off to a rocky start in the Linux world,
where it found itself adopted before it was ready (it was even billed on its
own website at the time as "the software that currently breaks your audio").
It's my opinion that the reputation that PulseAudio acquired due to problems
back then isn't deserved any longer. If your hardware supports the sampling
rate of the audio data you're trying to play, PulseAudio will not resample it
(and if your hardware doesn't support that rate, resampling can hardly be
avoided). The increased latency has not been an issue here. Nevertheless, I
recognize that there are use cases where PulseAudio is still a detriment.
While I don't generally recommend removing PulseAudio, I'm not going to cram
it down your throat. So, if you'd like to be rid of PulseAudio, head over to
the new extra/pure-alsa-system directory and follow the instructions in the
README file there, and you'll have a PulseAudio-free pure ALSA system.
Thanks to orbea who sent me a small patch for the mpg123.SlackBuild so that
it would detect the lack of PulseAudio and not try to build in support, which
got me to thinking about all of this. Cheers!

Posting a question on LQ asking which are theses use cases would un-avoidably trigger one more useless flame war, so I won't just not ship "pure-alsa-system" in Slint until I get a convincing answer to this question..

Have a good day,

[laprjns]

So @gapan, does the inclusion of PAM now make LightDM the leading candidate to replace GDM as the Salix display manager?

Reference The Salix Blog - Display Managers

[gapan]

So @gapan, does the inclusion of PAM now make LightDM the leading candidate to replace GDM as the Salix display manager?

Reference The Salix Blog - Display Managers

Yes!

[DidierSpaier]

Meanwhile, in Slint64-14.2.1:

Code: Select all

root[/home/didier]# login-chooser 

Usage: login-chooser <login manager>
Available login managers:
 text lightdm lxdm kdm gdm 
Short descriptions:
text:    Login in text mode, in a console. From there, you
         can type "startx" to start a graphical session.
lightdm: Light Display Manager, accessible with speech.
lxdm:    LXDE Display Manager.
kdm:     KDE Display Manager.
gdm:     GNOME Display Manager, fully accessible with speech.
Login is currently set to text mode.
root[/home/didier]
didier[~]$ ls /var/log/packages/|grep -e pam- -e gdm- -e lightdm -e xdm -e kdm 
gdm-2.20.11-x86_64-1slint
lightdm-1.24.0-x86_64-4slint
lightdm-gtk-greeter-2.0.3-x86_64-2slint
lightdm-gtk-greeter-settings-1.2.2-noarch-1slint
lxdm-0.5.3-x86_64-15slint
pam-1.2.1-x86_64-1slint
xdm-1.1.11-x#

Code: Select all

didier[~]$ ls /var/log/packages/|grep -e pam- -e gdm- -e lightdm -e xdm -e kdm 
gdm-2.20.11-x86_64-1slint
lightdm-1.24.0-x86_64-4slint
lightdm-gtk-greeter-2.0.3-x86_64-2slint
lightdm-gtk-greeter-settings-1.2.2-noarch-1slint
lxdm-0.5.3-x86_64-15slint
pam-1.2.1-x86_64-1slint
xdm-1.1.11-x86_64-6
didier[~]$ 

Maybe that's a little too much... In my opinion gdm is by far the best.

[Papasot]

Maybe that's a little too much... In my opinion gdm is by far the best.

The best Display Manager is... no display manager. I fail to see why I should have yet another process running in the background just to see a graphical login screen. Furthermore, sometimes you just don't need X at all - and when you need it, the traditional, tried-and-true startx is easier to configure. So just uninstall GDM, set the default runlevel to 3 in /etc/inittab, and you are set.