On Fri, 29 Aug 1997 11:32:35 -0400, you wrote:
/bin/ksh *has* to be executable. It is a shell and it needs to executable
for it to be of any use. Security concerns arise depending on *who* runs
it. Here is my ls -l /bin/ksh on Solaris 2.5
-r-xr-xr-x 2 bin bin 180816 May 2 1996 /bin/ksh
i.e. it has to be 'x' for user/group/world.
You were right--my ksh was not executable for anyone, and was actually a
corrupted file. Phooey. At least I feel that I'm making progress,
though...now I know what the problem is.
If you see a 's' instead of a 'x' in the above perms, you are in for some
fun, though!
Yikes--I've never seen an 's' in anything. I know read, write, and
'x'ecute...what's 's'?
All help much appreciated as usual. I feel like I should make brownies for
this group, or buy you a case of beer...
Sounds good!
If they can figure out a way to send beer over the internet, oh the virtual
parties that could be had...
-Bertha http://www.mhn.org/~bertha
Dr. Hibbert: You have twenty-four hours to live.
Homer: Twenty-four hours!
Dr. Hibbert: Well, twenty-two. I'm sorry I kept you waiting so long.