DataMuseum.dk

Presents historical artifacts from the history of:

DKUUG/EUUG Conference tapes

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about DKUUG/EUUG Conference tapes

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - metrics - download
Index: T b

⟦6a553e031⟧ TextFile

    Length: 2966 (0xb96)
    Types: TextFile
    Names: »bsd-network«

Derivation

└─⟦9ae75bfbd⟧ Bits:30007242 EUUGD3: Starter Kit
    └─⟦2fafebccf⟧ »EurOpenD3/mail/smail3.1.19.tar.Z« 
        └─⟦bcd2bc73f⟧ 
            └─⟦this⟧ »conf/driver/bsd-network« 

TextFile

# @(#)bsd-network	1.5 12/17/88 21:21:44

# this file lists the drivers used in a UNIX environment with
# BSD networking functionality.

# to add a new driver, make a source file in the tports/, routers/, or
# directors/ directory, whichever is appropriate, using the template
# from that directory.  Then, add the name of the driver in this file
# as a line of the form:
#
#	director  name	[flags]
# or	router	  name	[flags]
# or	transport name	[flags]
#
# the following flags can follow name:
#
#	nocache		- signify that there is no routine to cache
#			  resources
#	nofinish	- signify that there is no routine to free
#			  resources
#	nobuilder	- signify that there is no routine to read entries
#			  from the section configuration file
#	source=name	- specify the file containing the driver's source
#			  non-absolute names are relative to the appropriate
#			  source directory.  By default this is the
#			  name of the driver, with an extention of .c.
#	header=name	- specify the header file which contains the
#			  current version number.  By default this is
#			  the source file with an extension of .h rather
#			  than .c.
#
# ordering is not important, though it can make this file easier to read
#
# non-driver library routines for a particular driver library can be
# included using lines of the form:
#
#	director library  sourcefile...
# or	router library	  sourcefile...
# or	transport library sourcefile...
#
# where sourcefile can be a .c or .h file, whose source is in the
# appropriate driver source directory.  The objects are loaded into the
# library in the order specified, making the order important if library
# routines refer to each other.  Library source files are useful for
# creating common code that can be used by multiple drivers.


# director drivers
director aliasinclude	source=include.c nocache nofinish
director forwardinclude	source=include.c nocache nofinish
director genericinclude	source=include.c nocache nofinish
director aliasfile	nocache nofinish
director forwardfile	nocache nofinish source=fwdfile.c
director user		nocache nofinish
director smartuser	nocache nofinish


# router drivers
router	pathalias	nocache nofinish
router	uuname
router	smarthost	nocache nofinish

# note: the queryprogram driver is not used in default router configuration
router	queryprogram	source=queryprog.c nocache nofinish

# use these only if you have BSD networking routines
router	gethostbyname	source=gethost.c nocache nofinish
router	gethostbyaddr	source=gethost.c nocache nofinish

# use this only if you have the Berkeley BIND package
#router	bind		nocache nofinish

# this library source file is used by most routers above
router library rtlib.c rtlib.h


# transport drivers
transport pipe		nocache nofinish
transport appendfile	nocache nofinish

# use this only if you have BSD networking routines
transport smtp		source=tcpsmtp.c nocache nofinish
transport tcpsmtp	nocache nofinish
transport library	smtplib.c smtplib.h