[1135] in Athena Bugs
(VS2) Version 6.0C: "source" in csh doesn't distinguish executables
daemon@ATHENA.MIT.EDU (jik@ATHENA.MIT.EDU)
Thu Oct 6 12:18:41 1988
From: <jik@ATHENA.MIT.EDU>
Date: Thu, 6 Oct 88 12:18:21 EDT
To: henry@ATHENA.MIT.EDU
Cc: bugs@ATHENA.MIT.EDU
In-Reply-To: Henry Mensch's message of Wed, 05 Oct 88 22:11:52 EDT <8810060211.AA10216@GARP.MIT.EDU>
After doing a little investigation, I've discovered why the message
"cannot open" is being displayed instead of "not an RT executable".
It's still a bug, but not with source.
First of all, I might have stated that "not an RT executable" is the
error I received when I attempted to run /mit/18.03/1803/1803 from
command-line on the RT. This is incorrect -- I received "cannot open"
in that situation as well.
The reason that "cannot open" was being returned as an error message
is that the permissions on the executable /mit/18.03/1803/1803 are set
to 711.
This is still a bug, though. If I set the permissions on an RT
executable to 111 and then attempt to run it on an RT, it runs
perfectly. Therefore, if I set the permissions on a VAX executable to
111 and attempt to run it on an RT, I should get "not an RT
executable" instead of "cannot open".
Sample:
(when crypto is run without any arguments, it prints a usage message,
so if the usage message is printing, then the program is executing
properly.)
m4-167-3% cd ~/c/crypto
m4-167-3% chmod 111 crypto.rt
m4-167-3% crypto.rt
usage: crypto.rt [-cegnru] [file(s)]
help: crypto.rt -h, crypto.rt -i
m4-167-3% chmod 111 crypto.vax
m4-167-3% crypto.vax
crypto.vax: crypto.vax: cannot open
m4-167-3% echo $hosttype
rt
jik
