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 have some older hardware and was wondering about 'that which shall not be named' and if there was no slackware, archlinux seemed suitable.
Got it all installed, had to figure out a "few things", kept it updated, was ok, didn't really interest me much, probably because my slackware stable is stable. Occasionally archlinux has update failures, one of those things to figure out, probably because I really don't use it or follow their web site/forum like I do slackware.
Seems that without BDFL slackware wouldn't be slackware but there has gotta be someone somewhere who could carry on, as in the donate thread, there's lots of peoples using slackware.
I have been using Slackware since 2007, few weeks ago I decided that would be the end of Slackware journey for me.
1. Slackware is the most simple/user friendly distro I have used, but that is not the case when it comes to installing a package. if I want to install a package and there is no SlackBuild or binary package, I'd have to spend at least one hour tracking deps and compiling stuff.
It's funny because I remember I was always against users who complained about package management in Slackware, believing it's better to resolve deps my self, to know every single package/file on the system (which in practice is not that worthy IMHO).
I'm leaving Slackware because when I chose to run Slackware from the beginning it was because its simplicity , but installing package in Slackware is not that simple. and chasing packages not that fun (anymore). All I need at this time is install a package easily if I needed to.
2. I honestly don't know if I might switch back or not, but who knows!
3. I replaced Slackware with Ubuntu on my work laptop, My home laptop is still running Slackware. The reason I chose Ubuntu is due to easy package management, and the knowledge gained by being a Slackware user for a decade helped me customize Ubuntu to suit all my needs.
I honestly don't know if I might switch back or not, but who knows!
Free open source software is all about having the freedom to decide what your computing experience is like. Happy to hear that Ubuntu meets your needs.
welcome on LQ, and especially the Slackware channel.
No need to apologise, it seems you are in good company here.
This might also a nice hint why several people stopped using Slackware, or just quit posting here, and the rest of the leftover might be found in the cheers for Slackware thread working on the next hang over;-)
PS: in future you might want to give the edit post function a trial :-)
having to build add-on packages (SlackBuilds) from source is unjustifiable. Especially for a distro that supports so few architectures;
keeping up with security updates for SlackBuilds is a just a mess (end result: a less than secure system);
having to hunt for a ready-made binary package, that might or might not be there, on websites like Alien's and others. Never again;
A complete lack of deadlines. Not knowing what year the next Slackware release is out... that's truly outrageous and unthinkable.
That's it. I'm done with Slackware. It's been a mostly fun and productive 9 years, but it's simply no longer worth it. I'm using Devuan now. Time will tell if it'll be a long-term relationship like with Slackware.
having to build add-on packages (SlackBuilds) from source is unjustifiable. Especially for a distro that supports so few architectures;
keeping up with security updates for SlackBuilds is a just a mess (end result: a less than secure system);
having to hunt for a ready-made binary package, that might or might not be there, on websites like Alien's and others. Never again;
A complete lack of deadlines. Not knowing what year the next Slackware release is out... that's truly outrageous and unthinkable.
That's it. I'm done with Slackware. It's been a mostly fun and productive 9 years, but it's simply no longer worth it. I'm using Devuan now. Time will tell if it'll be a long-term relationship like with Slackware.
You make a lot of strong statements without any explanation. Building add-on packages from source is unjustifiable? Why? Not knowing when the next release is coming is outrageous and unthinkable, based on what?
I like it because is small and compact like OpenBSD used it too, you have everything what you need and easy can install new things. Don't have packet manager with huge repositories, some things is happened slowly but probably because the distro packages is update from few ppl but I can live with that
I use Slackware from version 3.4
having to build add-on packages (SlackBuilds) from source is unjustifiable. Especially for a distro that supports so few architectures;
keeping up with security updates for SlackBuilds is a just a mess (end result: a less than secure system);
having to hunt for a ready-made binary package, that might or might not be there, on websites like Alien's and others. Never again;
A complete lack of deadlines. Not knowing what year the next Slackware release is out... that's truly outrageous and unthinkable.
That's it. I'm done with Slackware. It's been a mostly fun and productive 9 years, but it's simply no longer worth it. I'm using Devuan now. Time will tell if it'll be a long-term relationship like with Slackware.
I'm also curious why you consider keeping up with security updates is a mess. You can subscribe to the mailing list for notifications, track it using RSS, or manually view the changelog. Then updating is as simple as slackpkg update && slackpkg upgrade-all. However, I will admit that it's been a long time since I've heavily used another distro, so I'm interested in what makes them stand apart from what Slackware does.
Binary vs source is a personal preference, so I understand your reasoning for not liking that, however, I think calling it unjustifiable is, well, unjustifiable. There are reasons for it, even if those reasons aren't a big deal to you.
I also understand why some are not fans of the "release when it's ready" model. It can be frustrating at times if you prefer sticking with a stable release but have newer hardware than what the stable version properly supports or need/want newer versions of software but don't want to be running -current, but "outrageous and unthinkable" seems a little excessive. Many, many projects on the web don't put out release schedules and follow the "release when it's ready" model. Not everyone is happy with it, but then not everyone would be happy with a less-than-stellar Slackware release if he rushes out a release to meet some arbitrary deadline.
But I do appreciate your comments. It is nice to know. Thanks!
I'm also curious why you consider keeping up with security updates is a mess. You can subscribe to the mailing list for notifications, track it using RSS, or manually view the changelog. Then updating is as simple as slackpkg update && slackpkg upgrade-all. However, I will admit that it's been a long time since I've heavily used another distro, so I'm interested in what makes them stand apart from what Slackware does.
Binary vs source is a personal preference, so I understand your reasoning for not liking that, however, I think calling it unjustifiable is, well, unjustifiable. There are reasons for it, even if those reasons aren't a big deal to you.
I also understand why some are not fans of the "release when it's ready" model. It can be frustrating at times if you prefer sticking with a stable release but have newer hardware than what the stable version properly supports or need/want newer versions of software but don't want to be running -current, but "outrageous and unthinkable" seems a little excessive. Many, many projects on the web don't put out release schedules and follow the "release when it's ready" model. Not everyone is happy with it, but then not everyone would be happy with a less-than-stellar Slackware release if he rushes out a release to meet some arbitrary deadline.
But I do appreciate your comments. It is nice to know. Thanks!
I find these responses unfair to a poster who has made genuine and reasonable comments on the thread topic. I understand the technical arguments against the propositions, but there is a need to address the perception without personal denigration.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.