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

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



* Joost Kooij said:
> Hi,
> 
> On Fri, 22 Oct 1999, Anthony Towns wrote:
> 
> > Then the Single Unix Specification is broken, and we shouldn't follow
> > it. Seriously, -e and -n are expected features of echo on GNU/Linux
> > systems, no matter what the Single Unix Spec might or might not say.
> 
> In any case we need some standardisation on "echo" behaviour.
> - should echo understand options?
yes

> - should echo default to interpret escaped characters?
no

> - what escape characters are there and what is their interpretation?
man echo(1) - these escapes should be supported.
  
> > Dropping them shortly before freeze seems an insane thing to do too,
> > fwiw.
> 
> Can achieving consistency across all echo implementations be harmful to
> the pending release?
Of course! Set /bin/sh to /bin/ash and simply reboot your potato - you will
see how many startup scripts are showing "-n" at the start of the line. 

marek

Attachment: pgpWCv7p7riX0.pgp
Description: PGP signature


Reply to: