>A little bit of explanations. I asked the question, because I found discrepancy in the permissions. Who, how, when, and why changed the permissions - I don't know, that's another story. However the system seemed to work properly with r-x on /bin/sh. The problem occured during installation of some IBM product, part of IDz (former RDz - Rational Developer for System z). Change to r-t fixed the problem.
Not sure what the problem was that you encountered. However, it seems to me that some part of your installation had not been done properly or completely. The shell is installed into LPA *and* into the /bin path of your version root file system. without the sticky bit, the version from the /bin directory is always used. The LPA version is not relevant. With the sticky bit, the LPA version is always used, and the version in /bin is not relevant. Except when the shell is not found in LPA, then the loader goes back and loads it from the /bin directory. I cannot say how a version discrepancy could cause troubles, but the same issue might exist with other sticky bit UNIX binaries, and the corresponding load module. As a side note: Other permission r-x is exactly the same as r-t from a permission point of view. The lower case t means x permission and sticky bit is set. Its kind of as overpunching on punch cards. The sticky bit is show in the same position as the execute permission. Sticky and no execute permission is shown as T, sticky and execute permission is shown as t. No sticky bit but execute permission is shown as x. Similarly, the Set-UID-bit and Set-Gid-bit are "overpunched" over the x position in the Owner, and Groups parts, resp. Shown as S or s, depending on whether execute permission is also present or not. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
