This directory (/tmp/notesdir) contains the binary data needed to
install notes on your machine.  It does almost all the work it can for
you.  You will need to edit the attached "install" script, and change a
few environment variables found there.  It also contains a safety catch
you'll have to remove to assure that the editing has been done.  If you
are a "normal" user of notes, you may only have to remove the safety
catch.

The most critical decision you'll have to make is where the notes data
itself goes.  It can take a *lot* of space if you receive net.* (the
worldwide groups).  "A lot" means thirty to fifty Megabytes.  If you are
tight for space, you may want to move the notes system to some other
file system than the default.  If the /usr file system is close to full,
or gets that way even occasionally due to uucp activity, you will
definitely want to move notes.  You'll have to decide on a file system
that has plenty of space.  Given you have such a file system identified,
go on with the instructions below.

The first thing you need to do is create a notes user, in a designated
group.  (Yes, in this case, the group is important!).  The assignment
must be to user "notes", usually in group "daemon".  Your HP-UX system
had these already set up when it arrived, so unless you have changed
them, you can leave these entries alone.  Install the new user.  His
shell and password are whatever you like (the notes system doesn't
care).  It is vital, however, that the home directory be set up
properly.  The home directory must be the same as LIBDIR in the
"install" script.  The choice is up to you, but there are two
recommendations:  if you will want the utilities kept in /usr (if its
file system is big enough), the home directory should be /usr/lib/notes.
Some prefer /usr/local/lib/notes,to keep local additions out of /usr/lib
(handy when it comes time to install the new release of Unix).  If you
want the data on another file system, use /<file_system>/notes/lib.  (If
it's going to be a file system by itself, /notes/lib is a good
suggestion.)

The other critical directory is SPOOLDIR.  This is where the data
resides, and it can get quite large.  /usr/spool/notes is the default if
/usr is big enough.  Otherwise /<file_system>/notes/spool or
/notes/spool are suggested.  It doesn't make a lot of sense to have the
programs separated from the data on a mounted volume, as neither is
particularly useful without the other.

The third directory is BINDIR, where the executables are kept.  Unless
there are site conventions to the contrary, /usr/contrib/bin is the
suggested place.  MANDIR is where users will find the manuals and be
able to read them.

You need to also decide what domain you are part of (w.r.t.  networking
standards such as ARPA RFC822).  If you don't know, use .UUCP, which is
the default.  Hewlett-Packard owned sites should use .HP, until the
mailers can handle .HP.COM.

Notes is smart enough to find it's way around if 1) BINDIR is in the
user's path, and 2) the notes entry in /etc/passwd points to a directory
containing a file "config" that has all the other critical information.

"Install" works from just this data, and installs notes.  The script
will direct you to what you should do after notes is installed, as there
is some data communications configuration to be set up.

You'll have to run "install" as root the first time, but it sets things
up so they can be updated by the notes user as subsequent releases are
made.

For most sites the following is not of interest, but if you are
particularly concerned about how your system is set up:  the script adds
rnews and nfrcv as commands in /bin (which simply exec the real thing)
and also adds them as legal command names to L.cmds.  This is the
straightforward way to make nfrcv and rnews executable, but other
solutions work if you want to set them up.  Look at the script for
details.

Now you should set up the /etc/passwd entry for notes, edit and then run
"install".
