> > However, our /bin/sh (at least the one in 1.6) doesn't know about
> > "command -V" either... /bin/ksh does though.

"command -V" is also optional anyway....

OTOH I might write the code for it.
(the handling of the 'command' builtin is somewhat painful, all the
variants except -v and -V have to be done inline in the 'find the
executable' path.

Perversions like "PATH=xxx command -V yyy" just make life complicated.

	David

-- 
David Laight: david@l8s.co.uk