Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 15 Jun 2005 18:52:49 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: check_case:strict problem Message-ID: <20050615225249.GA27652@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <20050615214129.GB25507@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050615214129.GB25507@trixie.casa.cgf.cx> User-Agent: Mutt/1.5.8i On Wed, Jun 15, 2005 at 05:41:29PM -0400, Christopher Faylor wrote: >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. Ok. I duplicated it. It has to be a share as in //foo/bar, not, /foo/bar/blaz. The next snapshot should fix it. 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/