From: yci@netcom.com (Yggdrasil Computing)
Subject: /etc/host.conf
Date: Sun, 17 Jan 1993 12:04:59 +0200




        Could somebody please point me to some documentation or source
code related to the host.conf file (which is apparently is not
the same thing as resolv.conf)?  Thanks in advance.

Adam J. Richter (adam@netcom.com)

From: Mitchum DSouza 
Subject:    Re: /etc/host.conf
Date: Mon, 18 Jan 1993 14:41:28 +0200



Adam asks:

>         Could somebody please point me to some documentation or source
> code related to the host.conf file (which is apparently is not
> the same thing as resolv.conf)?  Thanks in advance.

Please get the file I put up on sunsite.unc.edu in
	/pub/Linux/system/Network/net-lib-1.1.tar.Z
and read the manpage for the resolv+ code I integrated into the bind sources.

	PLEASE DO NOT USE THE LIBS INCLUDED - (as they, i.e. libnet and librpc,
have been reintegrated into libc after a lot of dissatisfaction about their
removal). Well I tell a lie - as you can use the libs with no harm, but I plan
mainly to use the libs for testing new code before submission into the main
libc - e.g for ypfake (nis) etc... Most people will only need to use the new
libc.so.4.2.

The source will have been included by HLU into his standard libc source (I
guess)

Also note that the source has been built with this define in place:

#define _PATH_HOSTCONF  __PATH_ETC"/host.conf"

This means that whenever a standard is derived for the positions of network
client/utilities/config files, then __PATH_ETC will/may be changed. Currently
__PATH_ETC is defined in resolv.h (or whatever when the library was built). If
you are not satisfied with these paths, then you are at liberty to build the
library and clients with a path of your choice by only altering resolv.h
(and/or netdb.h). This is the beauty of the having sources around !!

Mitch

From: yci@netcom.com (Yggdrasil Computing)
Subject: Config sources?
Date: Wed, 20 Jan 1993 11:26:51 +0200


	Does anybody know where I can find the sources to the
"config" program (for configuring network interfaces)?

Adam J. Richter (adam@netcom.com)