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.
Arch and Slackware? Chalk and cheese. And cheese is more nutritious. Arch is OK, but I'm too lazy to deal with rolling releases. Need a break now and then from typing pacman -Syu.
I ran Arch as my primary OS for a little over a year before making the switch to Slackware. Arch in many ways surpassed the expectations I had prior to actually using it. I really didn't expect the level of stability I received from a bleeding edge distro. I thought I might end up having to fix it every other week. In reality, I had a couple of minor breakages in that time but nothing that couldn't be resolved fairly quickly. Also the things that drew me to it in the first place, its simplicity and the fact that it provides a great way of testing against the latest software and libraries were still true when I moved away from it.
The reason for switching was primarily the fact that the constant updates required too much of my attention, not just to run a few pacman commands but to consider what some of those changes will mean to me and what adjustments I might need to make. Granted for the most part very little but I still had to consider their impact (I don't like taking too many risks, especially on my primary work machine).
This started me on the hunt for something that, like Arch, had a simple design and didn't try to be too clever for its own good. Slackware seemed like an obvious choice though I must admit I was initially concerned by the lack of inbuilt dependency management. Nonetheless I made the jump and was suprised to discover that dependency management actually turned out to be something of a non-issue. I have never had the urge to move back.
That all said, Arch is a fine distro and if something dramatic ever happened in Slackware land it would probably be the first candidate shoud I need a replacement. FreeBSD would be the another obvious choice for me, though inferior hardware support and some missing proprietary software might make that a trickier option.
P.S. One area where IMHO Arch still trumps all is its Wiki. But this is not a problem as I still use it.
i tried ArchLinux once in a while and it was driving me nuts when i left the system for 3 weeks without any update and then suddenly they migrated /lib to symlink few months ago and it breaks the system into unrecoverable system. Lucky enough it's just my old laptop with no data placed on it
i can leave Slackware for whole year and then i can upgrade it safely whenever i have time
That has been my experience as well. I've run Arch a few times and I found it very annoying that the system would routinely break when updating it. Slackware is rock-steady.
@willysr, @hitest: Keep in mind that with Arch you do have to follow what is happening in the news and community (and update very regularly). You are very active here on the Slackware forums. If you had that level of commitment when running Arch (i.e. following and the news, events and discussions in the Arch world) I think it is very unlikely you would have been tripped up.
@willysr, @hitest: Keep in mind that with Arch you do have to follow what is happening in the news and community (and update very regularly). You are very active here on the Slackware forums. If you had that level of commitment when running Arch (i.e. following and the news, events and discussions in the Arch world) I think it is very unlikely you would have been tripped up.
Yes. Very true. If I read the Arch news as regularly as I read the -current changelog I would not have encountered the breakage as much. Arch is a good distro for some users. Each to his own. Slackware for me.
@ruario:
Yes, i agree with that, but even though i have read all the news, if you didn't update your system for too long, the upgrade process might be a little tricky
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.