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
From: "John Marrett" <jmarrett AT mediagrif DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Invalid arugment and IO Error with bunzip2
Date: Tue, 22 Oct 2002 15:12:20 -0400
Message-ID: <B5B1F1162663D411BB8000508B691B2006076A43@stimxch1.dev.mediagrif.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <B5B1F1162663D411BB8000508B691B20060D528B@stimxch1.dev.mediagrif.com>
Importance: Normal

Christopher,

This was a clean install on a freshly installed Windows XP machine. It
is a domain client and not a standalone machine.

-JohnF

-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf
Of Christopher Faylor
Sent: October 22, 2002 11:56 AM
To: cygwin AT cygwin DOT com
Subject: Re: Invalid arugment and IO Error with bunzip2


On Tue, Oct 22, 2002 at 11:49:16AM -0400, William A. Hoffman wrote:
>My guess is this problem is related to the ntsec stuff as are many 
>recent posts.  Someone correct me if I am wrong, but to get cygwin to 
>work properly these days I had to do two things:
>
>1.  manually modify the /etc/passwd file mkpasswd -du mywindowslogin >>

>/etc/passwd Where mywindowslogin is the name of the account that you 
>log into windows with.
>
>2.  set CYGWIN=nontsec

There is no reason to do both.  If you are not going to use ntsec then
CYGWIN=nontsec should be equivalent to 1.3.12.

I'm amazed at the number of people who have incorrect /etc/passwd files.

>There are many posts of gcc does not work, patch does not work, bz2 
>does not work, XXX does not work....  I suspect many of these problems 
>are related to not being able to read/write files.
>
>Is there some way that this can be fixed?  If you run setup on a new 
>computer right now (or at least two days ago), gcc will not work and 
>all files you create
>will be owned by a non-existent user.    Perhaps there should be a
warning or a
>FAQ entry, but I would think that the default running of setup should 
>create a cygwin that works.

I haven't seen anyone say that running setup on a new computer doesn't
work. It seems to be existing implementations that need tweaking.  I
don't know why.

cgf

--
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/


--
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/