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.
So with PAM now in slackware current, will it become like pulseaudio or systemd where it's required to be installed for just about everything? I don't want to have insane dependency on PAM if I never intend on using it.
So with PAM now in slackware current, will it become like pulseaudio or systemd where it's required to be installed for just about everything? I don't want to have insane dependency on PAM if I never intend on using it.
PAM will be required due to it being included in many vital packages for the system. If you wanted to remove it, you'd at least have to recompile all the below programs (after removing the ones highlighted in red) and may need to adjust some or many conf files.
Code:
+--------------------------+
Mon May 18 19:17:21 UTC 2020
Greetings! After three months in /testing, the PAM merge into the main tree
is now complete. When updating, be sure to install the new pam, cracklib, and
libpwquality packages or you may find yourself locked out of your machine.
Otherwise, these changes should be completely transparent and you shouldn't
notice any obvious operational differences. Be careful if you make any changes
in /etc/pam.d/ - leaving an extra console logged in while testing PAM config
changes is a recommended standard procedure. Thanks again to Robby Workman,
Vincent Batts, Phantom X, and ivandi for help implementing this. It's not
done yet and there will be more fine-tuning of the config files, but now we
can move on to build some other updates. Enjoy!
a/cracklib-2.9.7-x86_64-1.txz: Added.
a/libcgroup-0.41-x86_64-7.txz: Rebuilt.
Rebuilt to add PAM support.
a/libpwquality-1.4.2-x86_64-1.txz: Added.
a/pam-1.3.1-x86_64-1.txz: Added.
a/shadow-4.8.1-x86_64-7.txz: Rebuilt.
Rebuilt to add PAM support.
a/util-linux-2.35.1-x86_64-6.txz: Rebuilt.
Rebuilt to add PAM support.
ap/at-3.2.1-x86_64-2.txz: Rebuilt.
Rebuilt to add PAM support.
ap/cups-2.3.3-x86_64-2.txz: Rebuilt.
Rebuilt to add PAM support.
ap/hplip-3.20.5-x86_64-2.txz: Rebuilt.
Rebuilt to add PAM support.
ap/mariadb-10.4.13-x86_64-2.txz: Rebuilt.
Rebuilt to add PAM support.
ap/screen-4.8.0-x86_64-2.txz: Rebuilt.
Rebuilt to add PAM support.
ap/sudo-1.9.0-x86_64-2.txz: Rebuilt.
Rebuilt to add PAM support.
kde/kde-workspace-4.11.22-x86_64-7.txz: Rebuilt.
Rebuilt to add PAM support.
l/ConsoleKit2-1.2.1-x86_64-4.txz: Rebuilt.
Rebuilt to add PAM support.
l/gnome-keyring-3.36.0-x86_64-2.txz: Rebuilt.
Rebuilt to add PAM support.
l/libcap-2.34-x86_64-2.txz: Rebuilt.
Rebuilt to add PAM support.
l/polkit-0.116-x86_64-3.txz: Rebuilt.
Rebuilt to add PAM support.
l/system-config-printer-1.5.12-x86_64-4.txz: Rebuilt.
Rebuilt to add PAM support.
l/vte-0.60.2-x86_64-2.txz: Rebuilt.
Recompiled against icu4c-67.1.
n/cifs-utils-6.10-x86_64-4.txz: Rebuilt.
Rebuilt to add PAM support.
n/cyrus-sasl-2.1.27-x86_64-4.txz: Rebuilt.
Rebuilt to add PAM support.
n/dovecot-2.3.10.1-x86_64-1.txz: Upgraded.
Rebuilt to add PAM support.
n/netatalk-3.1.12-x86_64-3.txz: Rebuilt.
Rebuilt to add PAM support.
n/netkit-rsh-0.17-x86_64-3.txz: Rebuilt.
Rebuilt to add PAM support.
n/nss-pam-ldapd-0.9.11-x86_64-1.txz: Added.
n/openssh-8.2p1-x86_64-3.txz: Rebuilt.
Rebuilt to add PAM support.
n/openvpn-2.4.9-x86_64-2.txz: Rebuilt.
Rebuilt to add PAM support.
n/pam-krb5-4.9-x86_64-1.txz: Added.
n/popa3d-1.0.3-x86_64-4.txz: Rebuilt.
Rebuilt to add PAM support.
n/ppp-2.4.8-x86_64-2.txz: Rebuilt.
Rebuilt to add PAM support.
n/proftpd-1.3.6c-x86_64-2.txz: Rebuilt.
Rebuilt to add PAM support.
n/samba-4.12.2-x86_64-2.txz: Rebuilt.
Rebuilt to add PAM support.
n/vsftpd-3.0.3-x86_64-6.txz: Rebuilt.
Rebuilt to add PAM support..
x/xdm-1.1.11-x86_64-10.txz: Rebuilt.
Rebuilt to add PAM support.
xap/xlockmore-5.63-x86_64-2.txz: Rebuilt.
Rebuilt to add PAM support.
xap/xscreensaver-5.44-x86_64-2.txz: Rebuilt.
Rebuilt to add PAM support.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,153
Rep:
Quote:
Originally Posted by ziprun
So with PAM now in slackware current, will it become like pulseaudio or systemd where it's required to be installed for just about everything? I don't want to have insane dependency on PAM if I never intend on using it.
If you don't use it, there is a good chance you'll never know it is there.
It has been completely transparent to me, but then, I sign on at the command line and then launch the
desktop, either Xfce or Kde, with startx.
I'd rather it doesn't end up in slackware but who knows where the road will take us. I'm curious to know whats going to happen with session management. ConsoleKit2 doesn't seem to get much attention anymore and there's not too many other options out there. It's a tough job avoiding the systemd creep and keeping everyone happy...
I would say, "never say never"... but there are no indications he's planning on moving us there. But as 0XBF mentions, we don't know what the future will hold for Linux and the various components. We've been able to escape systemd so far, although, with the help of projects that have pulled some components out of systemd and made them available for others to install without systemd (like eudev).
But 10 years ago, I'd imagine that people would've thought that Slackware would stay PAM free, but it got to a point where Pat felt it was beneficial to add it in, so here it is.
I'm hoping systemd can stay out of it, and it seems like the Slackware dev team seems to feel the same way for now, but we'll have to see how the Linux ecosystem changes over the years.
I'd rather it doesn't end up in slackware but who knows where the road will take us. I'm curious to know whats going to happen with session management. ConsoleKit2 doesn't seem to get much attention anymore and there's not too many other options out there. It's a tough job avoiding the systemd creep and keeping everyone happy...
What we really need is there - the elogind to replace that ConsoleKit2 covered with rust.
By just removing ConsoleKit2 and installing this elogind build according with its README, I was finally able to bring up a Wayland session with the otherwise unmodified build of Plasma5 as shipped by Mr. Hameleers. The ConsoleKit2 can't ...
In other hand, in a normal X11 session, I was able to run natively a particular application: Skype . And that without questionable login1 mock servers which interact badly with ConsoleKit2 server and/or the desktops.
Gentlemen, please do not treat softly this particular Microsoft software named Skype, specially when the companies from entire World pushes for their employers of working from home. Because it is what they use for internal communications.
Last edited by LuckyCyborg; 05-28-2020 at 08:48 PM.
Gentlemen, please do not treat softly this particular Microsoft software named Skype, specially when the companies from entire World pushes for their employers of working from home. Because it is what they use for internal communications.
I don't really have a leg in this race, but Skype can be run from the browser and does not require a program on the computer.
That being said, hopefully something can be done to allow it to be installed without breaking anything else. Whether that is by switching to elogind or something else is above my paygrade.
I don't really have a leg in this race, but Skype can be run from the browser and does not require a program on the computer.
That being said, hopefully something can be done to allow it to be installed without breaking anything else. Whether that is by switching to elogind or something else is above my paygrade.
No, it can't be fully run from a browser - at least under Linux.
Because the Skype for Web works usually only for the text messages, the Skype itself (and the Skype for Business) offers also audio calls, video calls, video conferences and desktop sharing - which is a way to make remote presentations or just a team leader can ask an employee to show his/her desktop, to ensure that the work is really in progress instead of posting photos in Facebook...
Last edited by LuckyCyborg; 05-28-2020 at 08:47 PM.
The deps are there for elogind now so it seems like a possible answer, or at least what the other non systemd init distros are doing. Things work now with CK2 but the github page hasn't changed in a while. Just an observation I've made so it got me wondering whats going to happen in that area. The work required to maintain that kind of software is beyond me so I can't say much more about it. Just have to see what comes of it.
The deps are there for elogind now so it seems like a possible answer, or at least what the other non systemd init distros are doing. Things work now with CK2 but the github page hasn't changed in a while. Just an observation I've made so it got me wondering whats going to happen in that area. The work required to maintain that kind of software is beyond me so I can't say much more about it. Just have to see what comes of it.
With all respect, the things does NOT work now with CK2. For example:
- the Wayland sessions, like Plasma5 or whatever else, i.e. SWAY
- the Skype "needs" a login1 mock server which may or may not confuse the desktops like Plasma5, resulting in lossing ability of power control via desktop.
- ConsoleKit2 supports only one seat, while elogind, like systemd-logind itself, support a true multiseat.
Permit me a note regarding this multiseat feature: it permits one computer to be used by (usually) two or more users simultaneous, while every one having his/her set of monitor, keyboard, mouse and headphones.
Maybe not so important for those rich citizens of North America, but it is a feature much appreciated elsewhere, both in schools and companies, because is much cheaper (for example: to buy 100 computers instead of 200) and it is more energy efficient.
I seen this multiseat in action even in home use, when the schools was closed because that coronavirus and the activity continued on-line, when some of my friends used this setup with Fedora, to offer to their children the ability to work independently on-line.
I know, I know, an American had been just bought several computers, but not everyone is that rich to do it just for a probably temporary situation...
Last edited by LuckyCyborg; 05-28-2020 at 09:33 PM.
Because the Skype for Web works usually only for the text messages
Is this something recent? Because there have been several posts discussing that the web version works fine for video (not sure about desktop sharing though, I haven't seen that one mentioned).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
