comparc@twwells.uucp (comp.archives) (11/12/88)
Here is a form to fill out if you want to register an archive site.
You can leave most items blank, all I really insist on is the minimum
information needed by someone who would like to get to your archive.
---
What is the name of the site that holds the archive? This should be
a domain name of some kind. If you are a uucp site, make it site.UUCP.
Site name:
What time zone is the site located in? This should be the three
letter abbreviation, like EST, etc.
Time zone:
When are the best and worse times of the day to use your archive?
This should be a measure of typical system load, and should not
include times when access to the site is not allowed. You can
specify days of the week as well as hours and minutes.
Best times:
Worst times:
---
Your site may have more than one archive. If that is the case,
duplicate the rest of the form and fill it in for each archive, or
send in multiple forms.
---
What is your archive called?
Archive title:
Who administers the archive? The e-mail address should be of the form
user@domainname.
E-mail address for the administrator:
Name of the administrator:
What address can someone mail to if they need help or information?
Mailing address:
---
If your site can be reached via uucp, fill in this section of the
form.
Where is the archive information kept? This is a directory which is
the leading path of all archive requests. If `~' is valid, as in
requests are from /usr/spool/uucppublic, then specify that. If there
is more than one archive directory or L.sys entry, make copies of
these two lines and fill in the duplicates. It is perfectly valid
for there to be some directories which are accessible only through a
subset of the L.sys entries. This is useful if you have directories
which have large files in them and you want to make them available
only through a faster line or at specific times.
Archive directory:
L.sys entry:
---
If your site can be reached via ftp, fill in this section of the
form. The ftp address is normally the same as the site address, but I
suppose there are cases where it wouldn't. (Perhaps the archive site
keeps its archives on different machines in its domain?)
Ftp address:
Internet address:
Archive directory:
Access times:
---
If your site can be reached by other than uucp or ftp, e.g., a mail
based server, enter the method on the following line and then follow
that with a brief description of how to access your archive.
Access method:
---
If your archive has index files available, fill in this section.
Duplicate this section for each index file.
If your site has more than one access method, which access methods is
the index file available through?
Index access method:
What is name of the file containing the index?
Index file name:
How big, in K, is this index file? An approximate size is OK.
Index file size:
If the index file is compressed or otherwise encoded, what programs
are needed to read it?
Index file tools:
What does this particular index file describe?
Index contains:
---
If your archive has a particular focus or purpose, enter a list of
keywords that describe this.
Archive keywords:
---
Write a short (preferably 10 lines or less) description of your
archive. This goes into the archive database.
---
If you'd like, you can append a long description of your archive to
this registration. This long description goes out with the posting of
your registration, but does not go into the archive database.
---
Bill
{uunet|novavax}!proxftl!twwells!bill
send comp.archives postings to twwells!comp-archives
send comp.archives related mail to twwells!comp-archives-requestcomparc@twwells.uucp (comp.archives) (01/03/89)
Here is a form to fill out if you want to register an archive site.
You can leave most items blank, all I really insist on is the minimum
information needed by someone who would like to get to your archive.
---
What is the name of the site that holds the archive? This should be
a domain name of some kind. If you are a uucp site, make it site.UUCP.
Site name:
What time zone is the site located in? This should be the three
letter abbreviation, like EST, etc.
Time zone:
When are the best and worse times of the day to use your archive?
This should be a measure of typical system load, and should not
include times when access to the site is not allowed. You can
specify days of the week as well as hours and minutes.
Best times:
Worst times:
---
Your site may have more than one archive. If that is the case,
duplicate the rest of the form and fill it in for each archive, or
send in multiple forms.
---
What is your archive called?
Archive title:
Who administers the archive? The e-mail address should be of the form
user@domainname.
E-mail address for the administrator:
Name of the administrator:
What address can someone mail to if they need help or information?
Mailing address:
---
If your site can be reached via uucp, fill in this section of the
form.
Where is the archive information kept? This is a directory which is
the leading path of all archive requests. If `~' is valid, as in
requests are from /usr/spool/uucppublic, then specify that. If there
is more than one archive directory or L.sys entry, make copies of
these two lines and fill in the duplicates. It is perfectly valid
for there to be some directories which are accessible only through a
subset of the L.sys entries. This is useful if you have directories
which have large files in them and you want to make them available
only through a faster line or at specific times.
Archive directory:
L.sys entry:
---
If your site can be reached via ftp, fill in this section of the
form.
Ftp address:
Internet address:
Archive directory:
Access times:
---
If your site can be reached through fidonet, fill in the following
line:
Fidonet access info:
---
If your site is a BBS, fill in the this section. If you have
different kinds of modems on different lines, duplicate this section
and fill it out for each kind of modem. The modem settings should
include the number of data bits, the parity, and the number of stop
bits. The protocols supported line should be filled in with each of
the protocols that can be used to download files.
Phone numbers:
Access times:
Modem settings:
Protocols supported:
---
If your site can be reached by other than any of the above, e.g., a
mail based server, enter the method on the following line and then
follow that with a brief description of how to access your archive.
Access method:
---
If your archive has index or README files available, fill in this
section. Duplicate this section for each file.
If your site has more than one access method, which access methods is
the index file available through?
Index access method:
What is name of the file containing the index?
Index file name:
How big, in K, is this index file? An approximate size is OK.
Index file size:
If the index file is compressed or otherwise encoded, what programs
are needed to read it?
Index file tools:
What does this particular index file describe?
Index contains:
---
If your archive has a particular focus or purpose, enter a list of
keywords that describe this.
Archive keywords:
---
Write a short (preferably 10 lines or less) description of your
archive. This goes into the archive database.
---
If you'd like, you can append a long description of your archive to
this registration. This long description goes out with the posting of
your registration, but does not go into the archive database.
---
Bill
{ uunet!proxftl | novavax } !twwells!bill
send comp.archives postings to twwells!comp-archives
send comp.archives related mail to twwells!comp-archives-request