Bug 5935 – Possible shell bug

Bug 5935 - Possible shell bug

Summary:	Possible shell bug

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	bash (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Cristian Gafton
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-10-14 01:23 EDT by Clay Jackson
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-10-15 16:08:40 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Clay Jackson 1999-10-14 01:23:22 EDT

After successful (no errors reported) upgrade from RH 6.0
to RH 6.1 -

The following code:
    ECHO="/bin/echo"
    export ECHO
    IFS=`$ECHO " \t\n\c"`
    IFS_OLD="$IFS"
    IFS_TMP="$IFS"
    IFS_NEW=`$ECHO "\t\c"`
returns:
    foo: /bi: No such file or directory

Please tell me what gives!
(This code fragment is from MicroLite's BackupEdge product).

Comment 1 Alan Cox 1999-10-15 16:08:59 EDT

Shell utils 2.0 follows the standard more closely and does not do the
quoting of \ that this script seems to expect. This is correct
standards behaviour now.

The script should probably be using /usr/bin/printf

Note You need to log in before you can comment on or make changes to this bug.