From: Igor Peshansky <pechtcha@cs.nyu.edu>
To: The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated [experimental]: findutils-4.3.0-1
Date: Wed, 18 Jan 2006 14:45:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.63.0601180938150.20867@access1.cims.nyu.edu> (raw)
In-Reply-To: <43CE5088.4070806@byu.net>
On Wed, 18 Jan 2006, Eric Blake wrote:
> According to Igor Peshansky on 1/18/2006 7:17 AM:
> > I fully expect a couple of hippos in this thread as well, but
> > nonetheless...
>
> What's that noise behind me? And why are there footprints in my butter?
Heh, I thought hippos only sat on spammers...
> >>** Functional Changes
> >>New tests, -readable, -writable, -executable. These check that a file
> >>can be read, written or executed respectively.
> >
> > Can someone explain to me how these are different from "-perm -0400",
> > "-perm -0200", and "-perm -0100" respectively? Do they use access()?
>
> Yes. Due to ACLs, it is possible for -readable to return true (it uses
> access()) and -perm /0444 to return false (it uses stat()). Also, note
> that -perm /0444 is different than -perm -0444 (/0444 is any of the three
> read bits set, regardless of all other bits, where -0444 is all three read
> bits set. Thus, a file can be readable, have no ACLs, and pass -perm
> /0444 while failing -perm -0444).
Ok, thanks! BTW, is /0444 also new? Didn't it use to be +0444?
> By the way, James added these new options at my request, although he
> chose a different name for the predicate than my original proposal:
> https://savannah.gnu.org/support/index.php?func=detailitem&item_id=104720
Interesting... FWIW, I think having one -access test (and reusing the
code from -perm to parse +r/+w/+x/=r/=w/=x/-r/-w/-x) makes more sense...
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
next prev parent reply other threads:[~2006-01-18 14:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.43CE3E6D.6050603@byu.net>
2006-01-18 14:17 ` Igor Peshansky
2006-01-18 14:28 ` Eric Blake
2006-01-18 14:45 ` Igor Peshansky [this message]
2006-01-18 15:06 Eric Blake
2006-01-18 15:19 ` Igor Peshansky
2006-01-18 15:28 ` Dave Korn
2006-01-18 15:39 ` Igor Peshansky
2006-01-19 13:45 ` Eric Blake
2006-01-19 14:14 ` Igor Peshansky
2006-01-19 14:43 ` Martin Slack
2006-01-19 14:49 ` Igor Peshansky
2006-01-19 3:22 REV KEVIN OLSON
2006-01-19 3:48 ` Christopher Faylor
2006-01-19 6:49 ` Gary R. Van Sickle
2006-01-19 3:31 Eric Blake
2006-01-19 14:46 Williams, Gerald S (Jerry)
2006-01-19 14:52 ` Gary R. Van Sickle
2006-01-19 15:17 ` Dave Korn
2006-01-19 15:39 ` Igor Peshansky
2006-01-19 16:33 ` Brian Dessent
2006-01-19 16:44 ` Dave Korn
2006-01-19 16:53 ` Igor Peshansky
2006-01-19 17:16 ` Dave Korn
2006-01-19 17:35 ` Corinna Vinschen
2006-01-19 17:44 ` Dave Korn
2006-01-19 15:23 ` Dave Korn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.63.0601180938150.20867@access1.cims.nyu.edu \
--to=pechtcha@cs.nyu.edu \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).