From: Mark-Jason Dominus <mjd@saul.cis.upenn.edu>
To: rc@archone.tamu.edu
Cc: mjd@saul.cis.upenn.edu
Subject: BUG: exec permission denied
Date: Tue, 2 Jul 1991 16:41:59 -0500 [thread overview]
Message-ID: <9107022142.AA10652@saul.cis.upenn.edu> (raw)
It seems that if I try to execute a command `foo' for which I don't have
execute permission, rc gives me `foo not found', which is justifiable if
rc had to do a path search to find `foo', but not justifiable if `foo'
specified a path. That is:
; echo $path
/usr/etc
; ls -l /usr/etc/shutdown
-rws------ 1 root 24576 Mar 6 1990 /usr/etc/shutdown
; shutdown
shutdown not found
makes sense (although you could argue against it), but
; /usr/etc/shutdown
/usr/etc/shutdown not found
is incorrect.
The night is pleasing to us because, like memory, it erases idle details.
Mark-Jason Dominus mjd@central.cis.upenn.edu
next reply other threads:[~1991-07-02 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-07-02 21:41 Mark-Jason Dominus [this message]
1991-07-02 22:25 ` Mark-Jason Dominus
1991-07-03 9:37 ` Boyd Roberts
1991-07-02 22:33 Byron Rakitzis
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=9107022142.AA10652@saul.cis.upenn.edu \
--to=mjd@saul.cis.upenn.edu \
--cc=rc@archone.tamu.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).