From: prj@po.cwru.edu (Paul Jarc)
Cc: bug-guile@gnu.org
Subject: Re: [PATCH] Small fixes in doc/ref/srfi-modules.texi; a couple other questions
Date: Mon, 05 May 2003 11:56:14 -0400 [thread overview]
Message-ID: <m3bryhpetn.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <200305022204.53383.s11@member.fsf.org> (Stephen Compall's message of "Fri, 2 May 2003 22:04:10 -0500")
Stephen Compall <s11@member.fsf.org> wrote:
> But since the ruid == euid etc. in non-set?id programs, I don't see
> the problem at first glance (though it could conceivably cause
> problems in set?id programs :).
access() is merely a waste of time in non-set?id programs. They can
just do whatever they want to do without explicitly checking for
permission first; if there's a permission problem, the operation will
simply fail. set?id programs should use access() because they have
more permissions than they sometimes want to use; the operation might
succeed when it ought to fail.
paul
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2003-05-05 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-03 3:04 [PATCH] Small fixes in doc/ref/srfi-modules.texi; a couple other questions Stephen Compall
2003-05-05 15:56 ` Paul Jarc [this message]
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: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3bryhpetn.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=bug-guile@gnu.org \
/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).