projects / unix-history / blame
| Commit | Line | Data |
|---|---|---|
| 15637ed4 RG |
1 | This directory contains cf files for these machines: |
| 2 | ||
| 3 | cad /* cad.berkeley.edu */ | |
| 4 | cadgroup /* any cadgroup machine */ | |
| 5 | cc /* computer center microvax */ | |
| 6 | cchem /* any machine in college of chemistry */ | |
| 7 | cogsci /* cogsci (to deal with uucp link) */ | |
| 8 | ic /* ic (to deal with uucp link) */ | |
| 9 | okeeffe /* okeeffe (to deal with uucp link) */ | |
| 10 | ucbarpa /* ucbarpa (to deal with uucp link) */ | |
| 11 | ucbvax /* ucbvax (to deal with uucp link) */ | |
| 12 | ||
| 13 | ucbproto.cf /* any Berkeley nameserver/hosttable machine */ | |
| 14 | ||
| 15 | tcpproto.cf /* any TCP/IP (SMTP) based machine */ | |
| 16 | uucproto.cf /* any UUCP only machine */ | |
| 17 | tcpuucpproto.cf /* a UUCP hub on a TCP/IP (SMTP) network */ | |
| 18 | ||
| 19 | Most all of the good stuff is contained in proto.mc. For all | |
| 20 | machines except ucbvax, all the .mc files do is define some m4 | |
| 21 | constants and include proto.mc. | |
| 22 | ||
| 23 | To make a file, say | |
| 24 | ||
| 25 | make cad.cf | |
| 26 | ||
| 27 | for example. | |
| 28 | ||
| 29 | N.B.: if you intend to maintain configuration files for more than | |
| 30 | one or two machines, you should probably create ".mc" files along | |
| 31 | the lines of the machine names above and use m4. If you just try | |
| 32 | to modify ".cf" files you'll eventually go insane. |