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.
If PV were to say "f#ck it" and release what's in current right now as 14.3-rc1, how bad would it be?
I think Slackware has been comfortably stable over the years exactly because Pat never had such a release attitude.
Everytime, if there's no next stable release yet, without diving into details, I just prefer to think that Pat knows better and that there are technical reasons for that.
My secret dream is that 15.0 is taking a bit longer than usual because Pat has finally started to write a book - the very few of his interviews clearly do not reveal his whole vision about building and managing Slackware. And while I have enough patience to wait for next releases, I clearly don't have enough patience to wait for such a book until Pat will retire
I think Slackware has been comfortably stable over the years exactly because Pat never had such a release attitude.
Sure. I was mostly wondering what people thought about the current status of the distro. Since posting that, elogind is becoming more of a thing with Plasma. I'm still not up to speed on the status of XFCE, though I don't really use it.
I'm in no rush for 15.0 myself. Its release would signify something important to us all; that Pat has gotten everything that was thrown at him figured out. I occasionally look at the patreon page and feel a bit of relief, seeing as how we have an easy avenue to "subscribe" again and he's got the income that he should have had for quite a while now.
This is the problem - some people think theirs are the only opinions Mr Volkerding has to listen to and weigh up. But they're not; some people prefer stable, prefer KDE 4 and prefer Xfce 4.12.
This is true. Some people also prefer twm over openbox.
Do you like multilib because if 32 bit is removed then we may not have it because most of the multilib packages come from the 32 bit version of Slackware.
Multilib is not officially supported. A lot of useful things are somewhere else, so 32bit support could be there too.
I believe that a multi-national huge company has hugely different needs for its office boxes than a home user.
The point is that the customers (or end-users) of RedHat and Slackware are absolutely different, then any comparation between them makes no sense.
To put in another way, what you people do is like me going at the local car dealer and asking why my brand new car is not shipped yet, and the clerk to try to explain me that also the tanks are shipped in a certain long period.
The point is: If I want to buy a new car, I expect to buy a good car, but not a tank able to resist at a nuclear bombing.
I would be ok with a tank. But...
Short story how I switched to -current. I bought new laptop almost 2 years ago (not today or yesterday, not even a year ago). Kernel of 14.2 version brought me a lot of troubles with recognizing hardware, so I built newer kernel and replaced the old one (from patches).
So, after "buying a tank", I had to replace its turret immediately. If this is stability, I don't know what instability is.
Slackware is great, but it is not perfect. We all have desires and expectations about the future of Slackware and I think is good to share the community view of it, so the Slackware team can see what can or want to do about it. I think this might be among the reasons why ktown, csb, slackbuilds and a lot of other great contributions exists.
Personally I would like to:
- have the installer modified so it select an appropriate font size depending on the DPI or something
- have the installer to provide a set of pre-made package templates tags to generate cloud, server, desktop or developer packages, etc.
- improve the web page, update the news section with important changes (like the introduction of PAM, help for testing, etc.), and make the changelog feed visible from the main page
- engage the community to improve the documentation. At least publish the README files as articles in the web
- supporting old hardware is great, but I don't think it should compromise the ability to use modern one
- have a predictable release cycle will be a huge benefit for me, so I can plan when to update, and when I would be able to deploy a feature that requires some library or kernel version
- try to get rid of unsupported software, even if it still works
I do most of these things for myself (to some degree), and some of them are solved by current, which is what I use. Slackware is fantastic for a lot of reasons, and in every decision there are trade-offs which is up to the team, and ultimately to Patrick to make.
Lastly, I don't try to convince anybody, I'm just sharing some concerns I have. They might have no value for most.
@ gdiazlo - Some decent suggestions above but I am confused a bit by
" - try to get rid of unsupported software, even if it still works "
Technically that may for example include LILO and I find it an example of software so fundamental and so efficient that it doesn't need any further support. It's The Wheel. One can alter it with rims and whitewall tires, but it's still a wheel and a simple circle will still do just fine. Why abandon such a thing?
May be because lilo project is itself abandoned?
I also don't like grub and I use syslinux instead. And here is the strange thing. Slackware provides grub, lilo and syslinux, but installer gives you two options: lilo or skip and do it yourself (like this slur "GoToSBo").
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
