Bug 6768

Summary: /bin/echo does not process escape char \n
Product: [Retired] Red Hat Linux Reporter: jcassell
Component: bashAssignee: Cristian Gafton <gafton>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: jcassell
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
URL: http://www.resonate.com
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-11-09 16:27:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description jcassell 1999-11-05 23:24:52 UTC
/bin/echo and echo no longer interpret the newline escape
character embedded in a string. E.G.

TMP="This is some text"
TMP=${TMP}"\nwith a newline in the middle"

/bin/echo ${TMP}

This code work fine in 6.0 and other flavors of unix:

This is some text
with a newline in the middle

but in RH 6.1 this is the output:

This is some text\nwith a newline in the middle

This bug has cost us a lot of time and money! What are you
guys smoking over there?! (sorry)

Comment 1 jcassell 1999-11-08 20:16:59 UTC
BTW, I neglected to mention, the bug-like echo behavior is exhibited
in a Bourne shell script - i.e. #!/bin/sh.

Comment 2 Bill Nottingham 1999-11-09 16:27:59 UTC
*** This bug has been marked as a duplicate of 6498 ***