Re: [PATCH] latest ash has broken 'echo' command
On Fri, Oct 22, 1999 at 10:06:04AM +1000, Herbert Xu wrote:
> 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.
Upon closer inspection, the SuS defines the behaviour of an echo *utility*
Therefore, if its a builtin it is no longer a utility, since utilities are
separate.
Myth
Reply to: