So far I've been developing on an embedded busybox system. My scripts currently all begin with #!/bin/sh
On my current target board that points to ash. All my scripts are ash-not-bash syntax, and I now want to be able to run them on a Debian system without maintaining 2 versions If I install in a sub-environment, I'd like them to pick up the shell in my sub environment - which could be /myapp/bin/sh - which I can then point to a private copy of ash. What are the rules here ? I notice that I seem to be able to run scripts under busybox which are missing the shbang - does that mean busybox is peering at the file and deciding it's not any kind of exe format it's been equipped to process, and dropping back to treating it as a script? Will other environments be equally flexible, or will they insist on the shbang on scripts? If I don't include a path, but just put #!sh - will the busybox and other shells search for sh on the current path? TVM Confused D _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
