I am providing a skeletal set of control files that you could use to allow
a client to "sup"  from a local repository.  You should read the sup manual
page and decide how sup works.

In a typical directory, say src.lib, you will find the following files:
	logfile
	host
	crypt
	prefix
	list

The logfile will record the address and date of hosts drawing data from the
repository.  If it does not exist, then this information is not logged.

The host file contains the names of hosts that are allowed to request data.
If the file does not exist, then any host that knows the crypt may request
data.  After the hostname, you may specify a password that must be used by
the host in requesting data.

The crypt is the password that the client must specify in as the crypt=
field of its control file.  This may be overridden as indicated above on
a per host basis.  I have left a placeholder "CRYPT" in this file.

The prefix file specifies the pathname on the repository to "cd" to before
interpretting the "list" of files to supply.  Again, I have left a rough
indication of what the path should be.

Lastly, the list file specifies what files relative to the prefix should be
transfered.  The data supplied are probably correct for your situation.

To be a bit more concrete, the repository is on the host x29.mach.cs.cmu.edu
at CMU.  The relevant files are located under /i386, which basically is
the root for the I386 file system.  The sources are as expected in
/i386/usr/src and kernel in /i386/usr/src/sys.  The control file directories
live under /i386/sup. So the prefix file (for src.lib [in /i386/sup/src.lib])
would contain the line:
/i386/usr/src/lib
(BASE in the prototype file would be /i386.)

The line in the local_client control file that requests this collection
would be
src.local  host=x29.mach.cs.cmu.edu hostbase=/i386 base=/usr/src prefix=lib crypt=CRYPT
As you see, SERVER is x29.mach.cs.cmu.edu and /SERVER_CONTROL_DIRECTORY_BASE 
is /i386.  base=/usr/src says that we store the client state files in
/usr/src and the prefix=lib means that the data files are rooted at the
directory lib relative to the base.
