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, for example, cannot do that. I lack the skills.
I naively expect my operating system to work for me, not the other way around. But you guys, go on and assure each other how little you need a new stable release.
Nobody was born with 'skills' as you call it, for the most part it's just experience and knowledge of OS internals accumulated over time, or lack thereof.
Quote:
Originally Posted by solarfields
However, it annoys me when users just overlook the obvious, that 14.2 is too old to run on modern hardware.
Blame the hardware vendor who only builds a driver for one specific version of windows, and doesn't share source code for that driver.
What is obvious the 'old' windows OS will not work on new hardware by design, you're either pushed to 'new' and 'improved' OS, or write your own driver from scratch.
While this is common for hardware vendors, it's not standard for all OS; i.e. linux kernel isn't supposed to break userspace so it's possible to get new hardware support for old OS.
It may be hard to fix sometimes, but sure as hell beats having a hardware vendor decide which OS you may or may not run on your property.
The grass isn't greener out there folks. Over the last little while I've tried out several distros for the heck of it and I find them sadly wanting. Very grateful for Patrick and the entire Slackware Team. Very happy to be a Slacker.
The grass isn't greener out there folks. Over the last little while I've tried out several distros for the heck of it and I find them sadly wanting. Very grateful for Patrick and the entire Slackware Team. Very happy to be a Slacker.
*** Strong Opinion Alert ***
I think it is the future that is "not greener", and we are at a point of forced sea change, and not for the better. Slackware is our refuge where we continue to build on proven ideas, while Linux itself has become very much a corporate entity now entirely under the Open Source flag and other distros chase business models void of Free Software ideals.
In the end, when keeping to the path becomes too difficult for Pat and Slackware, there will be no path with continuity for us to follow - we will change or become increasingly isolated running our privately maintained versions on aging hardware.
Free Software gave birth to the tidal wave of innovation which spawned GNU, Linux and a thousand other useful projects. But Free Software is now practically a four letter word, and our information and computing world is fundamentally changed for the worse without it as the driving force. Definitely not greener...
It was nice while it lasted. Thanks for holding the line as long as you have Pat, I hope we can continue another birthday or two or three!
or become increasingly isolated running our privately maintained versions
.. on whatever hardware we can support.
I'm actually pretty okay with this. The worst-case scenario you describe is more or less what using free software was like in the early 1990s. It wasn't as nice as the massive, intricate software ecosystem we have today, but I used it and enjoyed it.
It might not even get that bad. Let's stick by our values and see where they take us.
In the end, when keeping to the path becomes too difficult for Pat and Slackware, there will be no path with continuity for us to follow - we will change or become increasingly isolated running our privately maintained versions on aging hardware.
If it becomes impossible for Pat to maintain Slackware in its present form I will not be upset if he is forced to adapt to tidal forces and make unwanted changes to our operating system. We're a happy anomaly in the open source ocean. I am grateful that Patrick stays true to his vision for Slackware.
I thought SecureBoot would be doom for Linux, and so far, it isn't. If it becomes standard on all motherboards and unable to be turned off, then people will find a way. Back in the 90's, boot floppies were common, and it wouldn't surprise me if we need to go to the equivalent in the future.
It seems like OS development goes in waves of complexity and simplification, though, like a lot of things in the universe. We're seeing a pattern of simplification, for good or for ill. I'm concerned about the Linux ecosystem, that having been said, and what the commodification of FOSS is doing to it. Things do need to change, because hardware is changing, however. Should it go in the direction it is? I'm not sure. I think if change does happen to Slackware, it will be measured, reasoned, and not change for the sake of the newest shiny thing that doesn't work.
In the end, when keeping to the path becomes too difficult for Pat and Slackware, there will be no path with continuity for us to follow - we will change or become increasingly isolated running our privately maintained versions on aging hardware.
...
It was nice while it lasted. Thanks for holding the line as long as you have Pat, I hope we can continue another birthday or two or three!
Very true. Let us not forget how difficult it is for Pat out there. Remember this (https://www.linuxquestions.org/quest...9/#post5882751) from last year?
Man, this broke my heart.
I'm not exactly in a very good financial situation, but I tried to help, because without Slackware I don't know how I will continue to work. So, if anybody out there knows some sure way to give money to Pat, a small contribution once in a while will be good for him, and in return it will be good for the whole of the Slackware community and to our good old Slackware Linux.
I used Paypal. If there are other ways people know about, or if the man himself can, sort of, validate the most appropriate ways of contributing, that would be great.
If it becomes impossible for Pat to maintain Slackware in its present form I will not be upset if he is forced to adapt to tidal forces and make unwanted changes to our operating system. We're a happy anomaly in the open source ocean. I am grateful that Patrick stays true to his vision for Slackware.
I do not think Pat would make the 'unwanted changes'. It would be kinder to put Slackware down, allowing it to stay true to itself, than to make it into something it never was. There's no point given it an extended synthetic existence on life support just for the sake of it.
Quality of life is better than quantity. If the big 'unwanted change' seemed unavoidable, I would completely understand it if Pat decided to put it to rest rather than change Slackware into a mutant.
Last edited by Lysander666; 07-10-2019 at 08:14 AM.
I do not think Pat would make the 'unwanted changes'. It would be kinder to put Slackware down, allowing it to stay true to itself, than to make it into something it never was. There's no point given it an extended synthetic existence on life support just for the sake of it.
Quality of life is better than quantity. If the big 'unwanted change' seemed unavoidable, I would completely understand it if Pat decided to put it to rest rather than change Slackware into a mutant.
I apologize for suggesting that unsettling scenario. Like you I am very comfortable and happy with the present state of Slackware.
Haha, no need to apologise at all. I think it's inevitable in these kinds of threads. But at least we both addressed that 'potential' politely, respectfully and most importantly, namelessly.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by hitest
The grass isn't greener out there folks. Over the last little while I've tried out several distros for the heck of it and I find them sadly wanting. Very grateful for Patrick and the entire Slackware Team. Very happy to be a Slacker.
Care to share which you tried and a general thought or two about what was lacking or not up to snuff compared to Slack? Unless that's offtopic
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.