![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to mh-gen.8 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / contrib / mh / conf|
Return to mh-gen.8 CVS log | Up to [CSRG BSD Unix] / 43BSDReno / contrib / mh / conf |
1.1 root 1: .TH MH-GEN 8 MH [mh.6]
2: .SH NAME
3: mh-gen \- generating the MH system
4: .SH "READ THIS"
5: This documentation describes how to configure, generate, and install
6: the UCI version of the Rand \fIMH\fR system.
7: Although the \fIMH\fR system was originally developed by the Rand Corporation,
8: and is now in the public domain,
9: the Rand Corporation assumes no responsibility for \fIMH\fR
10: or this particular modification of \fIMH\fR.
11: .PP
12: In addition,
13: the Regents of the University of California issue the following
14: \fBdisclaimer\fR in regard to the UCI version of \fIMH\fR:
15: .in +.5i
16: \*(lqAlthough each program has been tested by its contributor,
17: no warranty, express or implied,
18: is made by the contributor or the University of California,
19: as to the accuracy and functioning of the program
20: and related program material,
21: nor shall the fact of distribution constitute any such warranty,
22: and no responsibility is assumed by the contributor
23: or the University of California in connection herewith.\*(rq
24: .in -.5i
25: .PP
26: This version of \fIMH\fR is in the public domain,
27: and as such,
28: there are no real restrictions on its use.
29: The \fIMH\fR source code and documentation have no licensing restrictions
30: whatsoever.
31: As a courtesy,
32: the authors ask only that you provide appropriate credit to the Rand
33: Corporation and
34: the University of California for having developed the software.
35: .PP
36: \fIMH\fR is a software package that is neither supported by the Rand
37: Corporation nor the University of California.
38: However,
39: since we do use the software ourselves and plan to continue using (and
40: improving) \fIMH\fR,
41: bug reports and their associated fixes should be reported back to us so that
42: we may include them in future releases.
43: The current computer mailbox for \fIMH\fR is \fBBug\[email protected]\fR
44: (in the ARPA Internet),
45: and \fB...!ucbvax!ucivax!bug\-mh\fR (UUCP).
46: Presently,
47: there are two Internet discussion groups, MH\[email protected]
48: and MH\[email protected].
49: If there is sufficient interest,
50: corresponding Usenet news groups may be established along with the
51: appropriate gateways.
52: .SH SYNOPSIS
53: MAKE
54: .SH DESCRIPTION
55: This is a description of how one can bring up an \fIMH\fR system.
56: It is assumed that you have super-user privileges in order to
57: (re\-)install \fIMH\fR.
58: Super-user privileges are not required to configure or generate \fIMH\fR.
59: .PP
60: Become the super-user and create a new directory under /usr/src/local/
61: (or whatever) for the \fIMH\fR area.
62: Traditionally, the directory's name should be mh/.
63: The distribution tape contains the hierarchy for the mh.6/ directory.
64: Bring the sources on-line:
65: .sp 1
66: .nf
67: # mkdir /usr/src/local/mh
68: % cd /usr/src/local/mh
69: % tar xv
70: .fi
71: .SH CONFIGURATION
72: First, go to the conf/ directory.
73: .sp 1
74: .nf
75: % cd conf/
76: .fi
77: .sp 1
78: This directory contains files that will produce source files tailored
79: for your choice of \fIMH\fR configuration.
80: You should edit only the file \fBMH\fR.
81: This file contains configuration directives.
82: These configuration directives are read by the \fImhconfig\fR program to
83: produce customized files.
84: For examples of various configurations,
85: look in the directory \fBconf/examples/\fR.
86: The file \fBMH\fR provided in \fBconf/\fR is a reasonable default.
87: .PP
88: Here are the \fIMH\fR configuraton options available:
89: .in +.5i
90: .ti -.5i
91: bin: /usr/local
92: .br
93: The directory where user\-invoked programs go (see manual section 1).
94:
95: .ti -.5i
96: debug: off
97: .br
98: Support for debug mode of \fIMH\fR.
99: Don't use this unless you know what you're doing,
100: which isn't likely if you're reading this document!
101:
102: .ti -.5i
103: etc: /usr/local/lib/mh
104: .br
105: The directory where pgm\-invoked programs go (see manual section 8).
106:
107: .ti -.5i
108: mail: /usr/spool/mail
109: .br
110: The directory where the maildrops are stored.
111: If this pathname is absolute (i.e., begins with a \fB/\fR\0),
112: then the user's maildrop is a file called \fB$USER\fR in this directory.
113: If the pathname is not absolute,
114: then the user's maildrop is in the user's home directory under the given name.
115:
116: .ti -.5i
117: mandir: /usr/man
118: .br
119: The parent directory of the manual entries.
120:
121: .ti -.5i
122: manuals: standard
123: .br
124: Where manual entries should be installed,
125: relative to the directory given with \*(lqmandir\*(rq.
126: Either \*(lqlocal\*(rq to install manual entries under \fBmanl/\fR,
127: or \*(lqnew\*(rq to install manual entries under \fBmann/\fR,
128: or \*(lqold\*(rq to install manual entries under \fBmano/\fR,
129: or \*(lqstandard\*(rq to install manual entries under \fBman?/\fR,
130: or \*(lqgen\*(rq to generate but not install them,
131: or \*(lqnone\*(rq to neither generate nor install them.
132: For example,
133: to install manual entries under \fB/usr/man/u_man/man?\fR,
134: use \*(lqstandard\*(rq and \fB/usr/man/u_man\fR for \*(lqmandir\*(rq.
135:
136: .ti -.5i
137: chown: /etc/chown
138: .br
139: The location of the \fIchown\fR\0(8) on your system.
140: If \fIchown\fR is in your search path,
141: just use the value of \*(lqchown\*(rq.
142: On SYS5 systems,
143: this should probably be \*(lq/bin/chown\*(rq.
144:
145: .ti -.5i
146: editor: prompter
147: .br
148: The default editor for \fIMH\fR.
149:
150: .ti -.5i
151: remove: mv \-f
152: .br
153: How \fIMH\fR shuld backup existing files when installing a new file.
154:
155: .ti -.5i
156: mts: sendmail
157: .br
158: Which message transport system to use.
159: Either \*(lqmmdf\*(rq to use \fIMMDF\fR as the transport system,
160: \*(lqmmdf2\*(rq to use \fIMMDF\-II\fR as the transport system,
161: \*(lqsendmail\*(rq to have \fISendMail\fR as the transport system,
162: or, \*(lqmh\*(rq to have \fIMH\fR as the transport system.
163: On 4.2BSD UNIX systems
164: you can add the suffix \*(lq/smtp\*(rq to the mts setting.
165: This often yields a superior interface as \fIMH\fR will post mail with the
166: local \fISMTP\fR server instead of interacting directly with \fIMMDF\fR or
167: \fISendMail\fR.
168: The \*(lq/smtp\*(rq suffix is described in detail in the \fIAdministrator's
169: Guide\fR.
170: Hence,
171: for 4.2BSD UNIX systems,
172: the \*(lq/smtp\*(rq suffix to either \*(lqsendmail\*(rq or \*(lqmmdf2\*(rq is
173: the preferred MTS configuration.
174:
175: .ti -.5i
176: bboards: off
177: .br
178: Support for the UCI BBoards facility.
179: BBoards may be enabled with any mts setting.
180:
181: .ti -.5i
182: bbhome: /usr/spool/bboards
183: .br
184: The home directory for the BBoards user.
185:
186: .ti -.5i
187: mf: off
188: .br
189: Support for mail filtering on those systems in which the message transport
190: system isn't integrated with \fIUUCP\fR
191: This option is strictly for an \fIMH\fR system using either \fIMMDF\-I\fR
192: as its transport system or one using \*(lqstand\-alone delivery\*(rq.
193:
194: .ti -.5i
195: pop: off
196: .br
197: Support for POP service.
198: This allows local delivery for non\-local users
199: (a major win).
200: See \fBsupport/pop/pop.rfc\fR for more information on the POP.
201: This option currently works only on 4.2BSD UNIX systems.
202: (It doesn't hurt to enable this option regardless of whether or not
203: you intend to use POP.)
204: If POP is enabled, there are two additional options which are of interest:
205: \*(lqRPOP\*(rq and \*(lqDPOP\*(rq.
206: The former indicates that support for the UNIX variant of POP,
207: RPOP, which uses privileged sockets for authentication be enabled.
208: This peacefully co\-exists with the standard POP.
209: The \*(lqDPOP\*(rq option indicates that POP subscribers do not have
210: entries in the \fIpasswd\fR\0(5) file,
211: and instead have their own separate database (another major win).
212: Both of these options can be enabled via an \*(lqoptions\*(rq directive in the
213: \fIMH\fR configuration file.
214:
215: .ti -.5i
216: popbboards: off
217: .br
218: Support for the UCI BBoards facility via the POP service.
219: Requires both bboards and pop to be enabled.
220:
221: .ti -.5i
222: options:
223: .br
224: \&`\-D' options to \fIcc\fR\0(1).
225:
226: .in +.5i
227: .ti -.5i
228: ALTOS
229: .br
230: Use on XENIX/v7 systems.
231: Also, be sure to use \*(lqoptions V7\*(rq.
232:
233: .ti -.5i
234: ATHENA
235: .br
236: \fIrepl\fR will assume `\-nocc\ all' as the default instead of `\-cc\ all'.
237:
238: .ti -.5i
239: ATZ
240: .br
241: Directs \fIMH\fR to use alpha\-timezones whenever possible.
242:
243: .ti -.5i
244: BANG
245: .br
246: Directs \fIMH\fR to favor `!' over `@'.
247:
248: .ti -.5i
249: BERK
250: .br
251: Optional for for 4.{2,3}BSD sites running SendMail.
252: Makes a lot of simplifying assumptions that makes the code run a bit faster.
253: Also enables one other change:
254: \fIscan\fR has a -[no]reverse switch which does the obvious thing.
255: \fIMH\fR purists hate this.
256:
257: .ti -.5i
258: BIND
259: .br
260: If you are running with the BIND code under 4.{2,3}BSD,
261: be sure to define this.
262:
263: .ti -.5i
264: BSD42
265: .br
266: Use on Berkeley UNIX systems on or after 4.2BSD.
267:
268: .ti -.5i
269: BSD41A
270: .br
271: Use on 4.1a Berkeley UNIX systems.
272:
273: .ti -.5i
274: BSD43
275: .br
276: Use on 4.3 Berkeley UNIX systems.
277: Also, be sure to use \*(lqoptions BSD42\*(rq.
278:
279: .ti -.5i
280: COMPAT
281: .br
282: If you previously ran a version of \fIMH\fR earlier than mh.4 use this option.
283: After a short grace period,
284: remove it and re-{configure,generate,install} everything.
285:
286: .ti -.5i
287: DPOP
288: .br
289: Enables the POP database, useful only if POP service is enabled.
290:
291: .ti -.5i
292: DUMB
293: .br
294: Directs \fIMH\fR to minimize address munging.
295:
296: .ti -.5i
297: FOLDPROT
298: .br
299: Defines the octal value for default folder-protection.
300: For example, FOLDPROT='\*(lq0700\*(rq'.
301: The default is \*(lq0711\*(rq.
302:
303: .ti -.5i
304: ISI
305: .br
306: Tells \fIrepl\fR to be more conservative in generating \*(lqcc:\*(rqs to the
307: user.
308:
309: .ti -.5i
310: LINK
311: .br
312: Defines the filename for alternate file name for \fIdist\fR and \fIrepl\fR.
313: For example, LINK='\*(lq\\\\043\*(rq'.
314: The default is \*(lq@\*(rq.
315:
316: .ti -.5i
317: locname
318: .br
319: Hard\-wires the local name for the host \fIMH\fR is running on.
320: For example, locname='\*(lqPICKLE\*(rq'.
321: It's probably better to either let UNIX tell \fIMH\fR this information,
322: or to put the information in the host specific \fBmtstailor\fR file.
323:
324: .ti -.5i
325: MHE
326: .br
327: Enables crude support for Brien Reid's MHE interface.
328:
329: .ti -.5i
330: MHRC
331: .br
332: Enables \fIMH\fR to recognize the \fICShell\fR's `~'\-construct.
333: This is useful for sites that run with a ~/.mhrc for their users.
334:
335: .ti -.5i
336: MORE
337: .br
338: Defines the location of the \fImore\fR\0(1) program.
339: For example, on ALTOS and DUAL systems,
340: MORE='\*(lq/usr/bin/more\*(rq'.
341: The default is \*(lq/usr/ucb/more\*(rq.
342:
343: .ti -.5i
344: MSGPROT
345: .br
346: Defines the octal value for default folder-protection
347: For example, MSGPROT='\*(lq0600\*(rq'.
348: The default is \*(lq0644\*(rq.
349:
350: .ti -.5i
351: NOMHSEQ
352: .br
353: Directs \fIMH\fR to make private sequences the default.
354:
355: .ti -.5i
356: OVERHEAD
357: .br
358: Enable \fIMH\fR commands to read profile/context from open fd:s
359: without doing an open(); see mh-profile(5) for the details.
360:
361: .ti -.5i
362: RPATHS
363: .br
364: Directs \fIinc\fR to note UNIX From: lines as Return-Path: info.
365:
366: .ti -.5i
367: RPOP
368: .br
369: Enables the RPOP variant of POP, useful only if POP service is enabled.
370:
371: .ti -.5i
372: SBACKUP
373: .br
374: Defines the prefix string for backup file names.
375: For example, SBACKUP='\*(lq\\\\043\*(rq'.
376: The default is \*(lq,\*(rq.
377:
378: .ti -.5i
379: SYS5
380: .br
381: Use on AT&T SYSTEM 5 UNIX system.
382:
383: .ti -.5i
384: TTYD
385: .br
386: Support for TTYD.
387:
388: .ti -.5i
389: UCI
390: .br
391: First, \*(lq_\*(rq and \*(lq#\*(rq are recognized as the prefixes for
392: scratch files.
393: Second, support for the UCI group\-leadership mechanism is enabled in
394: \fIconflict\fR.
395: Third, support for \fB$HOME/.signature\fR files is enabled.
396:
397: .ti -.5i
398: UK
399: .br
400: Directs the \fIscan\fR program to generate UK-style dates.
401:
402: .ti -.5i
403: V7
404: .br
405: Use on V7 UNIX systems.
406: Also, be sure to use \*(lqoptions void=int\*(rq.
407:
408: .ti -.5i
409: WHATNOW
410: .br
411: Enable certain \fIMH\fR commands to act differently when $mhdraft set.
412: .in -.5i
413:
414: .ti -.5i
415: ccoptions:
416: .br
417: Options given directly to \fIcc\fR\0(1).
418: The most common is \*(lq\-M\*(rq if you're running \fIMH\fR on an ALTOS.
419:
420: .ti -.5i
421: curses: \-lcurses\0\-ltermlib
422: .br
423: This should be the loader option required to load the \fItermcap\fR\0(3)
424: and \fIcurses\fR\0(3) libraries on your system.
425: On SYS5 systems, it probably should be just \*(lq\-lcurses\*(rq.
426: Some sites have reported that both \*(lq\-lcurses\*(rq and
427: \*(lq\-ltermlib\*(rq are necessary.
428:
429: .ti -.5i
430: ldoptions:
431: .br
432: Options given directly to \fIld\fR\0(1) (via \fIcc\fR\0) at the beginning
433: of the command line.
434: Useful for machines which require arguments to tell \fIld\fR to increase the
435: stack space (e.g. the Gould, which uses \*(lq\-m\08\*(rq).
436: Usually, \*(lq\-ns\*(rq is a good choice in any event.
437:
438: .ti -.5i
439: ldoptlibs:
440: .br
441: Options given directly to \fIld\fR\0(1) (via \fIcc\fR\0) at the end of the
442: command line.
443: The two most common are:
444: \*(lq\-ldbm\*(rq if you're running MMDF with the \fIdbm\fR package;
445: and, \*(lq\-lndir\*(rq if you are generating \fIMH\fR on a system
446: which does not load the new directory access mechanism by default
447: (e.g., 4.1BSD, SYS5).
448: If you don't have \fIlibndir\fR on your system,
449: the sources are in \fBmiscellany/libndir/\fR.
450:
451: .ti -.5i
452: oldload: off
453: .br
454: Support for the ALTOS loader.
455:
456: .ti -.5i
457: ranlib: on
458: .br
459: Support for systems with \fIranlib\fR\0(1).
460: For SYSTEM 5 systems,
461: this should be \*(lqoff\*(rq which tells \fIMH\fR to use \fIlorder\fR and
462: \fItsort\fR instead.
463: Some SYSTEM 5 sites reported that running this isn't always sufficient.
464: If this is the case,
465: then you should edit \fBconf/makefiles/uip\fR to include
466: \fB\&../sbr/libmh.a\fR and \fB../zotnet/libzot.a\fR twice in the LIBES
467: variable.
468:
469: .ti -.5i
470: tma: off
471: .br
472: Support for the TTI \fItrusted mail agent\fR (TMA).
473: Although the TTI TMA is \fBnot\fR in the public domain,
474: the \fIMH\fR support for the TTI TMA \fBis\fR in the public domain.
475: You should enable this option only if you are licensed to run the TMA
476: software
477: (otherwise, you don't have the software in your \fIMH\fR source tree).
478: .in -.5i
479: .PP
480: Now edit \fBconf/config/mtstailor\fR,
481: depending on your choice of the setting
482: for mts in the \fIMH\fR configuration file.
483: for an mts setting of \*(lqmh\*(rq,
484: look at the file \fBconf/tailor/mhmts\fR;
485: for an mts setting of \*(lqsendmail\*(rq, \*(lqsendmail/smtp\*(rq,
486: \*(lqmmdf/smtp\*(rq, or \*(lqmmdf2/smtp\*(rq,
487: look at the file \fBconf/tailor/sendmts\fR;
488: and,
489: for an mts setting of \*(lqmmdf\*(rq, or \*(lqmmdf2\*(rq,
490: look at the file \fBconf/tailor/mmdf\fR.
491: .PP
492: Now install the configured files into the source areas.
493: .sp 1
494: .nf
495: % make
496: % mhconfig MH
497: .fi
498: .PP
499: You now proceed based on your choice of a transport system
500: (the setting for mts above).
501: The best interface is achieved with \*(lqsendmail\*(rq
502: followed by \*(lqmmdf\*(rq or (\*(lqmmdf2\*(rq),
503: and then \*(lqmh\*(rq (stand\-alone delivery, not recommended).
504: .SS SENDMAIL
505: If you want \fISendMail\fR to transport messages for \fIMH\fR,
506: then go to the mts/sendmail/ directory.
507: .sp 1
508: .nf
509: % cd ../mts/sendmail/
510: .fi
511: .sp 1
512: This directory contains files whose definitions correspond to the
513: configuration of your \fISendMail\fR system.
514: If you have enabled BBoards or POP service,
515: then you will need to re\-configure \fISendMail\fR.
516: First, in the \*(lqlocal info\*(rq section of your site's
517: \fISendMail\fR configuration file,
518: choose a free macro/class (B is used in this distribution),
519: and add these lines:
520: .sp 1
521: .in +.5i
522: .nf
523: # BBoards support
524: DBbboards
525: CBbboards
526: .fi
527: .in -.5i
528: .sp 1
529: Second, immediately after the inclusion of the zerobase file,
530: in the \*(lqmachine dependent part of ruleset zero\*(rq section,
531: add these lines:
532: .sp 1
533: .in +.5i
534: .nf
535: # resolve names for the BBoards system
536: R$+<@$=B> $#bboards$@$2$:$1 topic@bboards
537: .fi
538: .in -.5i
539: .sp 1
540: Third, add the line
541: .sp 1
542: .in +.5i
543: .nf
544: include(bboardsMH.m4)
545: .fi
546: .in -.5i
547: .sp 1
548: after the line
549: .sp 1
550: .in +.5i
551: .nf
552: include(localm.m4)
553: .fi
554: .in -.5i
555: .sp 1
556: in your site's \fISendMail\fR configuration file.
557: Finally, you should link the file \fBmts/sendmail/bboardsMH.m4\fR into your
558: \fISendMail\fR cf/ directory and re\-configure \fISendMail\fR.
559: .PP
560: If you have enabled POP service,
561: a similar procedure must be used on the POP service host,
562: to re\-configure \fISendMail\fR.
563: First, in the \*(lqlocal info\*(rq section of your site's
564: \fISendMail\fR configuration file,
565: choose a free macro/class (P is used in this distribution),
566: and add these lines:
567: .sp 1
568: .in +.5i
569: .nf
570: # POP support
571: DPpop
572: CPpop
573: .fi
574: .in -.5i
575: .sp 1
576: Second, immediately after the inclusion of the zerobase file,
577: in the \*(lqmachine dependent part of ruleset zero\*(rq section,
578: add these lines:
579: .sp 1
580: .in +.5i
581: .nf
582: # resolve names for the POP system
583: R$+<@$=P> $#pop$@$2$:$1 subscriber@pop
584: .fi
585: .in -.5i
586: .sp 1
587: Third, add the line
588: .sp 1
589: .in +.5i
590: .nf
591: include(popMH.m4)
592: .fi
593: .in -.5i
594: .sp 1
595: after the line
596: .sp 1
597: .in +.5i
598: .nf
599: include(localm.m4)
600: .fi
601: .in -.5i
602: .sp 1
603: in your site's \fISendMail\fR configuration file.
604: Finally, you should link the file \fBmts/sendmail/popMH.m4\fR into your
605: \fISendMail\fR cf/ directory and re\-configure \fISendMail\fR.
606: .SS MMDF
607: If you want \fIMMDF\fR to be your transport service,
608: and have \fBNOT\fR specified \*(lqmmdf/smtp\*(rq (or \*(lqmmdf2/smtp\*(rq)
609: as your mts setting,
610: then go to the mmdf/ directory.
611: (If you're using \*(lqmmdf/smtp\*(rq or \*(lqmmdf2/smtp\*(rq
612: as your mts setting, then skip to the next section.)
613: .sp 1
614: .nf
615: % cd ../mts/mmdf/
616: .fi
617: .sp 1
618: This directory contains files whose definitions correspond to the
619: configuration of your \fIMMDF\fR system.
620: .PP
621: If you're running \fIMMDF\-I\fR,
622: then copy the following files from wherever you keep the \fIMMDF\fR sources
623: to this directory: mmdf/h/ch.h, mmdf/h/conf.h, utildir/conf_util.h,
624: utildir/ll_log.h, mmdf/h/mmdf.h, utildir/util.h, mmdf/mmdf_lib.a,
625: and utildir/util_lib.a.
626: .PP
627: If you're running \fIMMDF\-II\fR,
628: then copy the following files from where you keep the \fIMMDF\fR sources
629: to this directory: h/ch.h, h/conf.h, h/dm.h, h/ll_log.h, h/mmdf.h, h/util.h,
630: and lib/libmmdf.a
631: .PP
632: If you have enabled bboards,
633: then the directories \fBsupport/bboards/mmdfI\fR
634: and \fBsupport/bboards/mmdfII\fR
635: contain information you'll need to
636: put a UCI BBoards channel in your \fIMMDF\fR configuration.
637: Similarly, if you have enabled option \*(lqmf\*(rq and are
638: running \fIMMDF\-I\fR,
639: then the \fBzotnet/mf/mmdfI/\fR directory contains information you'll need to
640: put a \fIUUCP\fR channel in your \fIMMDF\-I\fR configuration.
641: Finally, the directory \fBsupport/pop/mmdfII\fR contains information you'll
642: need to put a POP channel in your \fIMMDF\-II\fR configuration.
643: .PP
644: Note that \fIMMDF\-II\fR is distributed with the BBoards channel,
645: although the version in the \fIMH\fR distribution might be more current,
646: the version in the \fIMMDF\-II\fR distribution has been tested with that
647: revision of \fIMMDF\fR.
648: .SS MMDF/SMTP
649: If you are using \*(lqmmdf/smtp\*(rq as your mts setting,
650: then no futher MTS\-specific action is required on your part!
651: .SS MMDF2/SMTP
652: If you are using \*(lqmmdf2/smtp\*(rq as your mts setting,
653: then no futher MTS\-specific action is required on your part!
654: .SS "STAND\-ALONE DELIVERY"
655: If, instead, you want \fIMH\fR to handle its own mail delivery,
656: then no futher MTS\-specific action is required on your part!
657: .SH GENERATION
658: Go to the mh.6/ directory and generate the system.
659: .sp 1
660: .nf
661: % cd ../; make
662: .fi
663: .PP
664: This will cause a complete generation of the \fIMH\fR system.
665: If all goes well, proceed with installation.
666: If not, complain, as there \*(lqshould be no problems\*(rq at this step.
667: .SH INSTALLATION
668: If the directories you chose for the user\-programs and
669: support\-programs
670: (\*(lqbin\*(rq and \*(lqetc\*(rq in the \fBconf/MH\fR file)
671: don't exist,
672: you should create them at this point.
673: .PP
674: Before proceeding,
675: you should familiarize yourself with the \fIAdministrator's Guide\fR.
676: To generate an \fInroff\fR version, go to the doc/ directory
677: and type:
678: .sp 1
679: .nf
680: % (cd doc/; make ADMIN.doc)
681: .fi
682: .sp 1
683: To generate a \fItroff\fR version, type
684: .sp 1
685: .nf
686: % (cd doc/; make guide)
687: .fi
688: .sp 1
689: instead.
690: .PP
691: If you're already running \fIMH\fR at your site,
692: you should also read the \fImh.6\fR changes document.
693: The sources are in \fBpapers/mh6/\fR.
694: .PP
695: Next, if you enabled support for the UCI BBoards facility,
696: then create a login
697: called \*(lqbboards\*(rq with the following characteristics:
698: home directory is \fB/usr/spool/bboards/\fR with mode 755
699: (actually, use the value for \*(lqbbhome\*(rq given in the \fIMH\fR
700: configuration file),
701: login shell is \fB/bin/csh\fR (or \fB/bin/sh\fR),
702: and, encrypted password field is \*(lq*\*(rq.
703: The \*(lqbboards\*(rq login should own the \fB/usr/spool/bboards/\fR
704: directory.
705: In addition to creating \fB/usr/spool/bboards/\fR,
706: also create \fB/usr/spool/bboards/etc/\fR
707: and \fB/usr/spool/bboards/archive/\fR.
708: These directories should also be owned by the \*(lqbboards\*(rq login.
709: .PP
710: If you enabled support for POP,
711: then on the POP service host,
712: create a login called \*(lqpop\*(rq with the following characteristics:
713: home directory is \fB/usr/spool/pop/\fR with mode 755,
714: login shell is \fB/bin/csh\fR,
715: and, encrypted password field is \*(lq*\*(rq.
716: If you don't have \fB/bin/csh\fR on your system (V7),
717: then \fB/bin/sh\fR is just fine.
718: The \*(lqpop\*(rq login should own the \fB/usr/spool/pop/\fR directory.
719: .PP
720: If this is not the first time you have installed \fIMH\fR,
721: you may wish to preserve the following files:
722:
723: .nf
724: .in +.5i
725: .ta \w'VeryVeryBigDirectoryName 'u
726: \fIdirectory\fR \fIfiles\fR
727: etc/ MailAliases, mtstailor
728: /usr/spool/bboards/ BBoards, \&.cshrc, \&.mh\(ruprofile
729: /usr/spool/bboards/etc/ *
730: .re
731: .in -.5i
732: .fi
733: .PP
734: As the super-user, and from the mh.6/ directory, install the system.
735: .sp 1
736: .nf
737: # make inst\-all
738: .fi
739: .sp 1
740: This will cause the \fIMH\fR
741: processes and files to be transferred to the appropriate areas
742: with the appropriate attributes.
743: .SH TAILORING
744: See the \fIAdministrator's Guide\fR for information on tailoring \fIMH\fR for
745: the MTS, BBoards, and POP.
746: .SH DOCUMENTATION
747: In addition to this document,
748: the administrator's guide,
749: and the user's manual,
750: there are several documents referenced by the user's manual which may be
751: useful.
752: The sources for all of these can be found under the \fBpapers/\fR directory.
753: .SH "OTHER THINGS"
754: Consult the directory \fBmiscellany/\fR for the sources to a number of things
755: which aren't part of the mainstream \fIMH\fR distribution,
756: but which are still quite useful.
757: .SH FILES
758: Too numerous to mention. Really.
759: .SH "SEE ALSO"
760: make(1)
761: .SH BUGS
762: The \fImhconfig\fR program should be smarter.
763: .PP
764: The Makefiles should know when \fImhconfig\fR has been run and force
765: \*(lqmake clean\*(rq behavior.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.