Carl Lowenstein wrote:
On 10/14/05, David M. Cook <[EMAIL PROTECTED]> wrote:
#!/bin/sh
Stylistically, I recommend:
#!/bin/env sh
or, more usually,
#!/usr/bin/env sh
unless this is an actual boot script. That way "sh" is reflected from
your current environment rather than some funky hybrid environment that
you then have to painstakingly debug.
Similarly, I always use:
#!/usr/bin/env perl
#!/usr/bin/env python
to avoid tying myself to a specific installation or version.
Couple of comments:
Shouldn't your script use fully qualified paths for commands it
invokes, or else set $PATH to fit your environment?
A fully qualified PATH or a specifically set path makes the script
completely useless for a different user, a different Linux or a
different OS.
Why in the world would you want to completely prevent the use of this
script in a different environment?
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
