projects / unix-history / blame
? search:
summary | tags | clone url | shortlog | log | commit | commitdiff | tree
blob | blame (incremental) | history | HEAD
BSD 4_4_Lite2 development
[unix-history] / usr / src / contrib / mh-6.8.3a / READ-ME
CommitLineData
3b5b17f7
C		 1
2
3
4MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
5
6
7
8NAME
9 mh-gen - generating the MH system
10
11READ THIS
12 This documentation describes how to configure, generate, and
13 install the UCI version of the RAND _\bM_\bH system. Be certain
14 to read this document completely before you begin. You
15 probably will also want to familiarize yourself with the _\bM_\bH
16 Administrator's Guide before you install _\bM_\bH. A copy can be
17 found in the file doc/ADMIN.doc is the _\bM_\bH sources.
18
19DISCLAIMER
20 Although the _\bM_\bH system was originally developed by the RAND
21 Corporation, and is now in the public domain, the RAND Cor-
22 poration assumes no responsibility for _\bM_\bH or this particular
23 modification of _\bM_\bH.
24
25 In addition, the Regents of the University of California
26 issue the following disclaimer in regard to the UCI version
27 of _\bM_\bH:
28 "Although each program has been tested by its contribu-
29 tor, no warranty, express or implied, is made by the
30 contributor or the University of California, as to the
31 accuracy and functioning of the program and related
32 program material, nor shall the fact of distribution
33 constitute any such warranty, and no responsibility is
34 assumed by the contributor or the University of Cali-
35 fornia in connection herewith."
36
37 This version of _\bM_\bH is in the public domain, and as such,
38 there are no real restrictions on its use. The _\bM_\bH source
39 code and documentation have no licensing restrictions what-
40 soever. As a courtesy, the authors ask only that you pro-
41 vide appropriate credit to the RAND Corporation and the
42 University of California for having developed the software.
43
44GETTING HELP
45 _\bM_\bH is a software package that is neither supported by the
46 RAND Corporation nor the University of California. However,
47 since we do use the software ourselves and plan to continue
48 using (and improving) _\bM_\bH, bug reports and their associated
49 fixes should be reported back to us so that we may include
50 them in future releases. The current computer mailbox for
51 _\bM_\bH is Bug-MH@ICS.UCI.EDU (in the ARPA Internet), and
52 ...!ucbvax!ucivax!bug-mh (UUCP).
53
54 Presently, there are two Internet discussion groups,
55 MH-Users@ICS.UCI.EDU and MH-Workers@ICS.UCI.EDU. MH-Workers
56 is for people discussing code changes to _\bM_\bH. MH-Users is
57 for general discussion about how to use _\bM_\bH. MH-Users is
58 bi-directionally gatewayed into USENET as comp.mail.mh.
59
60
61
62
63[mh.6] Last change: MH.6.8.3 1
64
65
66
67
68
69
70MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
71
72
73
74HOW TO GET MH
75 Since you probably already have _\bM_\bH, you may not need to read
76 this unless you suspect you have an old version. There are
77 two ways to get the latest release:
78
79 1. If you can FTP to the ARPA Internet, use anonymous FTP
80 to ftp.ics.uci.edu [128.195.1.1] and retrieve the file
81 pub/mh/mh-6.8.tar.Z. This is a tar image after being run
82 through the compress program (approximately 1.8MB). There
83 should also be a README file in that directory which tells
84 what the current release of _\bM_\bH is, and how to get updates.
85
86 This tar file is also available on louie.udel.edu
87 [128.175.1.3] in portal/mh-6.8.tar.Z. You may also find MH
88 on various other hosts; to make sure you get the latest ver-
89 sion and don't waste your time re-fixing bugs, it's best to
90 get it from either ftp.ics.uci.edu or louie.udel.edu.
91
92 2. You can send $75 US to the address below. This covers
93 the cost of a 6250 BPI 9-track magtape, handling, and ship-
94 ping. In addition, you'll get a laser-printed hard-copy of
95 the entire MH documentation set. Be sure to include your
96 USPS address with your check. Checks must be drawn on U.S.
97 funds and should be made payable to:
98
99 Regents of the University of California
100
101 The distribution address is:
102
103 Univeristy of California at Irvine
104 Office of Academic Computing
105 360 Computer Science
106 Irvine, CA 92717 USA
107
108 +1 714 856 5153
109
110 Sadly, if you just want the hard-copies of the documenta-
111 tion, you still have to pay the $75. The tar image has the
112 documentation source (the manual is in roff format, but the
113 rest are in TeX format). Postscript formatted versions of
114 the TeX papers are available, as are crude tty-conversions
115 of those papers.
116
117SYNOPSIS
118 MAKE
119
120DESCRIPTION
121 This is a description of how one can bring up an _\bM_\bH system.
122 It is assumed that you have super-user privileges in order
123 to (re-)install _\bM_\bH. Super-user privileges are not required
124 to configure or generate _\bM_\bH.
125
126
127
128
129[mh.6] Last change: MH.6.8.3 2
130
131
132
133
134
135
136MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
137
138
139
140 Become the super-user and cd to /usr/src/local/ (or whatever
141 you keep your local sources). The distribution tape con-
142 tains the hierarchy for the mh.6-8/ directory. Bring the
143 sources on-line:
144
145 # cd /usr/src/local
146 % tar xv
147 % cd mh-6.8
148
149CONFIGURATION
150 First, go to the conf/ directory.
151
152 % cd conf/
153
154 This directory contains files that will produce source files
155 tailored for your choice of _\bM_\bH configuration. You should
156 edit only the file MH. This file contains configuration
157 directives. These configuration directives are read by the
158 _\bm_\bh_\bc_\bo_\bn_\bf_\bi_\bg program to produce customized files.
159
160 For examples of various configurations, look in the direc-
161 tory conf/examples/. The file MH provided in conf/ is a
162 reasonable default. Lines beginning with `#' are comments,
163 and are not otherwise interpreted.
164
165 Here are the _\bM_\bH configuration directives available. Be sure
166 to read through this list completely before attempting to
167 decide what directives are appropriate for your system.
168
169 More information on some of these options is available in
170 the the _\bA_\bd_\bm_\bi_\bn_\bi_\bs_\bt_\br_\ba_\bt_\bo_\br'_\bs _\bG_\bu_\bi_\bd_\be. If you do not have a printed
171 copy, you should configure your system with the default con-
172 figuration file, MH, then generate and print a copy of the
173 guide (as described below).
174
175 Installation paths
176 bin: /usr/local
177 The directory where user-invoked programs go (see
178 manual section 1).
179
180 etc: /usr/local/lib/mh
181 The directory where pgm-invoked programs go (see manual
182 section 8).
183
184 mail: /usr/spool/mail
185 The directory where the maildrops are stored. If this
186 pathname is absolute (i.e., begins with a / ), then the
187 user's maildrop is a file called $USER in this direc-
188 tory. If the pathname is not absolute, then the user's
189 maildrop is in the user's home directory under the
190 given name.
191
192
193
194
195[mh.6] Last change: MH.6.8.3 3
196
197
198
199
200
201
202MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
203
204
205
206 mandir: /usr/man
207 The parent directory of the manual entries.
208
209 manuals: standard
210 Where manual entries should be installed, relative to
211 the directory given with "mandir". Either "local" to
212 install manual entries under manl/, or "new" to install
213 manual entries under mann/, or "old" to install manual
214 entries under mano/, or "standard" to install manual
215 entries under man?/, or "bsd44" to install manual
216 entries as man?/_\bp_\ba_\bg_\be.0, or "gen" to generate but not
217 install them, or "none" to neither generate nor install
218 them.
219
220 Any of these values may have the suffix "/cat" appended
221 to it. In that case, the manual entries will be for-
222 matted with "nroff -man" and they will be installed in
223 the corresponding "cat?" directories.
224
225 For example, to install manual entries under
226 /usr/man/u_man/man?, use "standard" and /usr/man/u_man
227 for "mandir". To install formatted manual entires
228 under /usr/contrib/man/cat?, use "standard/cat" and
229 /usr/contrib/man for "mandir". To install formatted
230 manual entries using the BSD44 convention, use
231 "bsd44/cat".
232
233 chown: /etc/chown
234 The location of the _\bc_\bh_\bo_\bw_\bn(8) on your system. If _\bc_\bh_\bo_\bw_\bn
235 is in your search path, just use the value of "chown".
236 On SYS5 systems, this should probably be "/bin/chown".
237
238 cp: cp
239 The command to copy files when installing, if not "cp".
240 (Some sites use "cp -p".)
241
242 ln: ln
243 The command to link files together in the source tree,
244 if not "ln". If you're using something like lndir to
245 keep your compile tree separate from your source tree,
246 set this to "ln -s" or "cp".
247
248 remove: mv -f
249 How _\bM_\bH should make backup copies of existing files when
250 installing new files. To simply remove the old files,
251 use "rm -f".
252
253 Compiler/loader
254 cc: cc
255 The name of your C compiler, if not "cc".
256
257 ccoptions: -O
258
259
260
261[mh.6] Last change: MH.6.8.3 4
262
263
264
265
266
267
268MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
269
270
271
272 Options given directly to _\bc_\bc(1). The most common is
273 "-M" if you're running _\bM_\bH on an ALTOS. This defaults
274 to "-O". If you define this and want to keep "-O", be
275 sure to include it explicitly. If you're using the _\bG_\bN_\bU
276 C compiler, it should include `-traditional'. See
277 "options:" for `-D' options.
278
279 curses: -lcurses -ltermlib
280 This should be the loader option required to load the
281 _\bt_\be_\br_\bm_\bc_\ba_\bp(3) and _\bc_\bu_\br_\bs_\be_\bs(3) libraries on your system. On
282 SYS5 systems, it probably should be just "-lcurses".
283 Some sites have reported that both "-lcurses" and
284 "-ltermlib" are necessary.
285
286 ldoptions: -s
287 Options given directly to _\bl_\bd(1) (via _\bc_\bc) at the begin-
288 ning of the command line. Useful for machines which
289 require arguments to tell _\bl_\bd to increase the stack
290 space (e.g. the Gould, which uses "-m 8"). Usually,
291 "-s" is a good choice in any event.
292
293 ldoptlibs:
294 Options given directly to _\bl_\bd(1) (via _\bc_\bc) at the end of
295 the command line. The two most common are: "-ldbm" if
296 you're running MMDF with the _\bd_\bb_\bm package; and, "-lndir"
297 if you are generating _\bM_\bH on a system which does not
298 load the new directory access mechanism by default
299 (e.g., 4.1BSD, SYS5). If you don't have _\bl_\bi_\bb_\bn_\bd_\bi_\br on
300 your system, the sources are in miscellany/libndir/.
301
302 lex: lex -nt
303 Alternative version of _\bl_\be_\bx. Used in zotnet/tws/.
304
305 oldload: off
306 This controls how _\bM_\bH will try to process library object
307 files to eliminate local symbols. Support for the
308 ALTOS loader if "on". Support for loaders not handling
309 `-x -r' correctly if "none".
310
311 ranlib: on
312 Support for systems with _\br_\ba_\bn_\bl_\bi_\bb(1). For SYSTEM 5 sys-
313 tems, this should be "off" which tells _\bM_\bH to use _\bl_\bo_\br_\bd_\be_\br
314 and _\bt_\bs_\bo_\br_\bt instead. Some SYSTEM 5 sites reported that
315 running this isn't always sufficient. If this is the
316 case, then you should edit conf/makefiles/uip to
317 include ../sbr/libmh.a and ../zotnet/libzot.a twice in
318 the LIBES variable.
319
320 Message Transport System
321 mts: sendmail
322 Which message transport system to use. Either "mmdf"
323 to use _\bM_\bM_\bD_\bF as the transport system, "mmdf2" to use
324
325
326
327[mh.6] Last change: MH.6.8.3 5
328
329
330
331
332
333
334MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
335
336
337
338 _\bM_\bM_\bD_\bF-_\bI_\bI as the transport system, "sendmail" to have
339 _\bS_\be_\bn_\bd_\bM_\ba_\bi_\bl as the transport system, "zmailer" to have
340 _\bZ_\bM_\bA_\bI_\bL_\bE_\bR as the transport system, or, "mh" to have _\bM_\bH as
341 the transport system.
342
343 On UNIX systems supporting TCP/IP networking via sock-
344 ets you can add the suffix "/smtp" to the mts setting.
345 This often yields a superior interface as _\bM_\bH will post
346 mail with the local _\bS_\bM_\bT_\bP server instead of interacting
347 directly with _\bM_\bM_\bD_\bF or _\bS_\be_\bn_\bd_\bM_\ba_\bi_\bl. Hence, for TCP/IP UNIX
348 systems, the "/smtp" suffix to either "sendmail" or
349 "mmdf2" is the preferred MTS configuration. The
350 "/smtp" suffix is described in detail in the
351 _\bA_\bd_\bm_\bi_\bn_\bi_\bs_\bt_\br_\ba_\bt_\bo_\br'_\bs _\bG_\bu_\bi_\bd_\be; be sure to set "servers:" as
352 described in _\bm_\bh-_\bt_\ba_\bi_\bl_\bo_\br(8) if you use this option.
353
354 mf: off
355 Support for mail filtering on those systems in which
356 the message transport system isn't integrated with _\bU_\bU_\bC_\bP
357 This option is strictly for an _\bM_\bH system using either
358 _\bM_\bM_\bD_\bF-_\bI as its transport system or one using
359 "stand-alone delivery".
360
361 UCI BBoards Facility
362 bboards: off
363 If "on", include support for the UCI BBoards facility.
364 BBoards may be enabled with any mts setting. If "off",
365 the BBoard reading program _\bb_\bb_\bc will not be installed.
366 If "nntp", include support for the UCI BBoards facility
367 to read the Network News via the NNTP. If "pop" (form-
368 erly "popbboards: on"), include support for the UCI
369 BBoards facility via the POP3 service; this setting
370 requires "pop: on".
371
372 bbdelivery: off
373 If "off", the BBoards delivery agent and library files
374 will not be installed. If "on", and you set "bboards:"
375 to something besides "off", then the BBoards delivery
376 agent and library files will be installed in the _\bb_\bb_\bh_\bo_\bm_\be
377 directory (see below). To read remote BBoards, the
378 usual configuration would have _\bb_\bb_\bc talk to a _\bP_\bO_\bP_\b3 or
379 _\bN_\bN_\bT_\bP server. However, it may be useful to set this to
380 "off" if you NFS mount the _\bb_\bb_\bh_\bo_\bm_\be directory from
381 another host and want to use _\bb_\bb_\bc to read those files
382 directly.
383
384 bbhome: /usr/spool/bboards
385 The home directory for the BBoards user.
386
387
388
389
390
391
392
393[mh.6] Last change: MH.6.8.3 6
394
395
396
397
398
399
400MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
401
402
403
404 Post Office Protocol
405 pop: off
406 Support for POP service. This allows local delivery
407 for non-local users (a major win). See
408 support/pop/pop.rfc for more information on the POP.
409 This option currently works only on UNIX systems with
410 TCP/IP sockets. (It doesn't hurt to enable this option
411 regardless of whether or not you intend to use POP.)
412 See also "bboards: pop" to enable reading bboards with
413 the POP.
414
415 popdir: /usr/etc
416 The directory where the POP daemon (popd) will be
417 installed.
418
419 options:
420 `-D' options to _\bc_\bc(1).
421
422 APOP='"/etc/pop.auth"'
423 This option indicates that the POP daemon will sup-
424 port the non-standard APOP command, and specifies the
425 name of APOP authorization database. The APOP com-
426 mand provides a challenge-based authentication system
427 using the MD5 message digest algorithm. This facil-
428 ity is documented in _\bT_\bh_\be _\bI_\bn_\bt_\be_\br_\bn_\be_\bt _\bM_\be_\bs_\bs_\ba_\bg_\be (ISBN
429 0-13-092941-7), a book by Marshall T. Rose.
430
431 This option also causes the popauth program to be
432 installed, which allows the administrator to manipu-
433 late the APOP authorization database. For more
434 details, see support/pop/pop-more.txt and the
435 _\bA_\bd_\bm_\bi_\bn_\bi_\bs_\bt_\br_\ba_\bt_\bo_\br'_\bs _\bG_\bu_\bi_\bd_\be.
436
437 DPOP
438 This option indicates that POP subscribers do not
439 have entries in the _\bp_\ba_\bs_\bs_\bw_\bd(5) file, and instead have
440 their own separate database (a win).
441
442 KPOP
443 Support for KERBEROS with POP. This code builds
444 _\bp_\bo_\bp_\bd, _\bi_\bn_\bc and _\bm_\bs_\bg_\bc_\bh_\bk to support only the "kpop" pro-
445 tocol. This code is still experimental, but is
446 available for those sites wishing to test it.
447
448 MPOP
449 This option indicates that the POP daemon will sup-
450 port the non-standard XTND SCAN command which pro-
451 vides performance enhancements when using the POP
452 over low-speed connections. This option also causes
453 an interactive POP client program, popi, to be com-
454 piled and installed. A man page for the popi program
455 is also provided.
456
457
458
459[mh.6] Last change: MH.6.8.3 7
460
461
462
463
464
465
466MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
467
468
469
470 These extensions are described in _\bT_\bh_\be _\bI_\bn_\bt_\be_\br_\bn_\be_\bt _\bM_\be_\bs_\b-
471 _\bs_\ba_\bg_\be, a book by Marshall T. Rose. For more details,
472 see support/pop/pop-more.txt. Note: this option
473 requires "bboards: pop".
474
475 POP2
476 Have the POP daemon understand the older POP2 proto-
477 col as well as the _\bM_\bH POP3 protocol - a major win.
478 The POP daemon auto-magically determines which POP
479 protocol your client is using. If you're enabling
480 POP service, there's no reason not to enable this
481 option as well. See also _\bP_\bO_\bP_\bS_\bE_\bR_\bV_\bI_\bC_\bE.
482
483 POPSERVICE
484 The port name the _\bM_\bH POP will use. For historical
485 reasons, this defaults to "pop".
486
487 In 1987, the _\bM_\bH POP protocol (POP version 3) was pub-
488 lished as RFC1081 and was assigned its own port
489 number (110), which differs from the original POP
490 (version 1 and 2) port number (109).
491
492 To have _\bM_\bH POP use the new assigned port number, set
493 POPSERVICE='"pop3"', and be sure that this service
494 name is listed in your /etc/services file on both POP
495 client and server hosts as "110/tcp". If you enable
496 _\bP_\bO_\bP_\b2, you can safely leave _\bP_\bO_\bP_\bS_\bE_\bR_\bV_\bI_\bC_\bE undefined
497 unless you are using POP3 clients besides _\bM_\bH.
498
499 RPOP
500 This option indicates that support for the UNIX vari-
501 ant of POP, RPOP, which uses privileged sockets for
502 authentication be enabled. This peacefully co-exists
503 with the standard POP.
504
505 SHADOW
506 Indicates that the popd POP server can find encrypted
507 passwords in the /etc/shadow file (and not in the
508 /etc/passwd file). It should be used only for some
509 (newer) SYSTEM 5 systems.
510
511 The "APOP" and "MPOP" non-standard POP facilities are
512 documented in _\bT_\bh_\be _\bI_\bn_\bt_\be_\br_\bn_\be_\bt _\bM_\be_\bs_\bs_\ba_\bg_\be (ISBN 0-13-092941-7),
513 a book by Marshall T. Rose. For more details, see
514 support/pop/pop-more.txt. The "APOP" option peacefully
515 co-exists with the standard POP. The "MPOP" option
516 requires "bboards: pop".
517
518 Shared libraries
519 sharedlib: off
520 If "sun4", makes libmh.a into a SunOS 4.0 (and later)
521 shared library. If you enable this, be sure to also use
522
523
524
525[mh.6] Last change: MH.6.8.3 8
526
527
528
529
530
531
532MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
533
534
535
536 "options SUN40". If "sys5", makes libmh.a into a SYS5
537 R4 (and later) shared library. If you enable this, be
538 sure to also use "options SVR4".
539
540 slflags: -pic
541 The compiler flags to produce position independent code.
542
543 slibdir: /usr/local/lib
544 The directory where the _\bM_\bH shared library should go.
545
546 Under SunOS (sun4)
547 Since some _\bM_\bH programs are setuid, they'll only look for
548 the library in "trusted" locations. Putting the library
549 somewhere besides /usr/lib or /usr/local/lib is not
550 advisable.
551
552 If you must do this, be sure that you add the path given
553 by slibdir to the compiler's library search list (e.g.,
554 "ldoptions: -L/usr/mh/lib") and make sure the path
555 starts with a leading `/'.
556
557 You may need to run _\bl_\bd_\bc_\bo_\bn_\bf_\bi_\bg(8) manually whenever a new
558 shared object is installed on the system. See _\bl_\bd(1) for
559 more information about using shared libraries.
560
561 Under Solaris 2.0 (and newer)
562 The above instructions for SunOS apply, except you
563 should set the run-time library search path using `-R'
564 instead of `-L' (e.g., "ldoptions: -R/usr/mh/lib").
565
566 General System Dependencies
567 You should include the following directives which are
568 appropriate for your version of UNIX. If you don't know what
569 an option does, it probably doesn't apply to you.
570
571 mailgroup: off
572 If set, _\bi_\bn_\bc is made set-group-id to this group name.
573 Some SYS5 systems want this to be set to "mail". Set
574 this if your /usr/spool/mail is not world-writeable.
575
576 Note that slocal doesn't know how to deal with this, and
577 will not work under these systems; just making it set-
578 group-id will open a security hole. If you're using
579 "mailgroup", you should remove slocal (and its man page)
580 from your system.
581
582 signal: int
583 The base type (int or void) of the function
584 parameter/return value of _\bs_\bi_\bg_\bn_\ba_\bl(2). The default is
585 int. Set "signal void" on systems which use this type
586 (e.g., SYSTEM 5 V3.0 and later or Sun OS 4.0 and later).
587
588
589
590
591[mh.6] Last change: MH.6.8.3 9
592
593
594
595
596
597
598MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
599
600
601
602 sprintf: char *
603 The return value of the _\bs_\bp_\br_\bi_\bn_\bt_\bf library routine. This
604 defaults to "char *". Set this to "int" if you have an
605 older version of SYSTEM 5 which has this routine return
606 an "int" type.
607
608 options:
609 `-D' options to _\bc_\bc(1).
610
611 ALTOS
612 Use on XENIX/v7 systems. Also, be sure to use
613 "options V7".
614
615 ATTVIBUG
616 This option causes _\bM_\bH to return to the "What now?"
617 prompt if your initial editor is vi and it exits with
618 non-zero status. Use on Sun OS 4.1 and other systems
619 where the /usr/ucb/vi editor was changed to exit with
620 its status equal to the number of pseudo-"errors"
621 encountered during the edit. This causes a problem
622 for programs that test the exit status of their editor
623 and abort if the status is non-zero. (This includes
624 _\bM_\bH and programs like /usr/etc/vipw).
625
626 AUX
627 Use with AUX systems.
628
629 BIND
630 If you are running with the BIND code on UNIX systems
631 with TCP/IP sockets (e.g. 4.{2,3}BSD), be sure to
632 define this.
633
634 BSD41A
635 Use on 4.1a Berkeley UNIX systems.
636
637 BSD42
638 Use on Berkeley UNIX systems on or after 4.2BSD.
639
640 BSD43
641 Use on 4.3 Berkeley UNIX systems. Also, be sure to
642 use "options BSD42". If _\bo_\bp_\be_\bn_\bl_\bo_\bg(3) (see "man 3 sys-
643 log") takes three arguments instead of two, and your
644 _\bw_\br_\bi_\bt_\be(1) command is set-group-id to group "tty", use
645 this option. If only one of these conditions is true,
646 you lose.
647
648 BSD44
649 Use on Berkeley UNIX systems on or after 4.4BSD.
650 Also, be sure to use "options BSD43" and "options
651 BSD42".
652
653 DBMPWD
654
655
656
657[mh.6] Last change: MH.6.8.3 10
658
659
660
661
662
663
664MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
665
666
667
668 Use this option if your _\bg_\be_\bt_\bp_\bw_\be_\bn_\bt(3) routines read a
669 dbm database (such as with Yellow Pages) instead of
670 doing a sequential read of /etc/passwd. Without
671 DBMPWD the entire passwd file is read into memory one
672 entry at a time for alias expansion. This is a per-
673 formance improvement when reading a standard
674 /etc/passwd file, but is _\bv_\be_\br_\by slow on systems with a
675 dbm database. At one site that runs YP on a large
676 passwd file, it showed a 6:1 performance improvement.
677
678 GCOS_HACK
679 The so-called "gcos" field of the password file is
680 used as a last resort to find the user's full name
681 (see _\bm_\bh-_\bp_\br_\bo_\bf_\bi_\bl_\be(5) for details). Enable this option
682 if your _\bp_\ba_\bs_\bs_\bw_\bd(5) man page notes that the `&' charac-
683 ter in the "gcos" field stands for the login name.
684
685 FCNTL
686 Directs _\bM_\bH to use the fcntl() system call for kernel-
687 level locking. If you're using a SYS5 system, you may
688 want this option. (See also `FLOCK' and `LOCKF').
689
690 FLOCK
691 Directs _\bM_\bH to use the flock() system call for kernel-
692 level locking. If you're on a BSD42 system, and
693 you're not using NFS to read or write maildrops, you
694 should enable this option. (See also `FCNTL' and
695 `LOCKF').
696
697 HESIOD
698 Support for HESIOD. This code was contributed, and
699 included no documentation.
700
701 LOCKF
702 Directs _\bM_\bH to use the lockf() system call for kernel-
703 level locking. If you're using NFS to read or write
704 maildrops, you should enable this option. (See also
705 `FLOCK' and `FCNTL').
706
707 locname
708 Hard-wires the local name for the host _\bM_\bH is running
709 on. For example, locname='"PICKLE"'. It's probably
710 better to either let UNIX tell _\bM_\bH this information, or
711 to put the information in the host specific mtstailor
712 file.
713
714 MORE
715 Defines the location of the _\bm_\bo_\br_\be(1) program. On
716 ALTOS and DUAL systems, set MORE='"/usr/bin/more"'.
717 The default is "/usr/ucb/more".
718
719 NDIR
720
721
722
723[mh.6] Last change: MH.6.8.3 11
724
725
726
727
728
729
730MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
731
732
733
734 For non-Berkeley UNIX systems, this _\bM_\bH will try to
735 find the new directory access mechanism by looking in
736 <ndir.h> if this option is given. Otherwise, _\bM_\bH will
737 try <dir.h>. If you still can't get this to work on
738 your system, edit h/local.h as appropriate. (See also
739 `SYS5DIR'.)
740
741 NFS
742 Tells _\bM_\bH to hack around a problem in the NFS C
743 library. If you get an undefined symbol "ruserpass"
744 when compiling _\bM_\bH, you probably need this option. If,
745 however, you include this option and get an undefined
746 symbol "__ruserpass" when compiling, then you should
747 omit this option. (See also `NORUSERPASS'.)
748
749 NOIOCTLH
750 Tells _\bM_\bH not to include the file <sys/ioctl.h>. To be
751 used on systems where this file is not present.
752
753 NORUSERPASS
754 Tells _\bM_\bH that your system doesn't have the _\br_\bu_\bs_\be_\br_\b-
755 _\bp_\ba_\bs_\bs(3) routine; _\bM_\bH will include its own copy of this
756 routine in its library. (See also `NFS'.)
757
758 NTOHLSWAP
759 Tells _\bM_\bH to use the ntohl() macro when processing _\bm_\bs_\bh
760 binary map files. _\bM_\bH can use this macro on systems
761 with the include file netinet/in.h, to byte-swap the
762 binary information in these map files. If you're
763 using the same map files on machines of different
764 architectures, enable this option.
765
766 RENAME
767 Include this option if your system has a rename()
768 library call. This is true on BSD42 and newer and
769 some SYS5 systems.
770
771 SENDMAILBUG
772 Causes SMTP reply code 451 (failure) to be considered
773 the same as code 250 (OK). Since this might cause
774 problems, only enable this if you are certain that
775 your SendMail will return this code even when it
776 doesn't mean to indicate a failure.
777
778 SOCKETS
779 Indicates the availability of a socket interface for
780 TCP/IP networking that is compatible with 4.{2,3}BSD
781 UNIX. It is not necessary to define this when BSD42
782 is already defined, but it might be useful for SYSTEM
783 5 or HPUX systems with TCP/IP sockets.
784
785 SUN40
786
787
788
789[mh.6] Last change: MH.6.8.3 12
790
791
792
793
794
795
796MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
797
798
799
800 Use on Sun OS 4.0 (and later?) systems. You also will
801 need "options BSD42", "options BSD43", and "signal
802 void".
803
804 If you're using Sun's brain-damaged approach to offer-
805 ing Domain Name Service through NIS, be sure to
806 include "options BIND" and "ldoptions -lresolv" to
807 work around some NIS/DNS bugs.
808
809 SYS5
810 Use on AT&T SYSTEM 5 R3 (and newer?) UNIX systems.
811 See also _\bm_\ba_\bi_\bl_\bg_\br_\bo_\bu_\bp.
812
813 SYS5DIR
814 Define this if your system uses "struct dirent"
815 instead of "struct direct". This is true of System V
816 Release 3.0 and later. Uses include file <dirent.h>
817 and the routines _\bm_\bk_\bd_\bi_\br, _\br_\bm_\bd_\bi_\br and _\bg_\be_\bt_\bc_\bw_\bd.
818
819 SVR4
820 Use on AT&T SYSTEM 5 R4 (and newer?) UNIX systems. You
821 should also include "options SYS5" and "options
822 SYS5DIR". See also _\bm_\ba_\bi_\bl_\bg_\br_\bo_\bu_\bp. You will also need to
823 include "oldload none" if your ld doesn't handle
824 `-x -r' correctly.
825
826 TERMINFO
827 Define TERMINFO if you have it. You get it automati-
828 cally if you're running SYS5, and you don't get it if
829 you're not. (If you're not SYS5, you probably have
830 termcap.)
831
832 TZNAME
833 Use time zone names from the _\bt_\bz_\bn_\ba_\bm_\be variable, set via
834 _\bt_\bz_\bs_\be_\bt. Only applicable on SYSTEM 5 systems and only
835 effective when you have asked for alpha-timezones (see
836 the ATZ option). See also ZONEINFO.
837
838 UNISTD
839 Include this option if your system has the file
840 <unistd.h>. If not specified, the LOCKF option will
841 include <sys/fcntl.h>.
842
843 V7
844 Use on V7 UNIX systems. Also, be sure to use "options
845 void=int".
846
847 VSPRINTF
848 Include this option if your system has the _\bv_\bs_\bp_\br_\bi_\bn_\bt_\bf(3)
849 library routine; otherwise, __\bd_\bo_\bp_\br_\bn_\bt(3) will be used.
850
851 WAITINT
852
853
854
855[mh.6] Last change: MH.6.8.3 13
856
857
858
859
860
861
862MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
863
864
865
866 BSD42 based systems call the _\bw_\ba_\bi_\bt(2) system routine
867 with a pointer to type _\bu_\bn_\bi_\bo_\bn _\bw_\ba_\bi_\bt. Include this
868 option if you included "options BSD42", but your sys-
869 tem calls the _\bw_\ba_\bi_\bt(2) system routine with a pointer to
870 type _\bi_\bn_\bt (the non-BSD42 default).
871
872 ZONEINFO
873 Specify this if you have a BSD43 based system that
874 keeps time zone information /etc/zoneinfo or
875 /usr/lib/zoneinfo (SunOS), and where the _\bs_\bt_\br_\bu_\bc_\bt _\bt_\bm
876 returned by _\bl_\bo_\bc_\ba_\bl_\bt_\bi_\bm_\be(3) contains a _\bt_\bm__\bg_\bm_\bt_\bo_\bf_\bf element
877 (see /usr/include/time.h). With this fix the GMT
878 offset specified in outgoing mail will be corrected
879 when the TZ enviornment variable is set to a different
880 time zone. See also TZNAME.
881
882Site Preferences
883 These options change the default behavior of _\bM_\bH or enable
884 optional features. Add the options which are appropriate for
885 your configuration or your site preferences.
886
887 editor: prompter
888 The default editor for _\bM_\bH.
889
890 options:
891 `-D' options to _\bc_\bc(1).
892
893 ATZ
894 Directs _\bM_\bH to use alpha-timezones whenever possible.
895 You should not use this option if you are on the Inter-
896 net, since it will make your host non-compliant with
897 RFC-1123 (Requirements for Internet Hosts).
898
899 ATHENA
900 Makes _\br_\be_\bp_\bl `-nocc all' the default instead of
901 `-cc all'. You may want to enable this if you're using
902 _\bx_\bm_\bh.
903
904 BANG
905 Directs _\bM_\bH to favor `!' over `@' in addressing.
906
907 BERK
908 Optional for for 4.{2,3}BSD sites running SendMail.
909 Disables nearly all of the RFC822 address and header-
910 parsing routines in favor of recognizing such formats
911 as ASCnet, and so on. If you don't need to disable the
912 parser for this reason, you probably want to use
913 "options DUMB" instead.
914
915 COMPAT
916 If you previously ran a version of _\bM_\bH earlier than mh.4
917 use this option. After a short grace period, remove it
918
919
920
921[mh.6] Last change: MH.6.8.3 14
922
923
924
925
926
927
928MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
929
930
931
932 and re-{configure,generate,install} everything.
933
934 DUMB
935 Directs _\bM_\bH not to try and rewrite addresses to their
936 "official" form.
937
938 FOLDPROT
939 Defines the octal value for default folder-protection.
940 For example, FOLDPROT='"0700"'. The default is "0711".
941
942 ISI
943 When using "repl -ccme", only "cc:" the first address
944 found which belongs to the user; any other _\bA_\bl_\bt_\be_\br_\bn_\ba_\bt_\be-
945 _\bM_\ba_\bi_\bl_\bb_\bo_\bx_\be_\bs do not receive "cc:"s.
946
947 LINK
948 Defines the filename for alternate file name for _\bd_\bi_\bs_\bt
949 and _\br_\be_\bp_\bl. For example, LINK='"\\043"' to use the
950 pound-sign character. The default is "@".
951
952 MHE
953 Enables crude support for Brien Reid's MHE interface.
954 Recommended for use with the GNU Emacs mh-e package.
955
956 MHRC
957 Enables _\bM_\bH to recognize the _\bC_\bS_\bh_\be_\bl_\bl's `~'-construct.
958 This is useful for sites that run with a ~/.mhrc for
959 their users.
960
961 MIME
962 Enables support for multi-media messages, as specified
963 in RFC 1341 -- a major win. This allows you to include
964 things like audio, graphics, and the like, in your mail
965 messages. Several _\bM_\bH commands are extended to support
966 these multi-media messages, and the _\bm_\bh_\bn command is pro-
967 vided to encode and decode MIME messages. For more
968 details, see miscellany/multi-media/READ-ME and _\bm_\bh_\bn(1).
969
970 MSGID
971 Enables slocal to detect and surpress duplicate mes-
972 sages received. This code uses the <ndbm.h> library,
973 and requires "options BSD42" since it uses the _\bf_\bl_\bo_\bc_\bk(2)
974 system call for locking. (Note that this means its
975 database locking does not work over NFS.) It has only
976 been tested under SUN40.
977
978 MSGPROT
979 Defines the octal value for default folder-protection.
980 For example, MSGPROT='"0600"'. The default is "0644".
981
982 NOMHSEQ
983 Directs _\bM_\bH to make private sequences the default.
984
985
986
987[mh.6] Last change: MH.6.8.3 15
988
989
990
991
992
993
994MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
995
996
997
998 OVERHEAD
999 Enable _\bM_\bH commands to read profile/context from open
1000 fd:s without doing an open(); see _\bm_\bh-_\bp_\br_\bo_\bf_\bi_\bl_\be(5) for the
1001 details.
1002
1003 RPATHS
1004 Directs _\bi_\bn_\bc to note UNIX "From " lines as Return-Path:
1005 info.
1006
1007 SBACKUP
1008 Defines the prefix string for backup file names. For
1009 example, SBACKUP='"\\043"'. The default is ",".
1010
1011 TMA
1012 Support for the TTI _\bt_\br_\bu_\bs_\bt_\be_\bd _\bm_\ba_\bi_\bl _\ba_\bg_\be_\bn_\bt (TMA). Although
1013 the TTI TMA is not in the public domain, the _\bM_\bH support
1014 for the TTI TMA is in the public domain. You should
1015 enable this option only if you are licensed to run the
1016 TMA software (otherwise, you don't have the software in
1017 your _\bM_\bH source tree).
1018
1019 TTYD
1020 Support for TTYD. This is no longer in wide use, and
1021 is not recommended.
1022
1023 UCI
1024 First, "_" and "#" are recognized as the prefixes for
1025 scratch files. Second, support for the UCI
1026 group-leadership mechanism is enabled in _\bc_\bo_\bn_\bf_\bl_\bi_\bc_\bt.
1027 Third, the first line of the file file $HOME/.signature
1028 is used as the _\bF_\bu_\bl_\bl _\bN_\ba_\bm_\be part of your "From:" header.
1029 This may conflict with the interpretation of this file
1030 by _\bN_\be_\bw_\bs. If you're not at UCI, you probably don't want
1031 this option.
1032
1033 UK
1034 Directs the _\bs_\bc_\ba_\bn program to generate UK-style dates by
1035 default.
1036
1037 WHATNOW
1038 Enable certain _\bM_\bH commands to act differently when
1039 $mhdraft set.
1040
1041 YEARMOD
1042 This option makes the _\bm_\bh-_\bf_\bo_\br_\bm_\ba_\bt %(year) function always
1043 return a value less than 100. Enable this option if
1044 you have local _\bm_\bh-_\bf_\bo_\br_\bm_\ba_\bt(5) files which cannot handle
1045 4-digit years. You should convert these files to use a
1046 4-character field width, or use the %(modulo 100) func-
1047 tion to obtain a 2-digit year value. After a short
1048 grace period, remove `YEARMOD' and re-
1049 {configure,generate,install} everything.
1050
1051
1052
1053[mh.6] Last change: MH.6.8.3 16
1054
1055
1056
1057
1058
1059
1060MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
1061
1062
1063
1064Testing/debugging
1065 debug: off
1066 Support for debug mode of _\bM_\bH. Don't use this unless you
1067 know what you're doing, which isn't likely if you're read-
1068 ing this document!
1069
1070 regtest: off
1071 Set this to "on" if you are doing regression testing among
1072 different compilations of _\bM_\bH, and you do not want the
1073 hostname and compile date included in _\bM_\bH binaries.
1074
1075
1076
1077 Now edit conf/config/mtstailor, depending on your choice of
1078 the setting for mts in the _\bM_\bH configuration file. for an
1079 mts setting of "mh", look at the file conf/tailor/mhmts; for
1080 an mts setting of "sendmail", "sendmail/smtp", "mmdf/smtp",
1081 or "mmdf2/smtp", look at the file conf/tailor/sendmts; and,
1082 for an mts setting of "mmdf", or "mmdf2", look at the file
1083 conf/tailor/mmdf.
1084
1085 Now install the configured files into the source areas. (On
1086 SYS5 systems, or other systems where you get complaints
1087 about "_index" and "_rindex" being undefined, you should use
1088 "make sys5" to compile mhconfig.)
1089
1090 % make
1091 % ./mhconfig MH
1092
1093 Before proceeding, you should familiarize yourself with the
1094 _\bA_\bd_\bm_\bi_\bn_\bi_\bs_\bt_\br_\ba_\bt_\bo_\br'_\bs _\bG_\bu_\bi_\bd_\be. To generate an _\bn_\br_\bo_\bf_\bf version, go to
1095 the doc/ directory and type:
1096
1097 % (cd ../doc/; make ADMIN.doc)
1098
1099
1100 If you're already running _\bM_\bH at your site, you should also
1101 read the _\bm_\bh changes document CHANGES. The source is in
1102 papers/changes/.
1103
1104 After reading the _\bA_\bd_\bm_\bi_\bn_\bi_\bs_\bt_\br_\ba_\bt_\bo_\br'_\bs _\bG_\bu_\bi_\bd_\be, you may decide to
1105 change your MH configuration. If so, cd back to the conf/
1106 directory, re-edit the files MH and conf/config/mtstailor,
1107 and re-run _\bm_\bh_\bc_\bo_\bn_\bf_\bi_\bg.
1108
1109 You now proceed based on your choice of a transport system
1110 (the setting for mts above). The best interface is achieved
1111 with "sendmail" followed by "mmdf" or ("mmdf2"), and then
1112 "mh" (stand-alone delivery, not recommended).
1113
1114 SENDMAIL
1115 If you have not enabled BBoards or POP then no further
1116
1117
1118
1119[mh.6] Last change: MH.6.8.3 17
1120
1121
1122
1123
1124
1125
1126MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
1127
1128
1129
1130 MTS-specific action is required on your part!
1131
1132 If you have enabled POP, but you want to let _\bS_\be_\bn_\bd_\bM_\ba_\bi_\bl
1133 deliver mail POP mail using its standard delivery program
1134 /bin/mail, then, again, no further MTS-specific action is
1135 required on your part!
1136
1137 Otherwise, go to the mts/sendmail/ directory.
1138
1139 % cd ../mts/sendmail/
1140
1141 This directory contains files whose definitions correspond
1142 to the configuration of your _\bS_\be_\bn_\bd_\bM_\ba_\bi_\bl system. If you have
1143 enabled BBoards or POP service, then you will need to
1144 re-configure _\bS_\be_\bn_\bd_\bM_\ba_\bi_\bl. First, in the "local info" section
1145 of your site's _\bS_\be_\bn_\bd_\bM_\ba_\bi_\bl configuration file, choose a free
1146 macro/class (B is used in this distribution), and add these
1147 lines:
1148
1149 # BBoards support
1150 DBbboards
1151 CBbboards
1152
1153 Second, immediately after the inclusion of the zerobase
1154 file, in the "machine dependent part of ruleset zero" sec-
1155 tion, add these lines:
1156
1157 # resolve names for the BBoards system
1158 R$+<@$=B> $#bboards$@$2$:$1 topic@bboards
1159
1160 Be sure to use tabs when separating these fields. Third,
1161 add the line
1162
1163 include(bboardsMH.m4)
1164
1165 after the line
1166
1167 include(localm.m4)
1168
1169 in your site's _\bS_\be_\bn_\bd_\bM_\ba_\bi_\bl configuration file. Finally, you
1170 should link the file mts/sendmail/bboardsMH.m4 into your
1171 _\bS_\be_\bn_\bd_\bM_\ba_\bi_\bl cf/ directory and re-configure _\bS_\be_\bn_\bd_\bM_\ba_\bi_\bl.
1172
1173 If you have enabled POP service, a similar procedure must be
1174 used on the POP service host, to re-configure _\bS_\be_\bn_\bd_\bM_\ba_\bi_\bl.
1175 First, in the "local info" section of your site's _\bS_\be_\bn_\bd_\bM_\ba_\bi_\bl
1176 configuration file, choose a free macro/class (P is used in
1177 this distribution), and add these lines:
1178
1179 # POP support
1180 DPpop
1181 CPpop
1182
1183
1184
1185[mh.6] Last change: MH.6.8.3 18
1186
1187
1188
1189
1190
1191
1192MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
1193
1194
1195
1196 Second, immediately after the inclusion of the zerobase
1197 file, in the "machine dependent part of ruleset zero" sec-
1198 tion, add these lines:
1199
1200 # resolve names for the POP system
1201 R$+<@$=P> $#pop$@$2$:$1 subscriber@pop
1202
1203 Be sure to use tabs when separating these fields. Third,
1204 add the line
1205
1206 include(popMH.m4)
1207
1208 after the line
1209
1210 include(localm.m4)
1211
1212 in your site's _\bS_\be_\bn_\bd_\bM_\ba_\bi_\bl configuration file. Finally, you
1213 should link the file mts/sendmail/popMH.m4 into your _\bS_\be_\bn_\bd_\b-
1214 _\bM_\ba_\bi_\bl cf/ directory and re-configure _\bS_\be_\bn_\bd_\bM_\ba_\bi_\bl.
1215
1216 MMDF
1217 If you want _\bM_\bM_\bD_\bF to be your transport service, and have NOT
1218 specified "mmdf/smtp" (or "mmdf2/smtp") as your mts setting,
1219 then go to the mmdf/ directory. (If you're using
1220 "mmdf/smtp" or "mmdf2/smtp" as your mts setting, then skip
1221 to the next section.)
1222
1223 % cd ../mts/mmdf/
1224
1225 This directory contains files whose definitions correspond
1226 to the configuration of your _\bM_\bM_\bD_\bF system.
1227
1228 If you're running _\bM_\bM_\bD_\bF-_\bI, then copy the following files from
1229 wherever you keep the _\bM_\bM_\bD_\bF sources to this directory:
1230 mmdf/h/ch.h, mmdf/h/conf.h, utildir/conf_util.h,
1231 utildir/ll_log.h, mmdf/h/mmdf.h, utildir/util.h,
1232 mmdf/mmdf_lib.a, and utildir/util_lib.a.
1233
1234 If you're running _\bM_\bM_\bD_\bF-_\bI_\bI, then copy the following files
1235 from where you keep the _\bM_\bM_\bD_\bF sources to this directory:
1236 h/ch.h, h/conf.h, h/dm.h, h/ll_log.h, h/mmdf.h, h/util.h,
1237 and lib/libmmdf.a
1238
1239 If you have enabled bboards, then the directories
1240 support/bboards/mmdfI and support/bboards/mmdfII contain
1241 information you'll need to put a UCI BBoards channel in your
1242 _\bM_\bM_\bD_\bF configuration. Similarly, if you have enabled option
1243 "mf" and are running _\bM_\bM_\bD_\bF-_\bI, then the zotnet/mf/mmdfI/
1244 directory contains information you'll need to put a _\bU_\bU_\bC_\bP
1245 channel in your _\bM_\bM_\bD_\bF-_\bI configuration. Finally, the direc-
1246 tory support/pop/mmdfII contains information you'll need to
1247 put a POP channel in your _\bM_\bM_\bD_\bF-_\bI_\bI configuration.
1248
1249
1250
1251[mh.6] Last change: MH.6.8.3 19
1252
1253
1254
1255
1256
1257
1258MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
1259
1260
1261
1262 Note that _\bM_\bM_\bD_\bF-_\bI_\bI is distributed with the BBoards channel,
1263 although the version in the _\bM_\bH distribution might be more
1264 current, the version in the _\bM_\bM_\bD_\bF-_\bI_\bI distribution has been
1265 tested with that revision of _\bM_\bM_\bD_\bF.
1266
1267 MMDF/SMTP
1268 If you are using "mmdf/smtp" as your mts setting, then no
1269 further MTS-specific action is required on your part!
1270
1271 MMDF2/SMTP
1272 If you are using "mmdf2/smtp" as your mts setting, then no
1273 further MTS-specific action is required on your part!
1274
1275 STAND-ALONE DELIVERY
1276 If, instead, you want _\bM_\bH to handle its own mail delivery,
1277 then no further MTS-specific action is required on your
1278 part!
1279
1280GENERATION
1281 Go to the _\bM_\bH top-level directory and generate the system.
1282
1283 % cd ../; make
1284
1285 This will cause a complete generation of the _\bM_\bH system. If
1286 all goes well, proceed with installation. If not, complain,
1287 as there "should be no problems" at this step.
1288
1289INSTALLATION
1290 If the directories you chose for the user-programs,
1291 support-programs and manuals ("bin", "etc", "popdir", "slib-
1292 dir", and "mandir" in the conf/MH file) don't exist, you
1293 should create them at this point.
1294
1295 Next, if you enabled support for the UCI BBoards facility,
1296 then create a login called "bboards" with the following
1297 characteristics: home directory is /usr/spool/bboards/ with
1298 mode 755 (actually, use the value for "bbhome" given in the
1299 _\bM_\bH configuration file), login shell is /bin/csh (or
1300 /bin/sh), and, encrypted password field is "*". The
1301 "bboards" login should own the /usr/spool/bboards/ direc-
1302 tory. In addition to creating /usr/spool/bboards/, also
1303 create /usr/spool/bboards/etc/ and
1304 /usr/spool/bboards/archive/. These directories should also
1305 be owned by the "bboards" login.
1306
1307 If you enabled support for POP, then on the POP service
1308 host, create a login called "pop" with the following charac-
1309 teristics: home directory is /usr/spool/pop/ with mode 755,
1310 login shell is /bin/csh, and, encrypted password field is
1311 "*". If you don't have /bin/csh on your system (V7), then
1312 /bin/sh is just fine. The "pop" login should own the
1313 /usr/spool/pop/ directory. You'll also need to add a line
1314
1315
1316
1317[mh.6] Last change: MH.6.8.3 20
1318
1319
1320
1321
1322
1323
1324MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
1325
1326
1327
1328 to the /etc/services file and the /etc/rc.local file, see
1329 the _\bA_\bd_\bm_\bi_\bn_\bi_\bs_\bt_\br_\ba_\bt_\bo_\br'_\bs _\bG_\bu_\bi_\bd_\be for more details.
1330
1331 If this is not the first time you have installed _\bM_\bH, these
1332 files will need particular attention:
1333
1334 _\bD_\bi_\br_\be_\bc_\bt_\bo_\br_\by _\bF_\bi_\bl_\be_\bs
1335 "etc/" MailAliases, BBoardAliases, mtstailor
1336 /usr/spool/bboards/ BBoards, .cshrc, .mh_profile
1337 /usr/spool/bboards/etc/ *
1338
1339 The MailAliases, BBoardAliases, mtstailor and BBoards files
1340 will NOT be installed over existing copies; you will need to
1341 edit these by hand and merge in any changes from your previ-
1342 ous _\bM_\bH release. The other files under /usr/spool/bboards/
1343 will be overwritten if they exist. You may wish to preserve
1344 your old versions of these before installing _\bM_\bH.
1345
1346 As the super-user, and from the mh.6/ directory, install the
1347 system.
1348
1349 # make inst-all
1350
1351 This will cause the _\bM_\bH processes and files to be transferred
1352 to the appropriate areas with the appropriate attributes.
1353
1354TAILORING
1355 See the _\bA_\bd_\bm_\bi_\bn_\bi_\bs_\bt_\br_\ba_\bt_\bo_\br'_\bs _\bG_\bu_\bi_\bd_\be for information on tailoring
1356 _\bM_\bH for the MTS, BBoards, and POP.
1357
1358DOCUMENTATION
1359 In addition to this document, the _\bA_\bd_\bm_\bi_\bn_\bi_\bs_\bt_\br_\ba_\bt_\bo_\br'_\bs _\bG_\bu_\bi_\bd_\be, and
1360 the _\bU_\bs_\be_\br'_\bs _\bM_\ba_\bn_\bu_\ba_\bl, there are several documents referenced by
1361 the user's manual which may be useful. The sources for all
1362 of these can be found under the papers/ directory.
1363
1364OTHER THINGS
1365 Consult the directory miscellany/ for the sources to a
1366 number of things which aren't part of the mainstream _\bM_\bH dis-
1367 tribution, but which are still quite useful.
1368
1369FILES
1370 Too numerous to mention. Really.
1371
1372SEE ALSO
1373 make(1)
1374
1375BUGS
1376 The _\bm_\bh_\bc_\bo_\bn_\bf_\bi_\bg program should be smarter.
1377
1378 There's no way to print the _\bA_\bd_\bm_\bi_\bn_\bi_\bs_\bt_\br_\ba_\bt_\bo_\br'_\bs _\bG_\bu_\bi_\bd_\be until
1379 after you have configured the system; it is difficult to
1380
1381
1382
1383[mh.6] Last change: MH.6.8.3 21
1384
1385
1386
1387
1388
1389
1390MH-GEN(8) MAINTENANCE COMMANDS MH-GEN(8)
1391
1392
1393
1394 configure the system without the _\bA_\bd_\bm_\bi_\bn_\bi_\bs_\bt_\br_\ba_\bt_\bo_\br'_\bs _\bG_\bu_\bi_\bd_\be.
1395
1396 The Makefiles should know when _\bm_\bh_\bc_\bo_\bn_\bf_\bi_\bg has been run and
1397 force "make clean" behavior.
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449[mh.6] Last change: MH.6.8.3 22
1450
1451
1452
Continuous source code history from original PDP-7 UNIX to FreeBSD 2, the first fully unencumbered FreeBSD release.