Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3D80C870.7060909@etr-usa.com>
Date: Thu, 12 Sep 2002 11:01:36 -0600
From: Warren Young <warren AT etr-usa DOT com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Beginnings of a patch: /etc/hosts
References: <Pine DOT GSO DOT 4 DOT 44 DOT 0209111814450 DOT 1269-300000 AT slinky DOT cs DOT nyu DOT edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Igor Pechtchanski wrote:
> 
> On another note, I'm not sure why you were checking for the presence of
> the windows files.  

I'm only checking for the existence of the Windows directory where we 
are expecting to find the hosts file and such.  This is to protect 
against the preceding code somehow failing to find the correct 
directory.  Let's say the script is somehow fooled into generating a 
WinNT-style path on a 9x type box: in that case the path won't exist, so 
even though the symlink can be created, it won't point to a useful path.

 > We could still create dangling symlinks if they are
> missing, which will allow the files to be created by editing/saving the
> symlink.

Precisely the correct behavior.

On Win9x systems, hosts and such don't exist until the user creates one. 
There's a *.sam ("sample") version of those files by default.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/