From owner-freebsd-hackers  Sun Jul  6 22:08:27 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id WAA24339
          for hackers-outgoing; Sun, 6 Jul 1997 22:08:27 -0700 (PDT)
Received: from misery.sdf.com (misery.sdf.com [204.244.210.193])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA24333
          for <freebsd-hackers@freebsd.org>; Sun, 6 Jul 1997 22:08:22 -0700 (PDT)
Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1)
	id 0wl5xY-0003qU-00; Sun, 6 Jul 1997 22:03:36 -0700
Date: Sun, 6 Jul 1997 22:03:35 -0700 (PDT)
From: Tom Samplonius <tom@sdf.com>
To: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
cc: freebsd-hackers@freebsd.org
Subject: Re: 127.1 and "localhost"  (name resolution problem.)
In-Reply-To: <199707070157.VAA00413@lakes.water.net>
Message-ID: <Pine.BSF.3.95q.970706220028.14775A-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Sun, 6 Jul 1997, Thomas David Rivers wrote:

> 127.1           localhost.water.net localhost
> 
> 
>  But - If I replace that line with:
> 
> 127.0.0.1           localhost.water.net localhost
> 
> 
>  Everything works fine.  I suggest that, until this problem
> is fixed,  we use 127.0.0.1 in any automated generation of 
> /etc/hosts... I'm not sure where mine came from; it could be an 
> older installation (e.g. upgrades...)

  I suspect that you put it there.  The last change to the /etc/hosts file
was made in 96/03/20.

>  If someone happens to be poking around in /etc/hosts resolution
> code; I'd be interested in knowning why this didn't work...

  Is it supposed to?  It is not a behaviour that seems useful in anyway.

> 	- Dave Rivers -

Tom