X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-0.1 required=5.0	tests=AWL,BAYES_00,GENERIC_IXHASH,KHOP_THREADED,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
X-MXL-Hash: 4f8598542ea9e788-1756596dbb1807c6cdc4413ae116e1697c846a45
From: "PRIKHODKO, GEORGE" <gp1865@att.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: Problem in searching /proc/registry.
Date: Wed, 11 Apr 2012 14:41:58 +0000
Message-ID: <397AD605DAD9254D9D2FFE207111E6441063A3A8@MOKSCY3MSGUSR9D.ITServices.sbc.com>
References: <397AD605DAD9254D9D2FFE207111E64410638476@MOKSCY3MSGUSR9D.ITServices.sbc.com> <4F849D97.2040704@t-online.de> <20120411085020.GC2415@calimero.vinschen.de>
In-Reply-To: <20120411085020.GC2415@calimero.vinschen.de>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
X-MAIL-FROM: <gp1865@att.com>
X-AnalysisOut: [v=1.0 c=1 a=n0W3tbonh9AA:10 a=v6y5nzg3jQMA:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=IkcTkHD0fZMA:10 a=Qs8R1XBwmid1qB]
X-AnalysisOut: [FB/a8mmA==:17 a=w_pzkKWiAAAA:8 a=zJ4bh0xDnEBLnP_YllEA:9 a=]
X-AnalysisOut: [QEXdDO2ut3YA:10 a=buB1NfXUTBUA:10 a=IfQ-iFkkCvMA:10]
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id q3BEgp3U014847

Thank you for taking care of it.

Thanks,
George Prikhodko


On Apr 10 22:52, Christian Franke wrote:
> PRIKHODKO, GEORGE wrote:
> >Hi,
> >
> >Since Cygwin 1.7.12 version find command run on /proc/registry started to fail with massages 'find: File system loop detected...'.
> >
> >>find /proc/registry -type f
> >find: File system loop detected; `/proc/registry/HKEY_CLASSES_ROOT' is part of the same file system loop as `/proc/registry'.
> >find: File system loop detected; `/proc/registry/HKEY_CURRENT_CONFIG' is part of the same file system loop as `/proc/registry'.
> >find: File system loop detected; `/proc/registry/HKEY_CURRENT_USER' is part of the same file system loop as `/proc/registry'.
> >find: File system loop detected; `/proc/registry/HKEY_LOCAL_MACHINE' is part of the same file system loop as `/proc/registry'.
> >find: File system loop detected; `/proc/registry/HKEY_USERS' is part of the same file system loop as `/proc/registry'.
> >find: File system loop detected; `/proc/registry/HKEY_PERFORMANCE_DATA' is part of the same file system loop as `/proc/registry'.
> >
> >Has something changed in a way Cygwin 1.7.12 and up handles Windows registry?
> >
> 
> This is likely a regression. Cygwin now returns same inode number
> 253 for each entry below /proc/registry node:

Should be fixed in CVS.


Thank,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


