X-Spam-Check-By: sourceware.org Date: Tue, 20 Feb 2007 08:48:15 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: 1.5.24 unable to access files via root / (forward slash) Message-ID: <20070220134814.GB20598@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <9061924 DOT post AT talk DOT nabble DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9061924.post@talk.nabble.com> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Tue, Feb 20, 2007 at 05:44:51AM -0800, Jeff2007 wrote: >Hi, > >I'm trying to access files for reading via the / directive, i.e. vi >/usr/foo.txt >However, this will not open foo.txt, vi creates a new file in the current >directory instead. >I can cd to the /usr directory and open the file with vi usr.txt. I'm using >vi as an example, I'm actually trying to compile files with a gcc variant, >and it can't access files the the / path either. > >I've checked with the mount command that / is mounted, and it reports: >D:\cygwin_root on / type system (binmode) >Output from ls -lg /usr shows >-rwxrwxrwx 1 mkgroup-l-d 13 Feb 20 13:33 foo.txt >Which seems ok from what I've read? > >I've attached the output from cygcheck using cygcheck -srvv. Apologies if >I'm missing something really simple here. > >http://www.nabble.com/file/6655/cygcheck.out cygcheck.out Well, from the cygcheck output, it seems like you aren't actually running a cygwin version of vim, so it is unlikely that 'vi' would understand cygwin's mount table. 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/