Description of problem:
This is installed at /bin/ksh, it is/was commonly also found at /usr/bin/ksh. If a script starts:
it will fail.
In RHel5 it was at both places.
Version-Release number of selected component (if applicable):
A symbolic link would fix it.
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
We are planning to document this is Migration Guide and release notes.
shells were intentionally moved out of /usr/bin
> shells were intentionally moved out of /usr/bin
I don't know if that is a good idea, at least not without leaving a symlink.
On many traditional unix systems (I am looking at an AIX one) ksh is in /usr/bin. The result of only having it in /bin will cause problems with portability of scripts between different Unix systems.
I have just checked a Debian squeeze/sid machine, I can see /usr/bin/ksh AND /bin/ksh --- so removing ksh from /usr/bin will cause portability problems between different Linux distros.
Please think again.
note added to migration guide
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
ksh in Red Hat Enterprise Linux 6 no longer contains /usr/bin/ksh symbolic link to /bin/ksh. Some scripts may need to change their shebang.
*** Bug 695434 has been marked as a duplicate of this bug. ***
*** Bug 871890 has been marked as a duplicate of this bug. ***