Re: Netscape helpers, or replacing /bin/sh
On 6 Jan 1998, Mark Montague wrote:
> I had the same problem and ended up replacing sh with bash 1.14.5(1),
> which I had lying around from an old slackware backup or something. I
> don't think this is a good solution, though.
>
> I saw some old discussion claiming that this is a netscape bug, but
> after further research, I think it's really a bash bug... run from
> tcsh, the command
>
> bash -c '( ( echo foo ) ; echo bar )'
>
> produces the expected
>
> foo
> bar
>
> output, while
>
> bash -c '(( echo foo ) ; echo bar )'
>
> says
>
> bash: -c: line 1: missing closing `)' for arithmetic expression
> bash: -c: line 1: syntax error near unexpected token `;'
> bash: -c: line 1: `(( echo foo ) ; echo bar )'
>
> Under HPUX 9.05 and 10.20, OSF1 v3.0, IRIX 6.3, SunOS 5.5.1, SunOS
> 4.1.4, and AIX 2.3 (? AIX uname is weird), the command
>
> sh -c '(( echo foo ) ; echo bar )'
>
> produces
>
> foo
> bar
>
> so I think this is a bash bug, and a Debian bug if sh is to be a link
> to bash. Someone claimed earlier on debian-user that bash's behavior
> is correct, but it seems like a goal of bash is to be compatible with
> sh. I don't know what the sh specs say about such things, but this
> seems to be non-standard with respect to sh on every system I've
> tried.
>
> I'm cc'ing this to gnu.bash.bugs, so I'll mention that Debian GNU
> linux 1.3.1 exhibits this bug on i386 systems, which is bash
> v2.00.0(1), according to bash -version. bash v.1.14.5(1) does not have
> the problem.
>
> Of course, it's probably also a bug that this sh code is hard-compiled
> into netscape, but I think that's secondary.
The bug is already known and fixed by bash 2.01, which is provided in the
hamm (unstable) section of the Debian archive. However, bash is linked
against libc6, so you'll need to read http://www.gate.net/~storm/FAQ/
for tips on how to upgrade.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: