Roland Mainz wrote:
>>> The integration into OS/Net is a requirement for the
>>> "migration".
>> Again, why? I don't see why the ksh93 must be in OS/Net to someday deliver
>> the
>> file /usr/bin/ksh.
>
> Why isn't /sbin/sh then in /usr/sfw/bin/ ? Or /usr/bin/csh ? What about
> /usr/bin/bc ?
Because those are covered by the compatibility guarantee. /usr/sfw was
intended as the "Use these at your own risk because they can change
incompatibily" directory, but is now deprecated. That's irrelevant to the
question though - ON vs. SFW is only about where software is built, not
where it is delivered. SFW components can be installed in /usr/bin or other
places as needed.
> An integration into SFW would make it FAR more difficult to convince other
> consolitations to use it and a replacement of /usr/bin/ksh will likely
> become IMPOSSIBLE.
Why? We all use lots of things from SFW already in the other consolidations.
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
