[1137] in Athena Bugs

home help back first fref pref prev next nref lref last post

(VS2) Version 6.0C: "source" in csh doesn't distinguish executables

daemon@ATHENA.MIT.EDU (jik@ATHENA.MIT.EDU)
Thu Oct 6 14:45:53 1988

From: <jik@ATHENA.MIT.EDU>
Date: Thu, 6 Oct 88 14:45:21 EDT
To: jtkohl@ATHENA.MIT.EDU
Cc: bugs@ATHENA.MIT.EDU
In-Reply-To: John T Kohl's message of Thu, 6 Oct 88 14:29:50 EDT <8810061829.AA01387@LYCUS.MIT.EDU>

This is incorrect.  The file with which I was showing the bug *is* an
NFS file and I was accessing it over the network.  When I set the
permissions to 111, I was able to execute it, but not read it, as long
as I executed it on the same machine.

Since the kernel on the workstation must be able to read a file in
order to execute it, root on the workstation must be able to read a
file which is set to 111 and which is being read over NFS.

Therefore, when I run an execute-only executable on a workstation, I
can run it because the kernel can read it.  Presumably, when I try to
run an execute-only executable on the wrong machine type, the kernel
(or whatever) should be able to read it, determine that it is of the
wrong type by looking at the magic number, and give "not a foo
executable" as the error when it discovers that it is not.

So why is it that the file can be read by root/kernel/whatever if it's
in the proper binary format, but can't be read if it is not?

jik

home help back first fref pref prev next nref lref last post