Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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: Thu, 30 May 2002 13:11:38 +0200
From: Pavel Tsekov <ptsekov AT syntrex DOT com>
Reply-To: Pavel Tsekov <cygwin AT cygwin DOT com>
Organization: Syntrex, Inc.
X-Priority: 3 (Normal)
Message-ID: <07748651.20020530131138@syntrex.com>
To: cygwin AT cygwin DOT com
Subject: Re: The road to 1.3.11 -- please try the latest snapshot
In-Reply-To: <20020530032207.GA29644@redhat.com>
References: <20020530032207 DOT GA29644 AT redhat DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


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

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 :)


--
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/