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.
From the Rubix FAQ:
"Rubix Linux was concieved during a time when the primary developer of Slackware,
Patrick Volkerding, was extremely ill. The fate of Slackware was uncertain since
it primarily used a "one man" development model. At the time, Joshua Rubin was a
happy Slackware user, but as it started to look unmaintained, he switched to
Arch Linux. Arch Linux had many advantages over Slackware, but was simply too
bleeding edge and the development did not seem well controlled. Joshua saw a
need for a Slackware-like, stable, supported distribution, with modern
ammenities such as dependency tracking package management provided with Arch
Linux's "pacman" package manager. Further, Joshua wanted to increase security,
but not in ways that would be imposing to the end user. The result ended up
being Rubix Linux."
Would you recommend the product? yes | Price you paid?: None indicated | Rating: 8
Pros:
Easy install, good package manager, security focused,
Cons:
Small repository of software so far, because this distro is so new.
This is a great product. Probably not for the very new though as it's default install is a fairly minimal CLI only. (though KDE 3.5.1 is in the main repo)
It's very Slackware like in it's configuration but rather than chmod-ing scripts in rc.d/ you add those scripts to rc.conf using ! to prevent the script from running and @ to run it in the background (ie. DAEMONS-(network !alsa @cron) )
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.