Stephane CHAZELAS <[EMAIL PROTECTED]> writes: >It's true it was vague and misleading,
>/bin is not the standard place to look for "sh" as far as the >"POSIX" standard is concerned. That doesn't mean that standard >commands (POSIX or not) cannot be found in /bin. But /bin/sh has >been made a non-standard place for "sh". It's the "legacy" >place. Those commands that have not undergone non-backward >compatible changes with POSIX can still be found in /bin, the >others are to be found in /usr/xpg<x>/bin (for the standard >versions). The proper place is "`getconf PATH`". POSIX doesn't list any pathnames. Of course, the problem is then "where did getconf come from?". Casper -- Expressed in this posting are my opinions. They are in no way related to opinions held by my employer, Sun Microsystems. Statements on Sun products included here are not gospel and may be fiction rather than truth. -- http://mail.python.org/mailman/listinfo/python-list
