VA Linux Workstation VArStation XMP
VA Linux OS 6.0 is actually a Red Hat-based CD-ROM which is customized for VA machines and their hardware. Although the systems come pre-installed, installation is quite easy and all one has to do is select the VA Workstation option from the package selection menu to get the VA wares. Obviously, you don't have to enter your hardware configurations, since either Red Hat is probing successfully or VA made sure the installer already knows.
VA Linux OS 6.0 differs from Red Hat in a number of ways, and in my mind, is an improvement. For one thing, VA's installation uses KDE instead of the other window managers, and regardless of how one feels morally about the GNOME vs. KDE debate (libQt still isn't truly free), KDE is by most accounts further developed at this point and does support several languages. I especially liked VA's account of why KDE was chosen:
The primary reasons were stability and consistency of interface. This is not a judgment against GNOME or for KDE, but merely a decision based on what is best for the novice user. It's our belief most advanced users will already have a preferred environment, which would not be GNOME or KDE in any case.
VA's variant of Red Hat looks quite nice; in fact, it's my favorite of all Red Hat variants including Red Hat itself. As far as became apparent to me, it's just a highly configured setup with a custom kernel (2.2.7-1.15smp) for the VA box. Nevertheless, the desktop looks very nice by default with a futuristic VA background and cool blue borders and buttons that look rather in tune with the whole quest to be “space age”, which comes with this millennium business.
Despite everything VA has going for it, a few small problems exist in the VA OS 6.0. Some kernel modules are compiled with an earlier kernel and require insmod -f to force them to load, which can lead to unresolved symbols. If you load the modules in the right sequence, you can usually get around this, although after I reinstalled the OS (the machine shipped with VA Linux OS 5.2) the sound modules remained dysfunctional without a kernel recompile. So, it seems to me that the weakest link in VA systems is audio. Nevertheless, it's not so hard to recompile a kernel for sound support, and these are exceedingly fast computers so kernel compilation goes quickly.
The Linux Journal benchmarks are still genuine vaporware, but as soon as they are developed, we'll print the results for this excellent VArStation. Computer systems are changing, moving from a single processor to multiple processors, supporting larger hard drives and much more RAM, and are designed for efficiency gains in areas often ignored by conventional benchmarks. In addition, greater customization of hardware can take the load off the CPU, while kernels are becoming more and more clever. As computers are whole systems rather than individual chips and pieces, the issue is not how well one of the processors performs a loop of floating-point operations, sets all the bits in memory, or scores on a bogomips test (547.23 and 545.59 for the processors on this particular VArStation), but how well the system as a whole performs. Overall system performance is dependent on many things, especially the operating system itself and how well it can manage various tasks and take advantage of hardware. Newer Linux kernels perform better.
Speaking of kernels, the most important activity of any Linux user is recompiling the kernel. Well, maybe not, when you've already got an ideal kernel as on a VA box, but it's often the biggest compilation many of us make. On a VArStation running egcs 2.91.66, my typically oversized kernel compiled with make bzImage in less than two minutes, with make modules requiring only three. make modules_install took two seconds and bzlilo ran in eleven. Although everyone's kernels are different, mine are usually too big, so yours would probably take even less time.
The machine is a true joy to use on a daily basis. There are no lags, no waiting, and not even Netscape manages to go awry. I can do neat things like play two chess engines against each other, each on a different processor—that makes for roughly 200,000 positions per second per processor. Compiling anything is a joke—it takes more time to type tar -xzf, cd and ./configure; make. In fact, although fast machines are nice as servers, the amazing compilation speed would probably save much time and money for software development firms, not to mention improve the quality of software, as one can make far more trials in a given amount of time. (Well, I for one am a practicioner of the trial-and-error approach to programming.) Besides, it boosts morale to have fast computers.
Table 1 shows the results of some common Linux benchmarks, for those interested. Keep in mind, however, that the BYTEmark tests check only a single processor, so practically speaking, the results should be doubled.
One Click, Universal Protection: Implementing Centralized Security Policies on Linux Systems
Join editor Bill Childers and Bit9's Paul Riegle on April 27 at 12pm Central to learn how to keep your Linux systems secure.
Free to Linux Journal readers.Register Now!
- Considering Legacy UNIX/Linux Issues
- Cluetrain at Fifteen
- [<Megashare>] Watch Mrs Brown's Boys Movie Online Full Movie HD 2014
- New Products
- Getting Good Vibrations with Linux
- Memory Ordering in Modern Microprocessors, Part I
- RSS Feeds
- Tech Tip: Really Simple HTTP Server with Python
- Security Hardening with Ansible
- Customizing Vim