Slackware NOT affected: Memory corruption bug in systemd, no patches yet
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.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by ZhaoLin1457
Let me quote myself:
Seriously? Why we should laugh our asses out of bugs from systemd, GNOME2, GNOME3, Plasma5, MATE, Cinnamon, Java or whatever software, if they aren't part of Slackware and we aren't affected?
How about this: is not our business and never was.
Completely wrong on all accounts, it is important to remain vigilant of the threats even if you are not affected, otherwise apathy takes over and before you know it you are walking with the sheep to the slaughterhouse as well.
... it is important to remain vigilant of the threats even if you are not affected, otherwise apathy takes over and before you know it you are walking with the sheep to the slaughterhouse as well.
And why I should be more scared by this nonexistent threat from an unused software in the foreseeable future, compared with the trillions of bugs about to be introduced in Slackware just when Plasma5 will be adopted, thanks to the strong push made by Mr. Hameleers and his friends?
Just because your Debian PTSD?
Last edited by ZhaoLin1457; 01-11-2019 at 05:20 PM.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by ZhaoLin1457
And why I should be more scared by this nonexistent threat from an unused software in the foreseeable future, compared with the trillions of bugs about to be introduced in Slackware just when Plasma5 will be adopted, thanks to the strong push made by Mr. Hameleers and his friends?
I am not Darth, but in the past I had been read his posts with respect and I learned much from them.
However, you have still to respond me why I should be more scared by a vague nonexistent remote threat, compared with something which will replace half of Slackware, and is famous, well... for being quite buggy.
Last edited by ZhaoLin1457; 01-11-2019 at 05:39 PM.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Because one represents vendor lock-in with as many holes as stars in the sky and is one of the most poorly constructed pieces of sh...software that I have seen. Your concern over Plasma is unfounded, because you can simply untick KDE during the install process and just use Xfce or the plethora of window managers that PV graciously includes on a full install. See the difference now?
I think that the keyword is "represents", so maybe it is a questionable vendor lock-in but there are no signs to enter in Slackware in the foreseeable future. Not when Mr. Volkerding has a conservatory position and Mr. Hameleers has a public claimed "anti" position.
However, how simple will be to not install Plasma5 after it will be merged, that's a debatable subject about facts to be seen.
How you spoken about Darth, I remember that he was quite afraid that half of Plasma5 will be dumped in the libraries and you like or not, you should install them, unless you do a fine analysis of dependencies.
TBH, he wasn't against Plasma5, but he was afraid about impossibility of clean not installing it, for whatever reasons. In his case, to continue the usage of KDE4.
Last edited by ZhaoLin1457; 01-11-2019 at 05:59 PM.
I think that the keyword is "represents", so maybe it is a questionable vendor lock-in but there are no signs to enter in Slackware in the foreseeable future. Not when Mr. Volkerding has a conservatory position and Mr. Hameleers has a public claimed "anti" position.
This is the stupidest argument. They are suggesting Plasma5, because KDE4 is not being actively developed anymore and many programs are starting to rely on QT5 and KDE5 libraries. Eventually KDE4 will be completely EOL (it might already be... I don't follow it much), and then there won't be any more security updates even if things are found.
As has been said, you can remove KDE if you don't want to... if you don't want all the dependencies of KDE5, then you may want to start doing the work to get them figured out... a good place to start would be Eric's ktown repo in the deps directory. Slackware doesn't provide dependency lists, so it's on you if you don't want to do a full install.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Interesting how even with Darth not here the topic is thrown to KDE/Plasma, ala Darth. Strange indeed, or according to Sherlock: https://www.youtube.com/watch?v=M76nPnaJ7G4
However, how simple will be to not install Plasma5 after it will be merged, that's a debatable subject about facts to be seen.
DEs in Slackware are completely optional. They always have been, and I have not seen anything that makes me believe that this will not be the case going forward. Even back when I started using it, there were half a dozen or more choices that I can remember.
Quote:
Originally Posted by ZhaoLin1457
TBH, he wasn't against Plasma5, but he was afraid about impossibility of clean not installing it, for whatever reasons. In his case, to continue the usage of KDE4.
So are you talking about the option to not install it? Or removing it?
Either way, what difficulties do you foresee? I don't see how it's going to be any different to any other version of Slackware.
You'll be able to choose to not install KDE. You'll be able to remove all of it if you install it by mistake. This ain't Windows man.
And of course, you realise that there's nobody holding a gun to your head demanding that you use the latest version of Slackware right? Version 14.2 continues to receive security updates, and most likely will for some time yet.
Quote:
Originally Posted by bassmadrigal
They are suggesting Plasma5, because KDE4 is not being actively developed anymore and many programs are starting to rely on QT5 and KDE5 libraries.
Fun fact: KDE4 made it's debut in Slackware when version 13.0 was released on 26 August 2009.
I'm wondering if it'll make it to 10 years... I can't explain why, but part of me hopes that it does...
No offense, but you are the one who bring up Darth in discussion, after all.
However, my last experiences with Plasma5 was disastrous, to say that in nice words. Specially with its taskbar, as you maybe seen by a recent thread of mine.
So, while intelligent people are busy bashing about imaginary threats, myself I started to be worried about the end quality of something which is expected to replace half of Slackware in the near future.
So are you talking about the option to not install it? Or removing it?
How about freedom to choice, much appreciated specially of those few users of pure-alsa but also by others. What if I do not want Plasma 5 at all, including its far dependencies, with the same passion how you does not want systemd or PulseAudio?
Or that "freedom of choice" is only for you, but not also for me?
You do not think is a perversion of the freedoms, if you have pure-alsa and me I cannot have pure-non-plasma?
Now these are just abstract questions, but I started to not need nothing more than XFCE.
So, while intelligent people are busy bashing about imaginary threats, myself I started to be worried about the end quality of something which is expected to replace half of Slackware in the near future.
I understand your reservations and your concern for the quality of Slackware packages, but KDE is unreservedly, unmitigatedly, indubitably optional. It's not going to occupy one byte of your hard drive if you don't want it to. It shan't on mine anyway, since I will be using Xfce with Slackware 15, just as I am with 14.2.
Those using KDE 5 will be the ones who like it and enjoy using it with all its foibles. And I'm sure they won't be put off by the occasional glitch either
Last edited by Lysander666; 01-11-2019 at 08:21 PM.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by ZhaoLin1457
How about freedom to choice, much appreciated specially of those few users of pure-alsa but also by others. What if I do not want Plasma 5 at all, including its far dependencies, with the same passion how you does not want systemd or PulseAudio?
Or that "freedom of choice" is only for you, but not also for me?
You do not think is a perversion of the freedoms, if you have pure-alsa and me I cannot have pure-non-plasma?
Now these are just abstract questions, but I started to not need nothing more than XFCE.
Freedom of choice, untick KDE and be done with it, choose to remove anything that depends on it, choose to blast your OS to smithereens, Slackware is all about Choice. Now, back on topic, systemd is about removing choice, its about control, and loss of freedom. Which is why I cherish stories of its failures, oh and the really good bits are just starting. Wait until that onion gets rolled back a few layers, nasty bits indeed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.