Darren J Moffat writes: > Now personally I recommend to people when writing scripts that use a > profile never to depend on $PATH and always fully specify the paths.
A bit off-topic, but I disagree with that. For trivial scripts, littering the code with /foo/bar/baz isn't too horrible, but for non-trivial scripts, it's a distraction and a maintenance hazard: both of which are serious issues that lead to security and reliability problems. Instead, just set PATH at the top (often just /my/stuff:/usr/bin) and drive on. PATH is documented and works. > So in ARC terminology, if this was a full case rather than a fast track > I would be suggesting a TCA (Technical Change Advised) that the builtins > be disabled when running as pfksh93. I'd also be suggesting opinion > Advice that this project team work with the RBAC project team (ie > Casper) to ensure that they don't clash and only one solution is needed. I feel a bit more strongly about this -- nearly TCR. I think that adding a new "pf*" shell that doesn't work right is an attractive nuisance. We should talk about adding that link in the future when we know how to make it work. -- James Carlson, KISS Network <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
