From: Paul Jackson <pj@sgi.com>
To: Petr Baudis <pasky@ucw.cz>
Cc: barkalow@iabervon.org, git@vger.kernel.org
Subject: Re: [4/5] Add option for hardlinkable cache of extracted blobs
Date: Sun, 17 Apr 2005 18:35:08 -0700 [thread overview]
Message-ID: <20050417183508.15beb1fd.pj@sgi.com> (raw)
In-Reply-To: <20050417201856.GJ1461@pasky.ji.cz>
Petr wrote:
> The documentation I've got says:
>
> "R_OK, W_OK and X_OK request checking whether the file exists and has
> read, write and execute permissions, respectively. F_OK just requests
> checking for the existence of the file."
You don't exactly say it, but I'm guessing that you think that this
documentation is stating that F_OK checks for the existance of the file
_regardless_ of path access permissions.
No so. Write your own little test program, and/or read the kernel source.
Even if the file exists, if its directory entry is not accessible to the
_real_ uid/gid, access F_OK will fail. If the problem is a lack of
seach permissions on some directory in the path, the errno will be
EACCES.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@engr.sgi.com> 1.650.933.1373, 1.925.600.0401
next prev parent reply other threads:[~2005-04-18 1:31 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050417144947.GG1487@pasky.ji.cz>
2005-04-17 15:20 ` [0/5] Patch set for various things Daniel Barkalow
2005-04-17 15:24 ` [1/5] Parsing code in revision.h Daniel Barkalow
2005-04-17 16:09 ` Petr Baudis
2005-04-17 16:44 ` Daniel Barkalow
2005-04-17 18:18 ` [1/5] " Linus Torvalds
2005-04-17 18:30 ` Petr Baudis
2005-04-17 19:25 ` Linus Torvalds
2005-04-17 19:45 ` Daniel Barkalow
2005-04-17 19:54 ` Linus Torvalds
2005-04-17 20:06 ` Linus Torvalds
2005-04-17 20:22 ` Daniel Barkalow
2005-04-17 19:09 ` Daniel Barkalow
2005-04-17 15:27 ` [2/5] Add merge-base Daniel Barkalow
2005-04-17 16:01 ` Petr Baudis
2005-04-17 16:36 ` Daniel Barkalow
2005-04-17 16:51 ` [2.1/5] " Daniel Barkalow
2005-04-17 21:21 ` Petr Baudis
2005-04-17 21:25 ` Daniel Barkalow
2005-04-17 15:31 ` [3/5] Add http-pull Daniel Barkalow
2005-04-17 18:10 ` Petr Baudis
2005-04-17 18:49 ` Daniel Barkalow
2005-04-17 19:08 ` Petr Baudis
2005-04-17 19:24 ` Daniel Barkalow
2005-04-17 19:59 ` Petr Baudis
2005-04-21 3:27 ` Brad Roberts
2005-04-21 4:28 ` Daniel Barkalow
2005-04-21 22:05 ` tony.luck
2005-04-22 19:46 ` Daniel Barkalow
2005-04-22 22:40 ` Petr Baudis
2005-04-22 23:00 ` Daniel Barkalow
2005-04-22 23:08 ` Petr Baudis
2005-04-22 23:12 ` Daniel Barkalow
2005-04-22 23:24 ` Martin Schlemmer
2005-04-17 18:58 ` [3.1/5] " Daniel Barkalow
2005-04-17 15:35 ` [4/5] Add option for hardlinkable cache of extracted blobs Daniel Barkalow
2005-04-17 17:47 ` Petr Baudis
2005-04-17 18:54 ` Daniel Barkalow
2005-04-17 19:25 ` Paul Jackson
2005-04-17 19:59 ` Petr Baudis
2005-04-17 20:03 ` Daniel Barkalow
2005-04-17 20:18 ` Petr Baudis
2005-04-18 1:35 ` Paul Jackson [this message]
2005-04-18 1:48 ` Petr Baudis
2005-04-18 4:49 ` Paul Jackson
2005-04-17 20:58 ` Russell King
2005-04-17 22:10 ` First ever real kernel git merge! Linus Torvalds
2005-04-18 1:24 ` [4/5] Add option for hardlinkable cache of extracted blobs Paul Jackson
2005-04-18 1:20 ` Paul Jackson
2005-04-17 15:37 ` [5/5] Add commit-id to version Daniel Barkalow
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050417183508.15beb1fd.pj@sgi.com \
--to=pj@sgi.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).