delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/12/15/13:07:06

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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: Wed, 15 Dec 2004 13:06:21 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Reini Urban <rurban AT x-ray DOT at>
cc: cygwin AT cygwin DOT com
Subject: Re: find crashes in /proc/registry
In-Reply-To: <41BF10F4.1050406@x-ray.at>
Message-ID: <Pine.GSO.4.61.0412151302150.2298@slinky.cs.nyu.edu>
References: <cpl2v0$b0d$1 AT sea DOT gmane DOT org> <20041213215844 DOT GA30011 AT trixie DOT casa DOT cgf DOT cx> <cpn24o$3du$1 AT sea DOT gmane DOT org> <41BF10F4 DOT 1050406 AT x-ray DOT at>
MIME-Version: 1.0

On Tue, 14 Dec 2004, 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.

'*' is a valid filename character (if not, please cite the part of POSIX
that claims that).  AFAIK, the only invalid filename character is '/',
which is a directory separator.  The problem with /proc/registry is that
'/' is a valid value name character, so keys like
"HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin"
end up as "/proc/registry/HKEY_LOCAL_MACHINE/SOFTWARE/Cygnus\
Solutions/Cygwin/mounts\ v2'/usr/bin'", which any Cygwin program
(including bash) will choke on.

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

If there's a solution, it should probably have something in common with
managed mounts...
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019