Re: [PATCH] latest ash has broken 'echo' command
David Benson <daveb@idealab.com> writes:
> I'm rather sorry to continue dragging this out,
> but now and then I actually write startup scripts
> so this is relevant...
>
> Is it fair to assume that /bin/echo -n and /bin/echo -e will
> always work?
> [What else *can* you do if /usr isn't necessarily available?]
According to POSIX -e cannot work and -n may work.
printf(1) is to be used instead.
Following your problem printf should be moved from /usr/bin/ to /bin/ .
Sven
--
Sven Rudolph <sr1@sax.de> http://www.sax.de/~sr1/
Reply to: