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.
Not gone yet but deprecated yes. I also think it is a shame. Here is another quote from that previous thread.
Quote:
Originally Posted by ruario
The bigger change I noticed was how much of rc.conf has been deprecated. It used to be a "one-stop shop" to configure almost everything. Now (like most other distros) configuration is done in various files scattered throughout /etc. IMHO this removes one of the nicest features of Arch and hence it was slightly disappointing. I can see how it was necessary as Arch gears up to being a systemd-based distro. It would have been nice however if they could have held off on that (at least for a while longer).
Last edited by ruario; 03-27-2013 at 12:47 PM.
Reason: added another quote
Not gone yet but deprecated yes. I also think it is a shame. Here is another quote from that previous thread.
I know that. Five years ago I had Arch and Slackware in evaluation for replacing FreeBSD on hardware, which runs Linux but not BSD. Arch appealed to me due to rc.conf, but Slackware won, because I knew it from the 90s and it provides stable point-releases.
Today after digging into the current state of the thing, I'm so glad, that I avoided this nightmare. And I'm even more scared by systemd now.
I migrated to Arch from Slackware about 8 or 9 years ago but might install Slack again to see what changes have taken place over the years. I've always told myself that if Arch were to ever disappear, I'd return to Slackware.
Perhaps, though I prefer the packaging system on Arch and everything associated with it, from the PKGBUILD format to the AUR and how easy it is to maintain something there. So I would still pick Arch over Gentoo personally.
Why are people still saying "X distro is more stable than Y distro", etc? You can make any distro do anything you want, and as the end user, you have the option to having that stable system, depending on what you do, program, script, recode, etc.... List goes on. I enjoy arch and gentoo equally, and the same goes for slackware. Almost sounds like a d*ck measuring contest to me
The question is not "which distro to pick up" but rather "what will you be able to do with that distro"
I've seen many people using "noob" distros and do amazing stuff on a development layer, while others, would just install Slack, Arch or anything else and don't do much afterwards, except maybe being elitists about it (I'm talking about some of my friends).
Personally, one of the key components for choosing a distro is surprisingly, not an advanced technical feature but rather the friendliness of the community behind it.
In my humble opinion; what differs really about (Arch or Gentoo) and Slack, is that the latter is driven by a single person and this maintains its focus and direction and that's the secret to Slack's longevity.
Gentoo while being a very good distro has some problems and many branches came out of it (Funtoo (amazing), exherbo(experimental), sabayon (meh))
Tips to help you to choose:
- Do you want frequent updates (many times a day), bleeding edge software and gazillions of repositories? choose Arch
- Are you looking to get a grip on UNIX systems and learn in a steep but sure curve with a rock stable distro? choose Slackware
- Do you have decent hardware? Do you want to *really* get your hands dirty, build an OS from the ground up, understand your system's internals and build a distro that is tailored to your needs exactly while having your software optimized for your cpu? choose Gentoo
Last edited by spiritual_fraud; 03-27-2013 at 01:32 PM.
The question is not "which distro to pick up" but rather "what will you be able to do with that distro"
I agree and IMHO that really should be how people should look at Linux distributions (or basically any OS). For one it could lead to the conclusion one can do almost everything with about any distro. And that in turn points to the value of a distro-agnostic view of things.
The question is not "which distro to pick up" but rather "what will you be able to do with that distro"
I've seen many people using "noob" distros and do amazing stuff on a development layer, while others, would just install Slack, Arch or anything else and don't do much afterwards, except maybe being elitists about it (I'm talking about some of my friends).
Personally, one of the key components for choosing a distro is surprisingly, not an advanced technical feature but rather the friendliness of the community behind it.
In my humble opinion; what differs really about (Arch or Gentoo) and Slack, is that the latter is driven by a single person and this maintains its focus and direction and that's the secret to Slack's longevity.
Gentoo while being a very good distro has some problems and many branches came out of it (Funtoo (amazing), exherbo(experimental), sabayon (meh))
Tips to help you to choose:
- Do you want frequent updates (many times a day), bleeding edge software and gazillions of repositories? choose Arch
- Are you looking to get a grip on UNIX systems and learn in a steep but sure curve with a rock stable distro? choose Slackware
- Do you have decent hardware? Do you want to *really* get your hands dirty, build an OS from the ground up, understand your system's internals and build a distro that is tailored to your needs exactly while having your software optimized for your cpu? choose Gentoo
Those last 3 points you made are right on!
Arch, I prefer bleeding-edge for my workstaion.
Slackware will probably be one of my server distros.
I want to build linux from scratch to really understand everything.
Linux from scratch as in gentoo, or LFS? I admit, LFS is where it's at if you want to get to the nitty gritty and fully customize everything. I still use arch and gentoo, as I can't see myself installing LFS on all 12 computers I own.
Those Arch users who are considering something else might also want to look at CRUX (3.0 was released at the start of the year). Not to put you off Slackware of course. Just another option to consider.
EDIT: Check out the CRUX 3.0 Handbook to get a feel for the kind of distro it is.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.