Quote:
Originally Posted by hawhill
The latter. The ":" should be OK, but I guess the interpreter line (first line) in the shell script got corrupted, so it's the interpreter that cannot be found. Touched with a not-that-sophisticated editor, perhaps?
|
The crew that writes BusyBox does a great job of writing tight, compact, code. . . .
But their idea of "descriptive error messages" leaves a bit (no pun intended) to be desired.
I expect that any day now, in their battle against "code bloat" they are going to settle on using just one general purpose error message:
"Command either not recognized or was unable to complete properly."
Or maybe just:
-EPEBKAC
For any and everything that returns an error code.