read-me

<B>Digital的Unix操作系统VAX 4.2源码</B>

   MH                                                               MH-GEN(8)



   NAME
     mh-gen - generating the MH system

   READ THIS
     This documentation describes how to configure, generate, and install the
     UCI version of the RAND _M_H system.  Be certain to read this document
     completely before you begin.  You probably will also want to familiarize
     yourself with the _M_H Administrator's Guide before you install _M_H.

   DISCLAIMER
     Although the _M_H system was originally developed by the RAND Corporation,
     and is now in the public domain, the RAND Corporation assumes no respon-
     sibility for _M_H or this particular modification of _M_H.

     In addition, the Regents of the University of California issue the fol-
     lowing disclaimer in regard to the UCI version of _M_H:
          "Although each program has been tested by its contributor, no war-
          ranty, express or implied, is made by the contributor or the
          University of California, as to the accuracy and functioning of the
          program and related program material, nor shall the fact of distri-
          bution constitute any such warranty, and no responsibility is
          assumed by the contributor or the University of California in con-
          nection herewith."

     This version of _M_H is in the public domain, and as such, there are no
     real restrictions on its use.  The _M_H source code and documentation have
     no licensing restrictions whatsoever.  As a courtesy, the authors ask
     only that you provide appropriate credit to the RAND Corporation and the
     University of California for having developed the software.

   GETTING HELP
     _M_H is a software package that is neither supported by the RAND Corpora-
     tion nor the University of California.  However, since we do use the
     software ourselves and plan to continue using (and improving) _M_H, bug
     reports and their associated fixes should be reported back to us so that
     we may include them in future releases.  The current computer mailbox
     for _M_H is [e-mail] (in the ARPA Internet), and
     ...!ucbvax!ucivax!bug-mh (UUCP).

     Presently, there are two Internet discussion groups,
     [e-mail] and [e-mail].  MH-Workers is for peo-
     ple discussing code changes to _M_H.  MH-Users is for general discussion
     about how to use _M_H.  MH-Users is bi-directionally gatewayed into USENET
     as comp.mail.mh.

   HOW TO GET MH
     Since you probably already have _M_H, you may not need to read this unless
     you suspect you have an old version.  There are two ways to get the
     latest release:

     1.  If you can FTP to the ARPA Internet, use anonymous FTP to
     ics.uci.edu [128.195.1.1] and retrieve the file pub/mh/mh-6.7.tar.Z.
     This is a tar image after being run through the compress program


   [mh.6]                                                                   1






   MH-GEN(8)                                                               MH


     (approximately 1.5MB).  There should also be a README file in that
     directory which tells what the current release of _M_H is, and how to get
     updates.

     This tar file is also available on louie.udel.edu [128.175.1.3] in
     portal/mh-6.7.tar.Z.  You may also find MH on various other hosts; to
     make sure you get the latest version and don't waste your time re-fixing
     bugs, it's best to get it from either ics.uci.edu or louie.udel.edu.

     2.  You can send $75 US to the address below.  This covers the cost of a
     6250 BPI 9-track magtape, handling, and shipping.  In addition, you'll
     get a laser-printed hard-copy of the entire MH documentation set.  Be
     sure to include your USPS address with your check.  Checks must be drawn
     on U.S. funds and should be made payable to:

               Regents of the University of California

     The distribution address is:

               Computing Support Group
               Attn: MH distribution
               Department of Information and Computer Science
               University of California, Irvine
               Irvine, CA  92717

               714/856-7554

     Sadly, if you just want the hard-copies of the documentation, you still
     have to pay the $75.  The tar image has the documentation source (the
     manual is in roff format, but the rest are in TeX format).  Postscript
     formatted versions of the TeX papers are available, as are crude tty-
     conversions of those papers.

   SYNOPSIS
     MAKE

   DESCRIPTION
     This is a description of how one can bring up an _M_H system.  It is
     assumed that you have super-user privileges in order to (re-)install _M_H.
     Super-user privileges are not required to configure or generate _M_H.

     Become the super-user and create a new directory under /usr/src/local/
     (or whatever) for the _M_H area.  Traditionally, the directory's name
     should be mh/.  The distribution tape contains the hierarchy for the
     mh.6/ directory.  Bring the sources on-line:

     # mkdir /usr/src/local/mh
     % cd /usr/src/local/mh
     % tar xv

   CONFIGURATION
     First, go to the conf/ directory.

     % cd conf/


   2                                                                   [mh.6]






   MH                                                               MH-GEN(8)



     This directory contains files that will produce source files tailored
     for your choice of _M_H configuration.  You should edit only the file MH.
     This file contains configuration directives.  These configuration direc-
     tives are read by the _m_h_c_o_n_f_i_g program to produce customized files.  For
     examples of various configurations, look in the directory
     conf/examples/.  The file MH provided in conf/ is a reasonable default.

     Here are the _M_H configuration options available:
     bin: /usr/local
          The directory where user-invoked programs go (see manual section
          1).

     debug: off
          Support for debug mode of _M_H.  Don't use this unless you know what
          you're doing, which isn't likely if you're reading this document!

     etc: /usr/local/lib/mh
          The directory where pgm-invoked programs go (see manual section 8).

     mail: /usr/spool/mail
          The directory where the maildrops are stored.  If this pathname is
          absolute (i.e., begins with a / ), then the user's maildrop is a
          file called $USER in this directory.  If the pathname is not abso-
          lute, then the user's maildrop is in the user's home directory
          under the given name.

     mailgroup: off
          If set, _i_n_c is made set-group-id to this group name.  Some SYS5
          systems want this to be set to "mail".

     mandir: /usr/man
          The parent directory of the manual entries.

     manuals: standard
          Where manual entries should be installed, relative to the directory
          given with "mandir".  Either "local" to install manual entries
          under manl/, or "new" to install manual entries under mann/, or
          "old" to install manual entries under mano/, or "standard" to
          install manual entries under man?/, or "gen" to generate but not
          install them, or "none" to neither generate nor install them.  For
          example, to install manual entries under /usr/man/u_man/man?, use
          "standard" and /usr/man/u_man for "mandir".

     chown: /etc/chown
          The location of the _c_h_o_w_n (8) on your system.  If _c_h_o_w_n is in your
          search path, just use the value of "chown".  On SYS5 systems, this
          should probably be "/bin/chown".

     editor: prompter
          The default editor for _M_H.

     remove: mv -f
          How _M_H should backup existing files when installing a new file.


   [mh.6]                                                                   3






   MH-GEN(8)                                                               MH


     mts: sendmail
          Which message transport system to use.  Either "mmdf" to use _M_M_D_F
          as the transport system, "mmdf2" to use _M_M_D_F-_I_I as the transport
          system, "sendmail" to have _S_e_n_d_M_a_i_l as the transport system, or,
          "mh" to have _M_H as the transport system.

          On UNIX systems supporting TCP/IP networking via sockets you can
          add the suffix "/smtp" to the mts setting.  This often yields a
          superior interface as _M_H will post mail with the local _S_M_T_P server
          instead of interacting directly with _M_M_D_F or _S_e_n_d_M_a_i_l.  Hence, for
          TCP/IP UNIX systems, the "/smtp" suffix to either "sendmail" or
          "mmdf2" is the preferred MTS configuration.  The "/smtp" suffix is
          described in detail in the _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e; be sure to set
          "servers:" as described in _m_h-_t_a_i_l_o_r (8) if you use this option.

     bboards: off
          If "on", include support for the UCI BBoards facility.  BBoards may
          be enabled with any mts setting.  If "off", the BBoard reading pro-
          gram _b_b_c will not be installed.  If "nntp", include support for the
          UCI BBoards facility to read the Network News via the NNTP.  If
          "pop" (formerly "popbboards: on"), include support for the UCI
          BBoards facility via the POP3 service; this setting requires
          "pop: on".

     bbdelivery: off
          If "off", the BBoards delivery agent and library files will not be
          installed.  If "on", and you set "bboards:" to something besides
          "off", then the BBoards delivery agent and library files will be
          installed in the _b_b_h_o_m_e directory (see below).  To read remote
          BBoards, the usual configuration would have _b_b_c talk to a _P_O_P_3 or
          _N_N_T_P server.  However, it may be useful to set this to "off" if you
          NFS mount the _b_b_h_o_m_e directory from another host and want to use
          _b_b_c to read those files directly.

     bbhome: /usr/spool/bboards
          The home directory for the BBoards user.

     mf: off
          Support for mail filtering on those systems in which the message
          transport system isn't integrated with _U_U_C_P This option is strictly
          for an _M_H system using either _M_M_D_F-_I as its transport system or one
          using "stand-alone delivery".

     pop: off
          Support for POP service.  This allows local delivery for non-local
          users (a major win).  See support/pop/pop.rfc for more information
          on the POP.  This option currently works only on UNIX systems with
          TCP/IP sockets.  (It doesn't hurt to enable this option regardless
          of whether or not you intend to use POP.) If POP is enabled, there
          are three additional options which are of interest: "RPOP", "DPOP"
          and "POP2".  The first indicates that support for the UNIX variant
          of POP, RPOP, which uses privileged sockets for authentication be
          enabled.  This peacefully co-exists with the standard POP.  The
          "DPOP" option indicates that POP subscribers do not have entries in


   4                                                                   [mh.6]






   MH                                                               MH-GEN(8)


          the _p_a_s_s_w_d (5) file, and instead have their own separate database
          (another major win).  The "POP2" option indicates that the _M_H POP
          daemon should speak the older POP2 protocol in addition to the _M_H
          POP3 protocol - a major win.  All of these options can be enabled
          via an "options" directive in the _M_H configuration file.

     options:
          `-D' options to _c_c (1).  If you don't know what an option does, it
          probably doesn't apply to you.

          ALTOS
               Use on XENIX/v7 systems.  Also, be sure to use "options V7".

          ATHENA
               Makes _r_e_p_l `-nocc all' the default instead of `-cc all'.  You
               may want to enable this if you're using _x_m_h.

          ATZ
               Directs _M_H to use alpha-timezones whenever possible.

          BANG
               Directs _M_H to favor `!' over `@' in addressing.

          BERK
               Optional for for 4.{2,3}BSD sites running SendMail.  Disables
               nearly all of the RFC822 address and header-parsing routines
               in favor of recognizing such formats as ASCnet, and so on.  If
               you don't need to disable the parser for this reason, you
               probably want to use "options DUMB" instead.

          BIND
               If you are running with the BIND code on UNIX systems with
               TCP/IP sockets (e.g. 4.{2,3}BSD), be sure to define this.

          BSD41A
               Use on 4.1a Berkeley UNIX systems.

          BSD42
               Use on Berkeley UNIX systems on or after 4.2BSD.

          BSD43
               Use on 4.3 Berkeley UNIX systems.  Also, be sure to use
               "options BSD42".  If _o_p_e_n_l_o_g (3) (see "man 3 syslog") takes
               three arguments instead of two, and your _w_r_i_t_e (1) command is
               set-group-id to group "tty", use this option.  If only one of
               these conditions is true, you lose.

          COMPAT
               If you previously ran a version of _M_H earlier than mh.4 use
               this option.  After a short grace period, remove it and re-
               {configure,generate,install} everything.

          DBM
               Use this option if your _g_e_t_p_w_e_n_t (3) routines read a dbm


   [mh.6]                                                                   5