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.
There are people posting here that run 14.2 nicely with 5.13.x. Hardware support is a non-issue friends.... AND Slackware is THE easiest distro upon which to build whatever kernel you want because Slackware is Vanilla. Others? Not so much.
I'm running 14.2 with 5.13 with tomoyo on a test machine.. And you're right, it's easier on Slackware than other distroes. I run a custom Kernel on Mageia too, but to run make I need to install make and a bunch of libs, and to run menuconfig I need to install a bunch of libs, and to compile it I need to install gcc and a bunch of libs. Sounds like alot, but Mageia is actually quite good, and much more nix principle like than many other distroes. By now it's not difficult for me to do it on Mageia, because I know what I need. But in the past, getting segfaults when running menuconfig, just to realize you missed a library took some effort to figure out.
But still, it's alot more stuff to deal with than on Slackware, where everything is provided to do it, so you just do it.
On some distroes it's a nightmare to build your own Kernel, and the distro will basically fight you until death to prevent you from doing so. It's the "distro way" or the highway in many cases.
Thanks for the video. That brought back many memories.
I'm guessing that is the Avenue Grand Army in the center, going out to the west/northwest to the La Defense area at the city limits?
Thanks, again.
Last edited by cwizardone; 08-15-2021 at 04:49 PM.
It's interesting to read the doublethink observed here.
Whenever someone came whining that stable was too old, they were told to use -current as it was very stable.
I, personally, would never give that advice.
Quote:
Originally Posted by solarfields
Now someone complains of an issue in -current and the response is that -current is for testing only.
Yeah. I've been using slackware long enough that I remember when there used to be a file called "CURRENT.WARNING" in the root of the current tree. That file has silently disappeared, but I remember its contents well.
Quote:
Originally Posted by solarfields
Hopefully 15.0 is here soon and we get back to how things should be: use stable for production, not being forced to use current due to hardware demands.
That happened long time ago son.
Keep an eye on the change log.
You been in RC a long time.
Talking about that ?
Code:
Sat Jul 17 17:55:10 UTC 2021
Happy 28th birthday, Slackware! :-)
a/aaa_base-15.0-x86_64-1.txz: Upgraded.
Bump version numbers in /etc/os-release and /etc/slackware-version.
Not quite ready to freeze things for a release candidate, but getting there.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008
Rep:
Quote:
Originally Posted by enorbet
WTF? Hardware support is basically in the KERNEL, not the distro. My main Multilib 14.2 install runs 5.0.20. There are people posting here that run 14.2 nicely with 5.13.x. Hardware support is a non-issue friends.... AND Slackware is THE easiest distro upon which to build whatever kernel you want because Slackware is Vanilla. Others? Not so much.
You need both: kernel and up to date distro to support hardware: if you have too old gcc, you will not be able to compile all the latest goodies (Slackware 14.2 is good example as it fails to compile kernel with some options enabled that need gcc newer than 5.5). To be honest, LSF is vanilla but I doubt that this matter, I never had any problems with kernel installation on any of the distros that I tested. In fact I use the same kernel config file for all the distors.
Most tricky is OpenBSD, not linux.
Sat Jul 17 17:55:10 UTC 2021
Happy 28th birthday, Slackware! :-)
a/aaa_base-15.0-x86_64-1.txz: Upgraded.
Bump version numbers in /etc/os-release and /etc/slackware-version.
Not quite ready to freeze things for a release candidate, but getting there.
as I said before 15 2021-07-17 17:46
Code:
cat /etc/slackware-version
But the new Slackers today seem to miss out on old cats.
Thanks for the Backup.
Mon Aug 16 05:28:16 UTC 2021
Hey everyone, long time no see! No, I wasn't out fishing. Sadly, I haven't had
a fishing rod in my hand (or even a fishing license in my wallet) for this
entire season, but there may yet be a chance for that this year. Along with the
usual suspects, I've been trying to clear out the list of things that needed
to get done in order to reach the standard of excellence demanded from a
Slackware release, and I think we've gotten it pretty close. GCC was bumped to
version 11.2.0 (because we just can't send this out 2 versions behind), and
everything was verified to build properly or fixed up so that it did. I don't
see any benefit to another public mass rebuild, so we're not going to do one.
Anyway, without further ado, here is Slackware 15.0 release candidate one.
Consider most things frozen and the focus now to be any remaining blocker bugs.
We'll more than likely take that next Plasma bugfix release, but it's soon
time to get off this treadmill. Enjoy! :-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.