Download Notesfile Reference Manual - BSD, Linux, Unix and The Internet

APPENDIX A
Notesfile Installation Checklist
A.1 Installing Notesfile Code.
You can be sure that you have modified all necessary constants in the notesfile system by following this
simple checklist.
____ change to the notesfile source directory
____ tar x [reads the notesfile tape]
____ cd src
____ [edit] parms.h
____ ARCHTIME. Default for how long unmodified note strings hang around.
____ WORKSETSIZE. The default number of notes to leave in a notesfile when archiving.
____ DFLTSH. This should be left as the Bourne shell, /bin/sh -RBE
____ DFLTED. The editor to use if no NFED or EDITOR environment variable exists.
____ SEQFILE. This is the name of a file in the utility directory which contains a list of notesfiles for
users without an NFSEQ environment variable. The default is probably just fine.
____ DFLTSEQ. For users without an NFSEQ environment variable and when the file specified by the
SEQFILE definition above doesn’t exist, we finally fall back to using the notesfiles
specified by this string. The nice thing about having things in SEQFILE is that you don’t
have to recompile the notesfile software everytime you wish to change the default set of
notesfiles; instead you edit a file.
____ MAILER. The program which will do mailing. If you are in a networked environment, this
mailer should manage to route letters to far away places for you. The notesfile system only
retains the name of the destination site; a path to that site is not kept.
____ SUPERMAILER. This should be defined if you have an intelligent mail program. Intelligent
here means that you can edit the letter and other fun things.
____ PAGER. A program which shows 1 screenful of information at a time.
____ WRITE. A program which allows online user-user communication (such as /bin/write).
____ FULLDOMAIN. This defines the domain name of your local systems. For many USENET sites,
this should be ‘‘UUCP’’. Other examples include ‘‘ARPA’’ and ‘‘Uiuc.ARPA’’. This
should not include the system name. In the UIUC Computer Science Department, we have
machines named ‘‘uiucdcs’’, ‘‘uiucdcsb’’, and so on; our value for FULLDOMAIN is
‘‘Uiuc.ARPA’’. The notesfile code puts things together to yield ‘‘uiucdcsb.Uiuc.ARPA’’
as a full domain name for one of our machines. Note that you do NOT need to place a ‘‘.’’
at the beginning of the domain name; the notesfile software does this for you.
g IDDOMAIN. This switch is (for now) undefined. When defined it indicates the the unique id’s
associated with notes are to have a system component containing the system name and the
string defined by FULLDOMAIN. The eventual goal is that this will be defined.
Currently, there are problems with using long strings for unique identifiers. This is related
to the old notesfile structure which used a 10 character maximum and didn’t check for
overflow.
So for now, leave this undefined. I’m not sure when it will be good to enable this option.
____ Select a kernel type for your machine. If no kernel is selected, the code may compile but most
likely will not run.
____ PROMPT. If you wish the system to give a command prompt. Otherwise the notesfile system is
promptless.
____ USERHOST. If this is defined, the notesfile system uses the convention ‘‘user@host’’ to indicate
where an article originated. If undefined, the notesfile system uses a ‘‘host!user’’ notation.
If you are running in an environment which supports Internet style names, you may choose
to use this.
____ DYNADIR. When defined, the notesfile system will determine the default spool directory
notesfiles from /etc/passwd. The home directory for the user ‘‘notes’’ (actually whatever is