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.
My guess is because not everyone wants to run an X session on their computers. Some probably don't even install it (think firewall or web/database server).
Distribution: Started with Slackware - 3.0 1995 Kernel 1.2.13 - Now Slackware Current. Also some FreeBSD.
Posts: 124
Rep:
Quote:
Originally Posted by bassmadrigal
My guess is because not everyone wants to run an X session on their computers. Some probably don't even install it (think firewall or web/database server).
Makes sense! Back a few years ago when I had half a dozen Slackware production servers at work running mail, web, DNS and as routers, I did not even install X. Alas, they have been replaced with Cisco routers and (ugh) Microsoft Windows servers (not by my choice of course ;-)
That's why I love Slackware!! Pat doesn't try and second guess what we want to do, he leaves it up to us to configure our systems as we need them!!
LightDM is my display manager of choice for my SlackMATE desktop. It won't compile on stock Slackware because PAM is a hard dependency. I like its "greeter" approach. LightDM is also my choice for this small project because it provides all needed functionality: PAM authentication, user switching and session locking.
LightDM is my display manager of choice for my SlackMATE desktop. It won't compile on stock Slackware because PAM is a hard dependency. I like its "greeter" approach. LightDM is also my choice for this small project because it provides all needed functionality: PAM authentication, user switching and session locking.
In that case, would it be sufficient if I installed Linux-PAM before building LightDM? Or would I have to rebuild a number of core Slackware packages for this to work?
My guess is because not everyone wants to run an X session on their computers. Some probably don't even install it (think firewall or web/database server).
My servers (LAN, public) are all headless, e. g. they run in runlevel 3 and they don't have a GUI. But that's not the question here.
@Eric, I've fiddled with customizing XDM and even succeeded to a certain point. The trouble is, I need some shutdown/reboot button for my users.
I see now. I would vote for gdm then. I just installed it (it needs only libgnomecanvas as dependency) and tried it just rebooting at runlevel 4.
Which Version did you install? From slackbuilds.org ist is 2.20.11 from 03-Jun-2010, maybe newer ones doen't work that easy.
Maybe a customized xdm ala alienbob http://www.linuxquestions.org/questi...3&d=1446756415
shipped with stock slackware would stop most users thinking of another Loginmanager.
Btw. the stock Lilo customization a few years ago was a nice addition too for me, personal.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
