RE: cygwin 2.22 find in NT 4.0

["Ayers, Mike" <Mike_Ayers at bmc dot com>]

> From: AlbertGalick@attotech.com [mailto:AlbertGalick@attotech.com]
>
> I have installed the Windows NT SDK (as myself, apparently)
> which is what
> gives
> me the following least obscure bug example (as NT administrator):
>
> $ ls mstools/bin/*.Ini
> mstools/bin/Port.Ini   mstools/bin/Win16.Ini   mstools/bin/WinNT.Ini
>
> $ find . -name "Port.Ini" -print
>
> $ find . -name "WinNT.Ini" -print
>
> $
>

	I myself discovered that cygwin's find is case hypersensitive.
Despite the
case insensitive nature of the Windows filesystems, apparently find gets the
name
of the file and compares against that, so that it only matches if your
pattern
is the exact (case matched) string that the FS is returning.  However, your
examples imply that you have handled this already.  Try:

$ find . -name [Pp][oO][Rr][Tt]\.[Ii][Nn][Ii]

	I just tested this (with win.ini) and it works nicely.  I haven't
written
the awk script to convert all alphas to 2 character classes yet, but I'd be
happy
to post it once it's ready...


	HTH,

/|/|ike

> I can find these .ini's with no problem as myself.
> Here's the output of cygcheck -s -v -r (as administrator)
> (See attached file: Cygcheck.nt) (Embedded image moved to file:
> pic26500.pcx)
> The most notable differences in the output as myself are the
> LOGONSERVER,
> USERNAME and USERPROFILE variables.
> The profiles themselves are very different but nothing pops
> out to explain
> this specific behavior w.r.t. the SDK.
>
> Other than waiting for a cygwin fix (I'm not a developer), is there
> possibly
> anything in my configuration that I might fix?  Should I
> re-install the SDK
> (and any other software I want to look at with cygwin) in a
> certain way?
>
> Albert Galick
>

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com