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 Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 31 May 2002 22:48:19 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: The road to 1.3.11 -- please try the latest snapshot Message-ID: <20020601024819.GA22455@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20020530032207 DOT GA29644 AT redhat DOT com> <07748651 DOT 20020530131138 AT syntrex DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <07748651.20020530131138@syntrex.com> User-Agent: Mutt/1.3.23.1i On Thu, May 30, 2002 at 01:11:38PM +0200, Pavel Tsekov wrote: >CF> Reports of success or failure to the list, please. > >First of all I decided to try the new /proc filesystem - here are some >things I have noticed and haven't seen them reported to the list so >far (or I missed them): > >1. Under /proc and /proc/registry you can "cd" to unexisting directories. > >paveltz AT MORDOR ~ >$ cd /proc/not_existing_dir > >paveltz AT MORDOR /proc/not_existing_dir >$ ls -l >ls: .: Not a directory > >paveltz AT MORDOR /proc/not_existing_dir > >Now if tou type "cd .." you get: > >paveltz AT MORDOR /proc/non_existing_dir >$ cd .. > >paveltz AT MORDOR /proc/non_existing_dir/.. >$ ls >104 140 1796 loadavg registry uptime >1144 1428 328 meminfo stat version > >paveltz AT MORDOR /proc/non_existing_dir/.. >$ cd .. > >paveltz AT MORDOR /proc/non_existing_dir/../.. >$ ls >bin cygwin.ico home sbin test_mds_7.bpr usr >cygwin.bat etc lib sys tmp var cd'ing to a nonexistent directory should now be fixed, i.e., it should not be possible to do so. >2. Deleting a directory under /proc/registry/ takes >enormous time if this directory has subdirectories. I tried to >trace with strace since first I thought that some kind of infinite >loop causes this behaviour, but then it turned out that "rm" is actually >working - it just takes too much time to complete ... Most of the time >is spent in the cygwin internal path conversion routines, trying to >convert the POSIX path representation of the registry key/data into >Win32 path name. > >Yes, I know this is read-only file system :) I didn't look at this one. Maybe Chris J will have some insight. Thanks for the report. 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/