Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Date: Wed, 15 Jun 2005 17:41:29 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: check_case:strict problem
Message-ID: <20050615214129.GB25507@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <Pine DOT CYG DOT 4 DOT 58 DOT 0506151608110 DOT 2428 AT Crunch DOT bcgssbd DOT sciatl DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.CYG.4.58.0506151608110.2428@Crunch.bcgssbd.sciatl.com>
User-Agent: Mutt/1.5.8i

On Wed, Jun 15, 2005 at 04:22:01PM -0400, Shaffer, Kenneth wrote:
>>>Along similar lines as the ls failure on shares with
>>>CYGWIN=check_case:strict, if /etc/passwd has a home directory set to a
>>>share, bash won't even start.
>>
>>WJFFM.  There was a problem pre-snapshot but bash still started.  Now I
>>get no errors.
>
>Really?  You DID edit your /etc/passwd and change the home directory to be
>a share?

No.  I didn't.  My home directory has been a share for about five years
now.

I sure did notice the huge slowdown in using CYGWIN=check_case:strict, though.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/