Roland Mainz writes: > Ok... back to the tracks... > ... if I recall the discussion about the /usr/gnu/bin/ ARC case > correctly GNU commands need to reside in /usr/gnu/bin/ if their location > in /usr/bin/ is "disputed".
Correct. > And I am "disputing" that place now for the > "stat" and "readlink" builtins (and for "open", "close", "poll" which > were explicitly developed for the ksh93-integration project on Sun's > request (there aren't matching GNU tools for these right now but I am > listing them for completeness...)) - claws raised and ready to fight... I think the ship has sailed. The first and simplest option available at this point would be to try to convince the project team for 2007/048 (Stephen Hahn seems to be the right contact here) to alter or withdraw those components for which you see a conflict. Failing that (and you should at least try that first), the right answer is to appeal that previous decision to ARC chairs. I think we can probably drum up the required support if that's necessary. The way I read it, though, I don't see a conflict here under the original /usr/gnu case. Nothing else actually *delivers* those things to /usr/bin, so there's no conflict, and they do not need to be renamed. The "conflict" is only in ksh93's peculiar use of builtins and path bindings. I don't think the original /usr/gnu case can be construed to mean that the ARC intended to rope off all names in /usr/bin that may in the future conflict with ksh93 built-in functions. That seems like an extreme answer, and quite unhelpful to all of the other shells. -- James Carlson, Solaris Networking <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
