For the folks on the project list: in the process of disabling the ksh93 builtins that are incompatible with their Solaris counterparts, Roland has discovered that disabling getconf breaks the test suite. There's been some off-list discussion of how to handle that, mostly focusing on the short-term approach for the initial integration into ON. (More on that in a future mail.)
>>>>> "April" == April Chin <April.Chin at eng.sun.com> writes: April> Yes, the Solaris OS has three versions of getconf-- April> /usr/bin/getconf, /usr/xpg4/bin/getconf and April> /usr/xpg6/bin/getconf. A user who configures his path to conform April> with SUSv2 or SUSv3 will expect to pick up the corresponding April> getconf which will return different values. In ksh93, executing April> getconf with no pathname prefix, just "getconf...", will execute April> the ksh93 getconf built-in which is incompatible with our getconf April> binaries and will not work differently depending on the usr's April> path. Clearly we need to get this resolved before we replace April> /usr/bin/ksh, but I'm not sure what the resolution is. I thought we already had a plan for the general case of builtins, which is that the behavior of the builtin would depend on $PATH? Did I miss something? mike
