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.
I am among those who hope for a Slackware 15 soon. But I realize that there is a lot that goes into making a stable distribution that is "current" enough for ordinary users and "stable" enough to be a reliable go-to linux. The strategy I am adopting is to stop updating slackware64_current as of now. I have everything I want and it all works. If there is some crisis in Firefox or some other package that requires upgrading I will hopefully find out about it and be able to upgrade only that package. Maybe in six months or so I will want to upgrade everything again, but I am going to try and restrain myself, since I am in no way a beta tester.
I switched to current because I needed new hardware drivers in the new kernels and some newer program versions. I think the single most important hardware need is for the new AMD ryzen processors and graphics. That seems to be pretty well handled now. I also think it should be made clear to users that the mozjs packages need to be handled with removepkg and install-new. That can be a show-stopper since your computer just doesn't work right if you mess that up.
Just pissing in the wind with this post/request but screw it - when Plasma5 is FINALLY included - can it be without KDE-Pim and Akonadi? After playing with Kubuntu further (fresh install) , I checked and noticed that Akonadi and KDE-Pim were actually not installed by default *shrug*; and the mem usage via htop makes me happy about it too... So I now have another vote for Plasma5 in my book
Just pissing in the wind with this post/request but screw it - when Plasma5 is FINALLY included - can it be without KDE-Pim and Akonadi? After playing with Kubuntu further (fresh install) , I checked and noticed that Akonadi and KDE-Pim were actually not installed by default *shrug*; and the mem usage via htop makes me happy about it too... So I now have another vote for Plasma5 in my book
I confirm you, from my own experience, that Ubuntu have a packages manager with a fine dependencies resolution and multiple remote binaries repositories support.
Just because they aren't installed by default in Ubuntu, that's NOT that they are removed from Ubuntu's repositories...
Anyway, I do not this apply even remotely to Slackware, because here we should install everything or we risk to be excommunicated.
I confirm you, from my own experience, that Ubuntu have a packages manager with a fine dependencies resolution and multiple remote binaries repositories support.
Just because they aren't installed by default in Ubuntu, that's NOT that they are removed from Ubuntu's repositories...
Anyway, I do not this apply even remotely to Slackware, because here we should install everything or we risk to be excommunicated.
Normally I would agree install everything, but as the devs did not include Akonadi and KDE-Pim and Plasma5 is working just fine; I say why the hell not in this case? It would slim Plasma5 a bit, and it isn't complaining about anything.
Normally I would agree install everything, but as the devs did not include Akonadi and KDE-Pim and Plasma5 is working just fine; I say why the hell not in this case? It would slim Plasma5 a bit, and it isn't complaining about anything.
Partial installs are not allowed in Slackware. I heard that over those who dare to do this, lighting bolts will fall from heavens.
Partial installs are not allowed in Slackware. I heard that over those who dare to do this, lighting bolts will fall from heavens.
I'll take my chances - the very least, If I can somehow get a list of what deps are there for Akonadi and KDE-Pim - I'll gladly go in and remove them myself then. Again for me the major gripe about KDE in general even in KDE4 was Akonadi - now that I know even Plasma5 can run just fine without it, I am more open to giving KDE another chance; so fine if I have the option to go into the menu of the install and manually choose, I will - I just now humbly request all the dependencies so that I can remove them as well during the install of Slackware
Maybe you did not get the substance of my post. Yes, you may disagree. Yes, whatever setup you might have might work wonderfully. In my system, elogind and PAM works wonders and that might be the case for many people. OK I get that I case you did not understand it.
But still yours and mine are not all Slackware use cases by any means.
The single reason for why ConsoleKit2 was invented was purely ideological. Nobody needed it, nobody asked for it, it was just a failed anti-systemd experiment. Is there someone which still uses ConsoleKit2, excluding the Slackware? Even LFS uses elogind.
The elogind works just fine, because the today software expects a valid login1 API. No roadblocks there.
Quote:
Originally Posted by sombragris
Thus it is highly probable there are still roadblocks. That was my point.
What roadblocks? We are all grownups, then let's say the truth: he just do not want to add Plasma5 to Slackware.
Hear my words, we will hang there in the year 2025 and we will talk about the "roadblocks" of adding Plasma6 to Slackware.
While Slackware-current will still have KDE4, and there will be still hopes that 15.0 will be released in the near future, to celebrate 10 years of development.
Last edited by ZhaoLin1457; 09-26-2020 at 04:32 PM.
I just built a system very similar to the quoted link - Threadripper 3960X on Gigabyte TRX40 Designare mobo and MSI 2060 Super graphics card but no water cooling. It's using an up to date -current i.e. kernel 5.4.67, so I can say that kernel 5.8 is not strictly required. Maybe 5.8 would help with Radeon graphic cards but I have no problems yet with 5.4.
I am among those who hope for a Slackware 15 soon. But I realize that there is a lot that goes into making a stable distribution that is "current" enough for ordinary users and "stable" enough to be a reliable go-to linux. The strategy I am adopting is to stop updating slackware64_current as of now. I have everything I want and it all works. If there is some crisis in Firefox or some other package that requires upgrading I will hopefully find out about it and be able to upgrade only that package. Maybe in six months or so I will want to upgrade everything again, but I am going to try and restrain myself, since I am in no way a beta tester.
I switched to current because I needed new hardware drivers in the new kernels and some newer program versions. I think the single most important hardware need is for the new AMD ryzen processors and graphics. That seems to be pretty well handled now. I also think it should be made clear to users that the mozjs packages need to be handled with removepkg and install-new. That can be a show-stopper since your computer just doesn't work right if you mess that up.
To points. First, by switch to -current, you became a tester. Second, if a package is listed in ChangeLog.txt as "Added." and another is listed as "Removed." It should be understood the one will have to do the following:
last firmware package: kernel-firmware-20200923_afbfb5f-noarch-1.txz, is missing symbol links.
upstream remove them, could be created by copy-firmware.sh.
That does not work for me, (maybe I did something wrong) but going back to an older version (20200901 in my case)
solved the problem: Some parts of "nouveau" are missing, so there was no hw-acceleration anymore ...
At this occasion I tried the proprietary nvidia-driver (450.66), that worked with X but when going back to runlevel 3
there was no signal for the monitor! Just a "black screen" with no chance to get back a screen!
rebooting over ssh and removing that driver "solved" that self-made problem
because here we should install everything or we risk to be excommunicated.
Quote:
Partial installs are not allowed in Slackware. I heard that over those who dare to do this, lighting bolts will fall from heavens.
You are perfectly entitled to do a partial install. The problem comes with the time wasted when a lightning bolt falls, leading to threads something like:
Q. Hello roadside assist, my new Slackware model does not go. Can you help?
A. Does the engine go?
Q. Yes. What do I try next?
A. Does the engine rev when you press the accelerator?
Q. Yes. What do I try next?
A. Is the car in gear?
Q. Yes. What do I try next?
A. Then it should be going. Have you made any mods?
Q. I wanted a low profile look and took the wheels off. Would that make a difference?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
AMD Threadripper / AMD Epyc/ AMD Ryzen/ AMD Radeon Pro
Even Kubuntu devs do not like Akonadi and KDE-Pim
