From: haahr@mv.us.adobe.com (Paul Haahr)
To: jeremy@sw.oz.au, rc@hawkwind.utcs.toronto.edu
Subject: Re: Porting rc to Linux
Date: Sun, 21 Mar 1993 23:16:37 -0500 [thread overview]
Message-ID: <9303220416.AA18919@astro.mv.us.adobe.com> (raw)
> When searching the path, why does rc try to double guess the kernel
> by testing the permissions itself rather than just trying to exec it?
because you want to be able to do the path search before you fork.
> And if it has to (whatis), why doesn't it just use the access system
> call rather than doing it for itself in rc_access?
because access lies if you run setuid or setgid, among other things.
next reply other threads:[~1993-03-22 4:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-03-22 4:16 Paul Haahr [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-03-22 3:43 Jeremy Fitzhardinge
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=9303220416.AA18919@astro.mv.us.adobe.com \
--to=haahr@mv.us.adobe.com \
--cc=jeremy@sw.oz.au \
--cc=rc@hawkwind.utcs.toronto.edu \
/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 NNTP newsgroup(s).