SCO's V.4 plans <was: ^3 What ....... Dell UNIX V.4>

[Dick Dunn]

> >SCO has, so far, promised NOT to go with V.4 -- buzzing about in their own
> >separate reality.

> 	As I recall from an SCO presentation at our user group last December,
> their stated inclination is to enhance 3.2 with those components or features
> from V.4 most in demand...

Interesting idea, but could someone explain how this works without giving
you a result which is neither fish nor fowl?  The best example I know of is
long file names in a BSD-like file system; it may well be the single most-
often-requested BSD feature.  But if you create a modified file system with
long file names, it's *going* to be incompatible, no getting around it.  At
that point, you're no longer a V.3.2 system, period.  How do you do this?
Anyone from SCO, or who's heard what SCO claims, want to explain this?

[V.4's approach to the fish/fowl dilemma is to put both seafood and poultry
on the menu, giving you your choice (and letting you pay for both:-) and
even allowing you to have some of each.)
-- 
Dick Dunn     rcd at ico.isc.com -or- ico!rcd       Boulder, CO   (303)449-2870
   ...Mr. Natural says, "Use the right tool for the job."