This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: find crashes in /proc/registry

On Tue, Dec 14, 2004 at 11:28:34AM -0500, Chuck wrote:
>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

To answer your question:  No, there are no plans to fix "it".


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]