Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The behaviour described below applies to ksh-20120801-21.el6.1 on RHEL 6 as well.
+++ This bug was initially created as a clone of Bug #1146161 +++
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Consistently
Steps to Reproduce:
1. yum install ksh
2. type ksh rksh
Actual results:
ksh is /bin/ksh
-bash: type: rksh: not found
Expected results:
I would expect a link for rksh to exist. The actually functionality is builtin
to the shell.
Additional info:
The synopsis for the ksh man page lists 'ksh', 'rksh', and 'pfksh'.
The 'rksh' functionality is built in, and only requires the symlink.
The 'pfksh' functionality is platform dependent (depends on solaris/illumos pfexec(1)) and could be removed from the man page.
AT&T ksh is my preferred shell for scripting, and does not share the same vulnerabilities as Bash. (Cf. CVE-2014-6271)
--- Additional comment from RHEL Product and Program Management on 2014-09-24 11:47:22 EDT ---
Since this bug report was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
--- Additional comment from Henk Langeveld on 2014-09-24 11:48:53 EDT ---
It's a drudge to keep adding the symlink during deployment, when a couple of lines in the rpm definition could do the trick.
--- Additional comment from errata-xmlrpc on 2014-10-06 09:43:44 EDT ---
Bug report changed to ON_QA status by Errata System.
A QE request has been submitted for advisory RHBA-2014:18335-02
https://errata.devel.redhat.com/advisory/18335
This is not a bug, it's a feature request and there is no customer requiring this. Do not clone feature requests to older branches in the future.
As there is no usable type of close status, closing as insufficient_data to indicate that it can (and maybe will) be reopen in future. This bug needs customer request to continue.