Table of Contents |
stoplevel
parameter.
Another option is to structure the %INCLUDED% pages so that their title is part of the included text. Remember that a WikiWord will itself be a link, so that will work. You might want to look at this site's home page in raw format for ideas on how a set of seperate pages can be assembled to a single whole, while (mostly) preserving page references. For that matter, simplifying the homepage might not be all bad either
-- KarstenSelf - 11 Jun 2003
Thanks. Having both the included-page title and the navigation sidebar make it easier to navigate for editing.
Just now, I almost started to refactor this part of the discussion, and then held off.
-- NedUlbricht - 14 Jun 2003
See TrillianProject : Old SCO , Old Caldera executives and developers helped in the development of Linux on the IA-64, including linked proof of an Old SCO core developer suppling linux kernel patches.
-- DavidMohring - 13 Jun 2003
GREAT STUFF on the Trillian project. Maybe UnixWare will need to be GPLd too.
Something is becoming clearer - some quotes from an interview with McBride
http://www.informationweek.com/story/showArticle.jhtml?articleID=10300886
"Sun paid more than $100 million to Novell for a Unix royalty buyout and the ability to redistribute the Unix source code in derivative works."
"IBM paid $10 million to buy the rights to an older Unix. It allegedly didn't pay for the rights to bypass the owner of Unix on derivative works."
So it looks like SCO is claiming EVERYTHING IBM has done with AIX to be a Unix derivative. Would IBM have been so silly as to give away all rights to those of its own technologies that IBM decided to put into AIX?
Of course Sun would have a huge incentive to pay a lot for Unix and sign that kind of deal. Around that time, Sun did not have a huge IP portfolio of its own, and Unix was the BASE of Sun's business.
IBM would have no such incentive. Unix started as a very small part of their business, and with a huge pool of its own IP to add to Unix, it didn't need to pay AT&T, if IBM felt that was (paying twice for)/reinventing IBM's own wheels.
So anyway, the story is changed again, and this time the power grab is even wider.
BUT McBride doesn't stop there. He has to do the obligatory threat against Red Hat and dig at Linux.
"The whole concept of getting something for nothing just doesn't hold up."
His current behavior comports admirably to my thesis that they have no case, are bullying and fudding for a settlement, and are getting desperate. I predicted a while back they'd get louder and nastier, the closer they got to having to prove their case. They're right on cue.
Couldn't figure out how to add these to the "complaints / raw documents " section. These are on the right hand sidebar of
http://www.sco.com/ibmlawsuit/.
[snipped - KarstenSelf]
-- SanjeevSharma - 13 Jun 2003
Sanjeev: That is part of the SCOvsIBMReferences page. (I'm trying to keep breaks at sections.) You can view source of this page with the SCOvsIBM?raw=on option (see the "More" link for this and other options) and figure out where it's at. Or if you're editing this page, search for the %INCLUDE% tags. Helps to use a real text editor (I tend to prefer w3m with vim as editor once a page gets past a certain size).
Anyway, I've parked those links for you. Or rather, moved existing links to more appropriate places as the material was already linked here.
-- KarstenSelf - 15 Jun 2003
LOOPHOLE for SCO's barren-cow loophole defense.
SCO is claiming that SCO did not GPL their trade-secret code because that code was supposedly incorporated into Linux without SCO's permission or knowledge. If SCO did not know their secret property was being mixed into Linux under their noses, then SCO could not have GPL'd the alleged code, since GPL requires deliberate GPLing.
Currently, SUN KNOWs that SCO's allegedly stolen code is in Linux. SUN is distributing Linux under GPL. SUN HAS THE RIGHT, by SCO's own mulitple admissions, to release the alleged code any way they see fit.
SUN has, AND CONTINUES TO independent of (allegedly) IBM, and independent of Caldera/SCO, GPL'd SCO's allegedly protected code.
THANKS SCOTT!!!!!! Whatta guy!!
I also wonder how many other licencees of AT&T, Novell, and old SCO have valid license to GPL SysV or SysV derivatives. Sony (they made Unix workstations from MIPS chips, right? or was that NEC?) Hitachi? SGI? HP? INTEL?
-- SanjeevSharma - 17 Jun 2003
Technical point for those familiar with contract law.
It seems SCO's "case" against Linux (if they are ever going to seek Linux licensing fees) is
Topic SCOvsIBMDiscussionArchive . { Edit | Attach | Ref-By | Printable | Diffs | r1.1 | More } |
| Copyright © 2001-2004 by the contributing authors. All material on TWikIWETHEY is the property of the contributing authors. This content may be freely distributed, copied, or modified, with attribution, and this notice. Works are provided AS IS with NO WARRANTY and NO LIABILITY for consequences of use. Ideas, requests, problems regarding TWikIWeThey? Send feedback. |