From: Kevin W. Hammond <hammond@kwhpc.caseng.com> Subject: Re: Broken symlinks ?? (followup) Date: Mon, 31 Aug 1992 05:46:08 GMT
|
| ** Mitchum D'Souza said:
| > Anyway about symbolic links: Say you have a binary, lets take `ls' for
| > example. Now say there is a symbolic link to it - maybe `dir'. Now if the
| > actual executable (ls) is non-readable then the symbolic link (dir) will fail
| > to execute. Theoretically this is the correct behavior, [...]
|
| No, this isn't correct behavior. That's the whole purpose of the execute
| permission bit: allow execute, but not read. Almost all of the executables
| on my system have mode 711. That includes symbolic links to executables
| (but I'm still on 0.97).
|
| > [...] (neither bash nor zsh), until the actual binary is make a+r.
|
| I dunno about bash and zsh, but tcsh works correctly with executables/symbolic
| links that are mode 711.
|
0.97 seems to fail if the actual executable is owned by root and has a mode of
711 (or actually, any mode that does not include read permission). If the executable
is owned by a non-root user, things do work correctly. Is this some sort of security
measure in the kernel? Maybe I (or anyone else) should look at the kernel code to
find out!
BTW: Darren - it looks like you finally made a break away from UUPC/Extended and into
the Linux world. How do you like it so far??
-kwh-
-- Kevin W. Hammond hammond@kwhpc.caseng.comCASE Engineering * 575 W. Madison #1601 * Chicago, IL 60661 * (312)902-2161