[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [PATCH] latest ash has broken 'echo' command

* Herbert Xu said:
> On Fri, Oct 22, 1999 at 09:59:58AM +1000, Herbert Xu wrote:
> > 
> > Anyway, I think the crux of the matter now is whether a POSIX compliant shell
> > has to have options or not, if they do, I'll change it back.  If they don't,
> > then by our very own policy, a /bin/sh shell script must not use options or
> > escape codes.
> Please note that I am by no means saying that we should do this for potato
> since we may want to change our policy instead and we don't have the time
> for it anyway.
> As for ash, it's not /bin/sh (last I checked bash still linked itself there)
> so you can always use bash.
But the reasons I use ash as /bin/sh are that it's a POSIX shell, which
ensures the basic compatibility with clean sans-bashism scritpts, and that
it's not as bloated as bash which is completely unsuitable as a simple


Attachment: pgptWf1AGX6Dg.pgp
Description: PGP signature

Reply to: