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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

Dear @ordealbyfire83, you are kind to explain how your opinion as BLFS user is relevant for Slackware Linux?

I'm not so inclined, but after reading this thread I found mentioned quite a lot of the concerns and problems that I had in getting KDE 5 built and configured. Let's NOT go there, but Slackware and B/LFS are probably the last traditional GNU/Linux distributions (as opposed to the so-called "modern" systemd/Linux variants). So if there gets a point where KDE5 will not run with the traditional LFS base then it probably won't work on Slackware without heavy modifications, either. And some parts seem to be headed that way.

Slackware is the distribution that people turn to when things are expected to "just work" and thus far it has all of the tight integration needed to make that happen. KDE5, well, doesn't "just work," and folks like to add a "yet" there, but will it ever?

Not to mention rebuilding a newer point release of KDE5 (kdelibs and plasma user space) sometimes requires newer versions of graphics packages (Mesa, X, ...) so it's not always even possible to fix bugs without an entire OS spec bump.

Care to share which part you are talking about? I would not be able to mention any at this point in time.

Quote:

Not to mention rebuilding a newer point release of KDE5 (kdelibs and plasma user space) sometimes requires newer versions of graphics packages (Mesa, X, ...) so it's not always even possible to fix bugs without an entire OS spec bump.

For slackware-current that is not an issue. And I have been building KDE5 packages for Slackware 14.2 (which was released one and a half year ago) until december 2017 without the need for X.Org or mesa updates. So I think it is not as bad as you think.

Care to share which part you are talking about? I would not be able to mention any at this point in time.

Specifically I'm talking about session management and getting Shutdown, Reboot, Hibernate, and Suspend to show up AND actually work. There was discussion about this here. I unfortunately could not get the desired behavior even by trying the suggestions in this thread regarding 'startkde'. If this has actually been fixed (in the sense of not needing any logind implementation whatsoever) since then, then that would surely be a plus.

In my experience there was a spec bump needed in going from KDE 5.5 to 5.8 - although the packages compiled without error, keyboard and mouse flat out failed to work, and text input was garbled, on 5.8 until I upgraded the underlying system. BLFS specifically asks for "Mesa built with Wayland" for building the Plasma part of KDE 5. I suspect this is where things can get messy - maybe Mesa built this way has issues. Perhaps you have found a way to avoid this (and thus skipping the kwayland{-integration} packages)? If so that would probably give much more flexibility and stability with adopting new versions.