[NTLUG:Discuss] SCO sues IBM over UNIX IP in Linux

Chris Cox cjcox at acm.org
Fri Mar 7 18:07:54 CST 2003


I had to respond since publically SCO has now sicked their
spin wizards on trying to dig them out of a pit by stating
vehemently that the lawsuit IS NOT ABOUT LINUX.

Since we know I'm not opinionated :-) here's my take, with some
of the more anti-Linux points from SCO's brief:

  82.          Linux started as a hobby project of a 19-year old student.
               Linux has evolved through bits and pieces of various
               contributions by numerous software developers using single
               processor computers.  Virtually none of these software
               developers and hobbyists had access to 

               enterprise-scale equipment and testing facilities for
               Linux development.  Without access to such equipment,
               facilities, sophisticated methods, concepts and
               coordinated know-how, it would be difficult or impossible
               for the Linux development community to create a
               grade of Linux adequate for enterprise use.

Ok... this is probably the only argument that has some validity.
It's based on the assumption (a weak one) that Linux developers
would not be able to put together the resources necessary to
actually obtiain high-end computing equipment to test against
without help from large corporations... of course, SCO would
like for you to believe that it is primarily ONE corporation,
IBM... belittling itself, SCO, to I suppose a SMALL pathetic,
perhaps desparate corporation without the power to help move Linux
forward in any way shape or form.


83.         As long as the Linux development process remained
             uncoordinated and random, it posed little or no threat to
             SCO, or to other UNIX vendors, for at least two major
             reasons: (a) Linux quality was inadequate since it was not
             developed and tested in coordination for enterprise use and
             (b) enterprise customer acceptance was non-existent because
             Linux was viewed by enterprise customers as a “fringe”
             software product.

SCO here states clearly that community software is "uncoordinated
and random" and therefore incapable of developing anything that
could possibly be as good or even relatively close to being as good
as Unix.

Also we learn that free software developers are incapable of
producing good quality software.

Ulitmately leading to the "fact" that the enterprise will reject
Linux strictly as a "fringe" product.

Well... I can smell the mj from here on this one.  What?!!


84.         Prior to IBM’s involvement, Linux was the software
             equivalent of a bicycle.  UNIX was the software equivalent
             of a luxury car.  To make Linux of necessary quality for use
             by enterprise customers, it must be re-designed so that
             Linux also becomes the software equivalent of a luxury car.
             This re-design is not technologically feasible or even
             possible at the enterprise level without (1) a high degree
             of design coordination, (2) access to expensive and
             sophisticated design and testing equipment; (3) access to
             UNIX code, methods and concepts; (4) UNIX architectural
             experience; and (5) a very significant financial investment.

Bicycle?  If Linux is a bicycle, I can guarantee, as a LONG time
developer of software under SCO's expensive excuse for an OS (take
any of their incompatible offerings... I can tell that SCO today IS
NOT the SCO of yesterday... this new company grew out of the garbage
heap and it stinks)... what was I saying... oh yes... if Linux is
a bicycle, SCO is a Big Wheel.  I don't about your experience with
the Big Wheel... but I remember large holes in plastic tires.

Like so many of their Big Wheel bretheren, AIX included btw...
it has many shortcomings and holes.  I can tell you with utmost
confidence that given a choice of hacking Linux and SCO Unix,
I'll bet I can hack SCO faster.

So again, we see that it is IMPOSSIBLE for you (since many of you
are developers) to produce software outside of your own Big Wheel
company because you simply lack the understanding, resources,
philosophy and money to do anything useful.

Sure am glad this isn't about Linux!!  Aren't you??

85.         For example, Linux is currently capable of coordinating the
             simultaneous performance of 4 computer processors.  UNIX, on
             the other hand, commonly links 16 processors and can
             successfully link up to 32 processors for simultaneous
             operation.  This difference in memory management performance
             is very significant to enterprise customers who need
             extremely high computing capabilities for complex tasks.
             The ability to accomplish this task successfully has taken
             AT&T, Novell and SCO at least 20 years, with access to
             expensive equipment for design and testing, well-trained
             UNIX engineers and a wealth of experience in UNIX methods
             and  concepts.

What the mislead SCO "professional" is saying is that 4 processors
is the most Linux can handle... of course anyone with a clue realize
that that's mainly referring to the ugly i386 architecture.

I'm sure the SGI boys will be the next people that SCO will sue on this
(of course they'll be attacking SGI and not the bicycle known as Linux).

So this one they have to prove.  They're saying that ALL of the
advancements in Linux that make it work on more than 4 processors
were STOLEN from Unix.  Myself, I don't want the plastic wheels,
I'd like something better.  Everything I've seen in Linux leads
me to believe that engineers are taking the ideas that their
Big Wheel companies would not listen to and they are implementing
them inside of Linux.  Now if SCO want their engineers, since
believe it or not, not everyone at SCO is as stupid as their
executive staff, to not work on Linux... fine, that's a corporate
policy they can dictate to their employees.

86.         It is not possible for Linux to rapidly reach UNIX
             performance standards for complete enterprise functionality
             without the misappropriation of UNIX code, methods or
             concepts to achieve such performance, and coordination by a
             larger developer, such as IBM.

Finally, IT IS NOT POSSIBLE FOR LINUX TO RAPIDLY REACH UNIX PERFORMANCE
STANDARDS FOR COMPLETE ENTERPRISE FUNCTIONALITY WITHOUT stealing from
Unix source code.... yep... it doesn't get plainer than that.

But let's not stop there... even if you had the Unix code... you
(the Linux developer) might be too stupid to do anything with it because
you lack THE METHODS AND CONCEPTS TO ACHIEVE SUCH PERFORMANCE mainly
because you LACK THE COORDINATION of a larger developer... IBM.  Ok..
I put more spin on that than what they actually said.. but still...
come on!!

Whew!!





More information about the Discuss mailing list