Re: Bugs in bash (was: Release-critical Bugreport)
- To: firstname.lastname@example.org
- Subject: Re: Bugs in bash (was: Release-critical Bugreport)
- From: Joel Klecker <email@example.com>
- Date: Sat, 29 May 1999 16:05:50 -0700
- Message-id: <firstname.lastname@example.org>
- In-reply-to: <19990529135212.A19818@molehole>
- References: <19990528001503.A9598@master.debian.org> <19990529084332.B1606@portaloo.> <19990529120021.A19542@molehole> <19990529182254.A1584@portaloo.> <19990529135212.A19818@molehole>
At 13:52 -0500 1999-05-29, Steve Greenland wrote:
This comes up every 6 months or so and inevitably devolves into a huge
flame war. The general consensus seems to be:
1. /bin/sh must be a POSIX compliant shell.
2. Any script that says "#!/bin/sh" but uses bash-specific constructs
has a bug in it.
3. /bin/bash must be present.
(The third item seems to be the one that annoys the most people.)
As far as I know, no one has replaced /bin/sh with something besides
bash (ash, for example) *and* reported back sufficiently positive
results to allow us to change the default /bin/sh to something smaller
ash is not POSIX compliant, incidentally. Basically there are two
POSIX shells in Debian, bash and pdksh.
Joel Klecker (aka Espy) Debian GNU/Linux Developer