Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Thu, 13 Jul 2000 20:59:58 -0400
Message-Id: <200007140059.UAA28562@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: bkeener AT thesoftwaresource DOT com
CC: cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to: <VA.0000046d.022750b6@thesoftwaresource.com> (message from Brian
	Keener on Thu, 13 Jul 2000 20:46:02 EDT)
Subject: Re: time to unleash the new setup?
References:  <VA DOT 0000046d DOT 022750b6 AT thesoftwaresource DOT com>


> Message box that said "parse error"

The error reporting from the setup.ini parser needs lots of work :-(

> 2) when it got to groff setup gave me a byte count error and then 
> gracefully skipped groff and went on to the next file.  I manually 
> downloaded groff without a problem via ftp before going on to the next 
> step so not sure why setup burped on it.

That means that setup.ini doesn't match the .tar.gz file in the ftp
site.  In theory, that shouldn't happen.  Note that setup knows what
it downloaded, and what it installed, so you should have been able to
just re-run setup and it should have just installed the missing groff.

> Not sure what to look for since this is a Win95 machine as far as
> the logic you added for passwd, groups, the setup shells, etc.

If you double-click the new cygwin icon on the desktop and you get a
working bash shell, I guess it's working.  We don't try to create
/etc/passwd and /etc/group on Win9x because we don't know what to put
in them.