Building the Perfect Box: How To Design Your Linux Workstation
We just got through with a lengthy explanation of why processor speed isn't that important. But nobody is going to buy a 386/25 (or even 386/50) at this point; if nothing else, you want to get a newer motherboard so you can put this week's flavor of RAM module on it. And who knows? Maybe you will end up doing real-time 3D graphics or nuclear-explosion modeling or one of the handful of applications that can really strain your processor.
So for all you processor-speed junkies out there who want to be able to wave around megahertz figures like gearheads bragging abut the compression ratios in their hot-rods, here's a simple rule:
Do buy one or two levels lower than commercial state of the art.
As of December 1996, if you look at a typical clone-maker's advertisement, you'll see that the top three systems are a Pentium Pro, a Pentium 166 and a Pentium 133. The rule of thumb tells us to skip the Pentium Pro, consider the Pentium 166, and look seriously at the 133.
Why? Because of the way manufacturers' price-performance curves are shaped. The top-of-line system is generally boob bait for corporate executives and other people with more money than sense. Chances are the system design is new and untried—if you're at the wrong point in the technology cycle, the chip may even be a pre-production sample, or an early production step with undiscovered bugs, like the infamous Pentium FDIV problem. You don't need such troubles. Better to go with a chip/motherboard combination that's been out for a while and is well known. It's not like you need the extra speed, after all.
Besides, if you buy one of these gold-plated systems, you're only going to kick yourself three months later when the price plunges by 30%. Further down the product line there's been more real competition, and the manufacturer's margins are already squeezed. There's less room for prices to fall, so you won't watch your new toy lose street value so fast. Its price will still drop, but it won't plummet sickeningly.
Again, bear in mind that the cheapest processor you can buy new today is plenty fast enough for Linux. So if dropping back to a Pentium 90 or 75 will bring you in under budget, you can do it with no regrets.
At December 1996 prices, there's really no reason to consider buying less than a 1-gigabyte disk. This is a convenient size, because “install everything” on most Linux distributions will lay out more than 540MB, but less than 1GB of stuff.
If you can afford 2GB, the natural thing to think about is buying a 2GB disk instead. But personally, I like a configuration with two 1GB disks better—one “system” disk and one “home” disk. There are several good reasons for this kind of setup. Most of them come down to the fact that you are quite a bit less likely to trash two disks at once than you are to trash a single one.
A lot of us do Linux upgrades every three months or so. Wouldn't it give you a warm, comforting feeling during your next one to be able to dismount your “home” disk in advance and know that there's no way the upgrade can possibly step on your personal files?
Or let's suppose you have a fatal disk crash. If you have only one disk, goodbye Charlie. If you have two, maybe the crashed one was your system disk, in which case you can buy another and mess around with a new Linux installation knowing your personal files are safe (see above). Or maybe it was your home disk; in that case, you can still run and do recovery stuff and basic Net communications until you can buy another home disk and restore it from backups (you did keep backups, right?).
You can even tune your disk configuration for performance this way. SCSI controllers can interleave requests to different disks, so your swapper and other system daemons will be able to use scratch files on the system disk at the same time your applications are using files on the home disk. Thus, you may find you actually get faster throughput with two smaller disks than one big one.
To get the most leverage from this effect, choose your system disk for access speed and your home disk for capacity. In December 96 I would ideally choose a 1GB fast system disk and a 2GB home disk.
First, buy your monitor. We won't go into detail about this here because the issues aren't at all specific to Linux—you can find good guidance in any DOS-related buyer's guide. There's not a whole lot of price variance among functionally equivalent monitors, since it's a mature commodity technology, so the basic question is, “how many square inches of screen can you afford?”
This is one of the areas where pinching pennies is not a good idea. You're going to be looking at your monitor for hours on end, and using the screen real estate constantly. Buy the best quality, largest screen you possibly can—it will be worth it. I personally shelled out $2,000 for a 21-inch monitor in January 1996. Though I have no regular income and this represented a significant portion of my bank account, I have never regretted it.
The reasons not to pinch pennies are also reasons why you should actually see the monitor you're contemplating before you buy it. A factory flaw like serious edge mis-convergence or a tilted yoke is not a happy thing to discover just after you've cut a check.
You may want to consider looking for a repaired or reconditioned monitor with a warranty. These are often as good as new and much cheaper.
Next, buy your card. The major issue here is matching the card to the capacity of your monitor—you don't want to pay for more card than your screen can use, and you don't want to buy too cheap a card and find it can't drive your monitor at its maximum capability.
So once you've specified your monitor, find a video card with a maximum video bandwidth equal to or just slightly higher than the monitor's. That way you know your video system is properly balanced with a minimum of wasted capacity.
There is a fair amount of price variance among equivalent video cards, so shop aggressively here. If you're on a budget, one easy thing to trade away is bit depth. Manufacturers like to include 16- and 24-bit “photographic” color as sizzle in their advertisements, but unless you're doing something like specialty photocomposition work or medical graphics, you'll never use more than 256. So you can settle for 8-bit color.
The days when XFree86 seriously constrained your choice of video card are long past. Just about anything you can buy in a clone system should work fine these days. If you're in doubt about whether the card is supported, surf over to http://www.xfree86.org/ and check out their compatibility list.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide