On Feb 17, 2008 1:56 PM, Jeremy Henty <[EMAIL PROTECTED]> wrote: > On Sun, Feb 17, 2008 at 10:10:13AM -0800, Dan Nicholson wrote: > > On Feb 17, 2008 6:16 AM, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote: > > > > > > You really should get the script from LFS-6.2 or 6.3, and replace > > > ${ECHO} with just "echo" > > > > Using /bin/echo produces the correct result. > > Thanks everyone. I installed the LFS 6.3 console script, added > "ECHO=/bin/echo" near the beginning, rebooted and all is good!
Just to quickly follow up on that. If /bin/sh is bash, then you can use the builtin echo which supports -e. To be POSIX compliant (i.e., using dash as /bin/sh) meant that we had to add a feature test to find out if -e was supported in the builtin echo, falling back to /bin/echo if not. There are other possible solutions for this issue, but that one was the least intrusive I could think of. So, if you're using bash as /bin/sh, then just use ECHO=echo. Using the builtin echo will be less overhead then forking /bin/echo every time a message goes to the screen. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page