read-me

早期freebsd实现

MH-GEN(8)             MAINTENANCE COMMANDS              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.  A copy can be
     found in the file doc/ADMIN.doc is the _M_H sources.

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

     In addition, the Regents of the University of California
     issue the following disclaimer in regard to the UCI version
     of _M_H:
          "Although each program has been tested by its contribu-
          tor, no warranty, 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 distribution
          constitute any such warranty, and no responsibility is
          assumed by the contributor or the University of Cali-
          fornia in connection 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 what-
     soever.  As a courtesy, the authors ask only that you pro-
     vide 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 Corporation 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 people 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.




[mh.6]                Last change: MH.6.8.3                     1






MH-GEN(8)             MAINTENANCE COMMANDS              MH-GEN(8)



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 ftp.ics.uci.edu [128.195.1.1] and retrieve the file
     pub/mh/mh-6.8.tar.Z.  This is a tar image after being run
     through the compress program (approximately 1.8MB).  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.8.tar.Z.  You may also find MH
     on various other hosts; to make sure you get the latest ver-
     sion and don't waste your time re-fixing bugs, it's best to
     get it from either ftp.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 ship-
     ping.  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:

               Univeristy of California at Irvine
               Office of Academic Computing
               360 Computer Science
               Irvine, CA  92717  USA

               [phone]

     Sadly, if you just want the hard-copies of the documenta-
     tion, 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.




[mh.6]                Last change: MH.6.8.3                     2






MH-GEN(8)             MAINTENANCE COMMANDS              MH-GEN(8)



     Become the super-user and cd to /usr/src/local/ (or whatever
     you keep your local sources).  The distribution tape con-
     tains the hierarchy for the mh.6-8/ directory.  Bring the
     sources on-line:

     # cd /usr/src/local
     % tar xv
     % cd mh-6.8

CONFIGURATION
     First, go to the conf/ directory.

     % cd conf/

     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 directives 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 direc-
     tory conf/examples/.  The file MH provided in conf/ is a
     reasonable default.  Lines beginning with `#' are comments,
     and are not otherwise interpreted.

     Here are the _M_H configuration directives available.  Be sure
     to read through this list completely before attempting to
     decide what directives are appropriate for your system.

     More information on some of these options is available in
     the the _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e.  If you do not have a printed
     copy, you should configure your system with the default con-
     figuration file, MH, then generate and print a copy of the
     guide (as described below).

  Installation paths
     bin: /usr/local
          The directory where user-invoked programs go (see
          manual section 1).

     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 direc-
          tory.  If the pathname is not absolute, then the user's
          maildrop is in the user's home directory under the
          given name.




[mh.6]                Last change: MH.6.8.3                     3






MH-GEN(8)             MAINTENANCE COMMANDS              MH-GEN(8)



     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 "bsd44" to install manual
          entries as man?/_p_a_g_e.0, or "gen" to generate but not
          install them, or "none" to neither generate nor install
          them.

          Any of these values may have the suffix "/cat" appended
          to it.   In that case, the manual entries will be for-
          matted with "nroff -man" and they will be installed in
          the corresponding "cat?" directories.

          For example, to install manual entries under
          /usr/man/u_man/man?, use "standard" and /usr/man/u_man
          for "mandir".  To install formatted manual entires
          under /usr/contrib/man/cat?, use "standard/cat" and
          /usr/contrib/man for "mandir".  To install formatted
          manual entries using the BSD44 convention, use
          "bsd44/cat".

     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".

     cp: cp
          The command to copy files when installing, if not "cp".
          (Some sites use "cp -p".)

     ln: ln
          The command to link files together in the source tree,
          if not "ln".  If you're using something like lndir to
          keep your compile tree separate from your source tree,
          set this to "ln -s" or "cp".

     remove: mv -f
          How _M_H should make backup copies of existing files when
          installing new files.  To simply remove the old files,
          use "rm -f".

  Compiler/loader
     cc: cc
          The name of your C compiler, if not "cc".

     ccoptions: -O



[mh.6]                Last change: MH.6.8.3                     4






MH-GEN(8)             MAINTENANCE COMMANDS              MH-GEN(8)



          Options given directly to _c_c(1).  The most common is
          "-M" if you're running _M_H on an ALTOS.  This defaults
          to "-O".  If you define this and want to keep "-O", be
          sure to include it explicitly.  If you're using the _G_N_U
          C compiler, it should include `-traditional'.  See
          "options:" for `-D' options.

     curses: -lcurses -ltermlib
          This should be the loader option required to load the
          _t_e_r_m_c_a_p(3) and _c_u_r_s_e_s(3) libraries on your system.  On
          SYS5 systems, it probably should be just "-lcurses".
          Some sites have reported that both "-lcurses" and
          "-ltermlib" are necessary.

     ldoptions: -s
          Options given directly to _l_d(1) (via _c_c) at the begin-
          ning of the command line.  Useful for machines which
          require arguments to tell _l_d to increase the stack
          space (e.g. the Gould, which uses "-m 8").  Usually,
          "-s" is a good choice in any event.

     ldoptlibs:
          Options given directly to _l_d(1) (via _c_c) at the end of
          the command line.  The two most common are: "-ldbm" if
          you're running MMDF with the _d_b_m package; and, "-lndir"
          if you are generating _M_H on a system which does not
          load the new directory access mechanism by default
          (e.g., 4.1BSD, SYS5).  If you don't have _l_i_b_n_d_i_r on
          your system, the sources are in miscellany/libndir/.

     lex: lex -nt
          Alternative version of _l_e_x.  Used in zotnet/tws/.

     oldload: off
          This controls how _M_H will try to process library object
          files to eliminate local symbols.  Support for the
          ALTOS loader if "on".  Support for loaders not handling
          `-x -r' correctly if "none".

     ranlib: on
          Support for systems with _r_a_n_l_i_b(1).  For SYSTEM 5 sys-
          tems, this should be "off" which tells _M_H to use _l_o_r_d_e_r
          and _t_s_o_r_t instead.  Some SYSTEM 5 sites reported that
          running this isn't always sufficient.  If this is the
          case, then you should edit conf/makefiles/uip to
          include ../sbr/libmh.a and ../zotnet/libzot.a twice in
          the LIBES variable.

  Message Transport System
     mts: sendmail
          Which message transport system to use.  Either "mmdf"
          to use _M_M_D_F as the transport system, "mmdf2" to use



[mh.6]                Last change: MH.6.8.3                     5






MH-GEN(8)             MAINTENANCE COMMANDS              MH-GEN(8)



          _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, "zmailer" to have
          _Z_M_A_I_L_E_R as the transport system, or, "mh" to have _M_H as
          the transport system.

          On UNIX systems supporting TCP/IP networking via sock-
          ets 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.

     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".

  UCI BBoards Facility
     bboards: off
          If "on", include support for the UCI BBoards facility.
          BBoards may be enabled with any mts setting.  If "off",