II.f Populate the Data Directory Root
-------------------------------------
Several files are needed in the root of the data directory.

The _SERVER_ERROR.* files supplied should be copied there and *editted* as
appropriate for your site.  If your selected Hidden prefix string as
specified in your configuration file is not "_", then the filenames should
be changed by to be prefixed by that chosen Hidden prefix string:

	$ RENAME _SERVER_ERROR.* <hidden_prefix>SERVER_ERROR.*

The "SERVER_ERROR" and filename extensions should remain unchanged;
specific file extensions and the SERVER_ERROR filename are used throughout
the OpenVMS code to allow the server to specifically target error explanations
to client's users.

It is very important to edit every one of these files since, as
distributed, they tell people who want to question or complain about a
problem to contact GopherAdmin@       , lacking the address of your own
Gopher administration organization.  This gets extremely confusing for
client users when they see this incorrect information coming from your
site. 

It's wise to have an "ABOUT" file in the root directory to explain the basic
purpose intended for your Gopher Server.  This can be a hidden file (that is,
name it "_ABOUT", for example) since it will likely be directly located
through the root .LINKS file.

You'll need a root .LINKS file, which will be offered upon root connection to
any client.  This is the heart of a Gopher Server environment.  A .LINKS file
is *ANY* file that begins with "." (by default; this can be overriden with
another character or string of characters in the configuration).  These files
normally sort to the top of the directory by beginning with ".", so they are
usually found and processed before any other files are detected in a
directory.

.