Bug 805459 - Tilda expansion failing in ksh
Summary: Tilda expansion failing in ksh
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: ksh
Version: 5.8
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Michal Hlavinka
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On: 802565
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-21 11:17 UTC by RHEL Program Management
Modified: 2018-11-27 20:22 UTC (History)
10 users (show)

Fixed In Version: ksh-20100621-5.el5_8.1
Doc Type: Bug Fix
Doc Text:
Previously, ksh did not expand the tilde (~) character properly. For example, characters in the tilde prefix were not treated as a login name but as a part of the path and the "No such file or directory" message was displayed. The underlying source code has been modified and tilde expansion now works as expected in such a scenario.
Clone Of:
Environment:
Last Closed: 2012-03-28 11:17:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0432 0 normal SHIPPED_LIVE ksh bug fix update 2012-03-28 15:16:57 UTC

Description RHEL Program Management 2012-03-21 11:17:13 UTC 
This bug has been copied from bug #802565 and has been proposed
to be backported to 5.8 z-stream (EUS).
Comment 6 Eliska Slobodova 2012-03-28 09:50:30 UTC 
    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.
    
    New Contents:
Previously, ksh did not expand the tilde (~) character properly. For example, characters in the tilde prefix were not treated as a login name but as a part of the path and the "No such file or directory" message was displayed. The underlying source code has been modified and tilde expansion now works as expected in such a scenario.
Comment 7 errata-xmlrpc 2012-03-28 11:17:49 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0432.html
Note You need to log in before you can comment on or make changes to this bug.