DataMuseum.dk

top - metrics - download

    Length: 1110 (0x456)
    Types: TextFile
    Names: »README«

└─⟦9ae75bfbd⟧ Bits:30007242 EUUGD3: Starter Kit
    └─⟦02f44f254⟧ »EurOpenD3/mail/sendmail.5.65.tar.Z« 
        └─⟦4e8d58309⟧ 
            └─⟦this⟧ »./cf/cf/README« 
└─⟦9ae75bfbd⟧ Bits:30007242 EUUGD3: Starter Kit
    └─⟦bfebc70e2⟧ »EurOpenD3/mail/sendmail-5.65b+IDA-1.4.3.tar.Z« 
        └─⟦f9e35cd84⟧ 
            └─⟦this⟧ »sendmail/cf/cf/README« 

TextFile

This directory contains cf files for these machines:

	cad		/* cad.berkeley.edu */
	cadgroup	/* any cadgroup machine */
	cc		/* computer center microvax */
	cchem		/* any machine in college of chemistry */
	cogsci		/* cogsci (to deal with uucp link) */
	ic		/* ic (to deal with uucp link) */
	okeeffe		/* okeeffe (to deal with uucp link) */
	ucbarpa		/* ucbarpa (to deal with uucp link) */
	ucbvax		/* ucbvax (to deal with uucp link) */

	ucbproto.cf	/* any Berkeley nameserver/hosttable machine */

	tcpproto.cf	/* any TCP/IP (SMTP) based machine */
	uucproto.cf	/* any UUCP only machine */
	tcpuucpproto.cf	/* a UUCP hub on a TCP/IP (SMTP) network */

Most all of the good stuff is contained in proto.mc.  For all
machines except ucbvax, all the .mc files do is define some m4
constants and include proto.mc.

To make a file, say

	make cad.cf

for example.

N.B.: if you intend to maintain configuration files for more than
one or two machines, you should probably create ".mc" files along
the lines of the machine names above and use m4.  If you just try
to modify ".cf" files you'll eventually go insane.