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