Installation Procedure

User comes in bearing a machine for installation.  We need a procedure 
to see him through.

We'll have one LAN of bridged 10BT hubs.  We will furnish all cables.
Each cable-end distal to the hub will be marked with a tag stating its
IP address, hostname, netmask, and DNS server IP.

192.168.1.1   bigbrother.cabal.gov  255.255.255.0   192.168.1.1
192.168.1.2   2.cabal.gov           255.255.255.0   192.168.1.1
192.168.1.3   3.cabal.gov           255.255.255.0   192.168.1.1
192.168.1.4   4.cabal.gov           255.255.255.0   192.168.1.1
192.168.1.5   4.cabal.gov           255.255.255.0   192.168.1.1
192.168.1.6   4.cabal.gov           255.255.255.0   192.168.1.1
192.168.1.7   4.cabal.gov           255.255.255.0   192.168.1.1
192.168.1.8   4.cabal.gov           255.255.255.0   192.168.1.1
192.168.1.9   4.cabal.gov           255.255.255.0   192.168.1.1
192.168.1.10 10.cabal.gov           255.255.255.0   192.168.1.1
192.168.1.11 11.cabal.gov           255.255.255.0   192.168.1.1
192.168.1.12 12.cabal.gov           255.255.255.0   192.168.1.1
192.168.1.13 13.cabal.gov           255.255.255.0   192.168.1.1
192.168.1.14 14.cabal.gov           255.255.255.0   192.168.1.1
192.168.1.15 15.cabal.gov           255.255.255.0   192.168.1.1
192.168.1.16 16.cabal.gov           255.255.255.0   192.168.1.1

"bigbrother" will be my machine, running bind.  It will have
NFS export, and both regular CD and a CDR drive.  And lots of 
disk space.  And ftp'able files.  And Apache, with informational
pages (if I have time to write them).

I can make sure I have these patch cables pre-assembled and ready
to go.  (My port is only a four-banger, but we can use multiples
using crossover cables.  Other ports _will_ be brought.)

I do not intend to interconnect this network to the Internet, so
the private IPs (RFC 1597) and joke domain name are not a problem.

A volunteer checks in the machine.  Check-in must be complete BEFORE
the machine is allowed to be connected.  (SVLUG's InstallFest network 
went screwy because of bizarre IP traffic emitted by non-organised
volunteers who didn't know what they were doing.)

The volunteer also requires of the machine owner a signed disclaimer
and release of liability.  We need this because of data on the owners'
hard drives, and because of potential monitor damage if X gets badly
misconfigured.

I'd suggest that Linux problem-solving cases be physically off to one 
side, and installations off on the other.

Information sheets about BALUG, SFpcUG, SVLUG, and BALE should be 
handed out.