Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!ncar!ico!rcd From: rcd@ico.isc.com (Dick Dunn) Newsgroups: comp.unix.sysv386 Subject: Re: SCO's V.4 plans Summary: explain how a filename-length change would work? Message-ID: <1990Nov26.194751.24747@ico.isc.com> Date: 26 Nov 90 19:47:51 GMT References: <1990Nov15.225728.16481@cbnewsm.att.com> <152@raysnec.UUCP> Organization: Interactive Systems Corporation, Boulder, CO Lines: 21 > >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@ico.isc.com -or- ico!rcd Boulder, CO (303)449-2870 ...Mr. Natural says, "Use the right tool for the job."