Well,
"echo -e" tells bash to interpret antislashes in strings.
The ash shell (a very faster shell than bash) does not know this option,
and interpret antislashes by default.
It seems that some bourne shell script in the buildroot use "echo -e".
the problem is, in ubuntu, sh is a symlink to ash.
So, you have the choice :
sudo rm /bin/sh && sudo ln -s /bin/bash /bin/sh
or find the erroneous script and replace the first line #!/bin/sh by
#!/bin/bash
See
++
Sam
Sean Reilly a écrit :
> Hi All,
> Does anyone know why -e is appearing in the modules file and
> interfaces file ? It means that bootup takes forever and interfaces
> don't come up after the first bootup. This is after building from the
> latest gumstix svn repo (1431) so I'm not sure why this is happening.
> Does anyone know how to stop this ? I can fix it by deleting various -e'
> s in conf files but I'd like to stop it at source especially as I'm
> becoming suspicious of all "-e"s I meet such as the "set -e" which
> appears at the start of "/etc/init.d/S30bluetooth"
>
> thanks,
>
> Sean
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>
|