On 6/6/07, Roland Mainz <roland.mainz at nrubsig.org> wrote: > * Use builtin commands if the shell provides them. For example ksh93s+ > (ksh93, version 's+') delivered with Solaris supports the following > builtins:
This seems to favor the use of never specifying the full path to all of your commands, rather set PATH. Builtins can then be picked up automatically without thinking about it. > chown How does this work? Surely ksh93 doesn't install setuid by default... Does it try to use the builtin then try chown in $PATH if it gets EPERM? > * Using -p" for starting non-interactive shell scipts is AFAIK a NO-OP, > e.g. > -- snip -- > #!/bin/ksh -p > -- snip -- > should be replaced with > -- snip -- > #!/bin/ksh > -- snip -- I've recently been burned by this one. lucreate or luupgrade (I forget which) blew up due to missing -p and having some questionable stuff in the file pointed to by $ENV. Mike -- Mike Gerdts http://mgerdts.blogspot.com/
