Language Selection

English French German Italian Portuguese Spanish

Solving Rubix Linux 1.0 RC2

Filed under
Linux
Reviews
-s

Rubix is a Linux distribution forked from Slackware Linux. It differs from its parent in that Rubix uses Arch Linux's 'pacman' for simplified package management with dependency resolution. They released rc2 for their upcoming version 1.0 and we took it for a little spin.

The announcement states that highlights of this release include:
* Kernel 2.6.15.1 with reiser4 support (including the installer)
* Kernel 2.4.32, vanilla and patched for grsecurity
* GCC 3.4.4 patched with Stack Smashing Protection
* Heimdal Kerberos Support
* SKey Password Support
* KDE 3.5.0
* Firefox and Thunderbird 1.5
* Xorg 6.9.0
* Udev has completely replaced hotplug for 2.6 kernels
* Cleaned up and made the boot process much faster
* Encrypted partition support through loop-aes
* Online Package Browser
* New Custom Live CD that is nearly the exact same environment every Rubix user will boot into after hard disk installation

Installation

It was stated that rubix installs from a livecd environment, but it was virtually indistinguishable from other slack-based installs. It boots up to a bash prompt and requires root login. As with most slack installers, one then types 'setup.' From there it walks it thru the install configuration in the same manner as other slack installers. One difference is that it asks where to install from, the livecd or an internet repository. Then a message appears stating that no package selection will be offered because rubix installs a bare minimum system and one should use pacman to install the rest after boot. As you might guess that first step takes a very short time. The opportunity to install grub and setup the root password happen next. Finally one is given the option of editing their rc.conf file. This is where one might setup their hostname, timezone, system clock, other modules, etc. I actually like this method because it's much faster than waiting for a new gui screen to come up for each option.

Upon first boot, one logs in as root and continues the install manually. I say manually, but one actually uses pacman to install X and kde and such. Being a binary distribution, this doesn't take too much time either, with the biggest expenditure being the downloading. At this point, one might use xorgconfig to setup their X server. I suggest setting up a regular user account as well.

        

System

Now one should be ready to log into their KDE 3.5.0 desktop. It's a default kde, but it's very stable and fast. It sits on Xorg 6.9.0 and uses gcc 3.4.4 on top of Kernel 2.6.15.1. Firefox 1.5 and OpenOffice 2.0.1 is also available from the online repository thru pacman. Gimp 2.2.10 must have been a dependency for KDE because it did not require my installing it. KDE required many many dependencies I wouldn't have thought necessary such as mysql. But at least all that good stuff gets installed with little effort from the end user. Mplayer is also available in the repository and functions very nicely other than complaining about /dev/dsp. It played any file type I threw at it. Regardless of that little error box, sound works fine not only in mplayer, but throughout. One can also install the kernel sources if need be.

A couple of packages I looked for that wasn't available are xawtv and rar/unrar. In fact, the only tv application available was mythtv. That's a bit overkill for my purposes. My only hardware problem was its failing to detect my usb scanner.

Another yummy morsel is their new online package browser. It's located on their site at http://www.rubixlinux.org/packages. This offers a much quicker way of finding if your desired package is available. If so, then one can simply "pacman" it on. So far, pacman has worked flawlessly for me and the packages work wonderfully. Even menu entries are made.

        

Conclusions

Rubix is a nice little system for the slack fan or anyone who doesn't mind a little fiddling under the bonnet. There are no gui configuration tools, but just as slack, it is simplicity at its finest. Just a few configuration files to edit to achieve the same end as heavy time consuming graphical tools offer. This is one of the reasons slack and slack based distros stay in the list of Tuxmachines' favorite distribution(s). With the addition of pacman and an expanding repository, it is a very nice, stable, and fast system. It's not fancy or what I'd refer to as "newbie-friendly," but it's a nice little system for someone with a little linux experience. It did what it advertised and it did it very well.

why Rubix

From your review it is a bit hard to tell what it is that Rubix actually offers - it uses pacman, rc.conf similar to Arch... and it has KDE. Great! Why not just run Arch then? What, if anything, makes Rubyx different?

I *think* they devote more attention to security, with things like encrypted partitions and gcc with stack smashing protection... but it's a bit hard to tell reading the review. More details please!

In my opinion, and that is directed at reviewers in general - when reviewing a distro it would be useful to pay more attention to the stated goals of the system, and how well it meets them in practice, rather than just list some superficial features.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Avidemux 2.6.13 Open-Source Video Editor Gets AAC/ADTS Import and Export

The developers of the Avidemux open-source and cross-platform video editor software have announced a new maintenance update in the 2.6 series, bringing multiple improvements, bug fixes, and a handful of new features. Read more

5 Best Linux Distros for Security

Security is nothing new to Linux distributions. Linux distros have always emphasized security and related matters like firewalls, penetration testing, anonymity, and privacy. So it is hardly surprising that security conscious distributions are common place. For instance, Distrowatch lists sixteen distros that specialize in firewalls, and four for privacy. Most of these specialty security distributions, however, share the same drawback: they are tools for experts, not average users. Only recently have security distributions tried to make security features generally accessible for desktop users. Read more

Linux Foundation and Linux

  • How IoTivity and AllJoyn Could Combine
    At the Embedded Linux Conference in April, Open Connectivity Foundation (OCF) Executive Director Mike Richmond concluded his keynote on the potential for interoperability between the OCF’s IoTivity IoT framework and the AllSeen Alliance’s AllJoyn spec by inviting to the stage Greg Burns, the chief architect of AllJoyn. Burns briefly shared his opinion that not only was there no major technical obstacle to combining these two major open source IoT specs, but that by taking the best of both standards, a hybrid could emerge that improves upon both. Later in the day, Burns gave a technical overview of how such a hybrid could be crafted in “Evolving a Best-of-Breed IoT Framework.” (See video below.) Burns stated in both talks that his opinions in no way reflect the official position of OCF or the AllSeen Alliance. At the time of the ELC talk in April, Burns had recently left his job as VP of Engineering at Qualcomm and Chair of the Technical Steering Committee at the AllSeen Alliance to take on the position of Chief IoT Software Technologist in the Open Source Technology Center at Intel Corp.
  • ​Linus Torvalds' love-hate relationship with the GPL
    Linux's founder appreciates what the GNU General Public License has given Linux, but he doesn't appreciate how some open-source lawyers are trying to enforce it in court.
  • Linus Torvalds reflects on 25 years of Linux
    LinuxCon North America concluded in Toronto, Canada on August 25th, the day Linux was celebrating its 25th anniversary. Linus Torvalds, the creator of Linux, and Dirk Hohndel, VP and chief of open source at VMware, sat down for a conversation at the event and reflected upon the past 25 years. Here are some of the highlights of that conversation.
  • 6 things you should know from Linux's first 25 years
    Red Hat was founded in 1993, two years after Linux was announced and the company has been one of the top contributors to Linux. There is a symbiotic relationship between the company and the project. Whitehurst pointed out that it’s hard to talk about the history of Red Hat without talking about Linux and vice versa.
  • There Is Talk Of Resuming OpenChrome VIA KMS/DRM Driver Development
    Two or so years back or so it was looking hopeful that the mainline Linux kernel would finally have a proper VIA DRM/KMS driver for the unfortunate ones still have VIA x86 hardware and using the integrated graphics. However, that work was ultimately abandoned but there is talk of it being restored.

Security News

  • New FairWare Ransomware targeting Linux Computers [Ed: probably just a side effect of keeping servers unpatched]
    A new attack called FaireWare Ransomware is targeting Linux users where the attackers hack a Linux server, delete the web folder, and then demand a ransom payment of two bitcoins to get their files back. In this attack, the attackers most likely do not encrypt the files, and if they do retain the files, probably just upload it to a server under their control.
  • How do we explain email to an "expert"?
    This has been a pretty wild week, more wild than usual I think we can all agree. The topic I found the most interesting wasn't about one of the countless 0day flaws, it was a story from Slate titled: In Praise of the Private Email Server The TL;DR says running your own email server is a great idea. Almost everyone came out proclaiming it a terrible idea. I agree it's a terrible idea, but this also got me thinking. How do you explain this to someone who doesn't really understand what's going on? There are three primary groups of people. 1) People who know they know nothing 2) People who think they're experts 3) People who are actually experts
  • Why the term “zero day” needs to be in your brand’s cybersecurity vocabulary
    Linux is “open source” which means anyone can look at the code and point out flaws. In that sense, I’d say Linus Torvalds doesn’t have to be as omniscient as Tim Cook. Linux source code isn’t hidden behind closed doors. My understanding is, all the Linux code is out there for anyone to see, naked for anyone to scrutinize, which is why certain countries feel safer using it–there’s no hidden agenda or secret “back door” lurking in the shadows. Does that mean Android phones are safer? That’s up for debate.