Date: Fri, 20 Aug 1999 19:22:15 -0400 (EDT) From: aa8vb@ipass.net To: FreeBSD-gnats-submit@freebsd.org Cc: aa8vb@ipass.net Subject: bin/13274: /bin/sh 'read' command does not work correctly Message-ID: <199908202322.TAA10796@stealth.ipass.net.>
next in thread | raw e-mail | index | archive | help
>Number: 13274
>Category: bin
>Synopsis: /bin/sh 'read' command does not work correctly
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Aug 20 16:30:00 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator: Randall Hopper
>Release: FreeBSD 3.2-RELEASE i386
>Organization:
self
>Environment:
Stock 3.2-RELEASE
>Description:
The "read" command FreeBSD Bourne shell (/bin/sh) does not work
like the Bourne read command on most other major UNIX systems with
regards to continuation line handling. Other UNIXes' Bourne shells
merge lines ending with a trailing '\' character, while FreeBSD's
does not unless a FreeBSD-specific option is specified.
In particular, this breaks Python's 'makesetup' script (used to
build Python extensions) when fed standard Setup scripts because
FreeBSD's Bourne 'read' behavior is different from other UNIXes.
>How-To-Repeat:
Sun Solaris 2.5:
> sh
$ read line
some text here \
more text
$ echo $line
some text here more text
SGI IRIX 6.5.4:
$ read line
some text here \
> more text
$ print $line
some text here more text
DEC UNIX V4.0:
$ read line
some text here \
more text
$ echo $line
some text here more text
Redhat 5.2 Linux / bash:
$ read line
some text here \
more text
$ echo $line
some text here more text
FreeBSD 3.2:
$ read line
some text here \
$ more text
text: No such file or directory
>Fix:
Please fix /bin/sh so that the default behavior of the "read"
command is such that it merges lines ending with a trailing '\'
(i.e. like it behaves now only if -e is specified). Thanks.
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908202322.TAA10796>