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: Tue, 14 Dec 2004 11:31:52 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: find crashes in /proc/registry Message-ID: <20041214163152.GD4346@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20041213215844 DOT GA30011 AT trixie DOT casa DOT cgf DOT cx> <41BF10F4 DOT 1050406 AT x-ray DOT at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Tue, Dec 14, 2004 at 11:28:34AM -0500, Chuck wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Reini Urban wrote: >| Chuck schrieb: >| >|> Christopher Faylor wrote: >|> | On Mon, Dec 13, 2004 at 04:52:31PM -0500, Chuck wrote: >|> |>I don't know if this has been reported before >|> | >|> | It has. >|> | The conclusion? >|> | Don't use find on /proc. >| >| >|> Are there any plans to fix it? Thanks. >| >| >| How? >| '*' is by POSIX definition an invalid filename character. >| '*' is by MS definition a valid registry key, which is mapped into a >| virtual file-system. >| >| If the findutils maintainer decides to add a /proc/registry patch to >| make '*' a valid filename char, other fileutils should be fixed also. >| ls and cat at least. >| >| So it should be better "fixed" in cygwin. How? >| Make it a valid file character there? >| How not to break all other file-,find-,text-,shellutils then, which will >| have to deal with this and glob expansion. >| >| Replace it by some other character? Which? > >Fixing it so that it least works in directories that don't have * as a >file name. Perhaps the directory I used as an example was a poor >choice. To answer your question: No, there are no plans to fix "it". 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/