From: elf AT netcom DOT com (Marc Singer)
Message-Id: <199610231855.LAA10320@netcom4.netcom.com>
Subject: Re: Permissions for FIND?
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Wed, 23 Oct 1996 11:55:08 -0700 (PDT)
Cc: djgpp AT delorie DOT com (DJGPP List Alias)
In-Reply-To: <Pine.SUN.3.91.961023145314.7877B-100000@is> from "Eli Zaretskii" at Oct 23, 96 02:59:17 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 950       

> DOS-specific mode bits (such as hidden, system, volume, and archive) are 
> indeed not supported by `find', since it calls `stat' which doesn't know 
> about those DOSisms.  However, the read-only bit *is* supported, because 
> it just means that the write bit is NOT set.  Therefore, the following 
> should accomplish what you need:
> 
> 	find . -perm a=r -print
> or
> 	find . -perm 0222 -print
> 
> If you need the DOS-specific attributes, you will have to write a trivial
> program that tests for a certain attribute and returns 0 if it's set or 1
> if it's not; then just invoke it with -exec option to `find'. 
> 

OK.  I use the command 

  find <path> -perm a=r -print

for a path that contains a R/O file.  It is not found.  Neither does
the 0222 perm setting work.  I downloaded find for v2.01

  10-19-96 122880 bytes find.exe

I tried these syntax combinations last night along with +2, +20, +200,
-2, -20, and -200.  No luck.

Thots?