Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <4.3.1.2.20020214093005.01dea388@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Thu, 14 Feb 2002 09:34:49 -0500 To: Roland Glenn McIntosh , cygwin AT cygwin DOT com From: "Larry Hall (RFK Partners, Inc)" Subject: Re: minor bug - No ".." directory gives error in ls In-Reply-To: <5.1.0.14.2.20020214083308.06041948@lnxmain> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 08:37 AM 2/14/2002, Roland Glenn McIntosh wrote: >In some cases when listing a directory in which there is no parent ls gives an error: > ls: ..: No such file or directory > >If there was no directory then I would expect ".." to refer to "." like it does in the root of a unix partition. Specifically, this happens with network shares. To reproduce: > >cd //192.168.0.2/shared >ls -la > >Where 192.168.168.0.2 is a server on which you have authenticated yourself or need no authentication, and 'shared' is a directory which has been shared. There should be no other resources available at 192.168.0.2 via CIFS other than the shared directory. OK. For me this works fine at my root (/). I do get the error you claim if I "ls .." from a network share directory, as you indicate. Since there is no analog to this in the UNIX world, it's not that surprising that this doesn't just work. If you are interested in providing a patch to implement the behavior you're interested in, I'm sure it will be thoughtfully considered. Otherwise, the mail archives will contain a record of your report for anyone looking for a bug to fix. Thanks, Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- 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/