Michael Doran Home Page
Contact | Site Map | Search  
  Home > Archives > Unix Sysadmin 101 > Test Boxes
This page is deprecated: please read archives disclaimer.

Unix Sysadmin 101: What newbies need to know, but nobody tells them.

Test Boxes

test box   1 : a server used for development or testing   2 : a server where you can try things out without fear of failure   3 : a server where you can install software and make system configuration changes prior to trying them out on a production server   4 : a server that, if things go terribly wrong, your Voyager system doesn't crash, and your boss and the library director don't come asking just what the heck you thought you were doing

The "Rolls Royce"

This option would entail an exact duplication of your production system, including all hardware and software (and additional application software licenses).

Although typical for insurance companies, banks, and the like, academic libraries don't have the moola for this.

The "Cadillac"
  • Sun Enterprise 250
    • 400 MHz CPU
    • 1 x 18 GB disk
    • 1 x 36 GB disk
    • 512 MB RAM
    • 17" monitor
    • graphics card
    • Solaris media kit
  • Cost: $10,285 (retail)
You can do a lot with a test box like this, including (for most Voyager libraries) a stand-alone Continuous OPAC.
The "Honda Civic"
  • Sun Blade 100
    • 500 MHz CPU
    • 256 MB RAM
    • 2 x 20 GB disks
    • 17" monitor
    • Solaris media kit
  • Cost: $1,845 (retail)

Within the budget of most mid-size libraries.

The "Yugo"
  • Surplus PC and monitor
    • min. 75 MHz Pentium CPU
    • min. 64 MB RAM
    • min. 2 GB disk
    • CD-ROM drive
    • Solaris media kit
      (Intel platform edition)
  • Cost: about $75

Within the budget of even the most humble Voyager library. (This configuration was my first test box.) [1]

Notes

  1. See also Building a System with the Solaris OS, x86 Platform Edition, for Under $500 By Eric Rinker