[opensuse] SCO is toast... Novell go get em


http://www.groklaw.net/article.php?story=20061129165103775

Well, it looks like SCO isn't going to get to use their *evidence* because de
judge has slapped them hard with a devastating ruling... basically upholding
the lower court's ruling that a sanction is warranted because SCO willfully
violated discovery rules. ooops, SCO is toast, and Groklaw is vindicated.

Go get em Novell... I'm rooting for you ! (trial coming up)

... and the good news is, you're going to have some new bucks to pursue the
case--- from the M$ deal. cool~ huh?

Ok Suse fans I have a very serious question for yous guys (and please don't
tell me its off topic, cause it aint, so stay in your chair) .... I want to
know who puts code into the kernel... please don't laugh... I'm serious. In
other words, how in the world can SCO (or anybody else) accuse IBM (as a sole
entity) of placing anything willfully into the kernel, when the kernel is not
controlled by IBM, and when the kernel is contributed to from kernel
developers world-wide...??? How much of the kernel comes from Novell? How
much from Shuttleworths folks..??? how much from Redhat...oooops, I mean
IBM?? yeah, right....

Look, either the kernel has System V code in it (copyright protected, or
patented, or both) or it doesn't. This shouldn't be about discovery rules in
a court of law for crying out loud. Either copyrighted code is in the kernel
or not, and if so why can't SCO prevail??? (they shouldn't and I don't want
them to, just a hypothetical question--)

But that is not my real question... my real question is this: How hard would
it be to pull M$ hooks out of the kernel (once they're in there) if and when
they get discovered a year from now... ? ha-uummm??? Would it take a court
order? ---years of litigation? you know... discovery, summary judgment
petitions, rules and thousands of pages of B$ .... and all the time M$ has
hooks into the kernel...

Let's make sure from the top that that does not happen... please?





--
Kind regards,

M Harris <><
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

Relevant Pages

  • Re: CRN is Outta Their Tree--DARL MCBRIDE?
    ... >>Linux kernel. ... SCO has gone much further, ... >>went into Linux is a kernel for everybody, but SCO wants Linux all to ... >What I DON'T understand is why the big deal about someone making money from something ...
    (comp.unix.sco.misc)
  • Re: [OT] Does this mean that IP was proven on the SCO case?
    ... were all developed by IBM or companies that IBM bought ). ... license Unix belongs to SCO. ... Apparently at least one was a Unix kernel hacker: ...
    (RedHat)
  • Re: [opensuse] SCO is toast... Novell go get em
    ... upholding the lower court's ruling that a sanction is warranted because SCO ... want to know who puts code into the kernel... ... This shouldn't be about discovery rules ... Linus has worked for company in the past and didn't lean the kernel towards ...
    (SuSE)
  • Re: more files with licenses that arent GPL-compatible
    ... > license such code, any license that appears to be associated with it ... Your argument applies to the SCO case because their code (if there is ... whatever else the GPL requires; ... they'll try to argue that they didn't know the kernel was covered by the ...
    (Linux-Kernel)
  • Re: Transferring SCO Drive to Another Server
    ... Transferring SCO Drive to Another Server ... Or does it absolutely refuse to boot, ... > somehow get this data off the drive (as i stated, since the kernel is not ... Sounds like you will be able to use tcp/ip just fine. ...
    (comp.unix.sco.misc)