Meta tags:

Headings (most frequently used words):

edit, sgi, code, of, the, navigation, tools, sco, dispute, 2003, contents, background, origin, responds, see, also, references, external, links, menu, personal, namespaces, views, search, contribute, print, export, languages,

Text of the page (most frequently used words):
the (69), code (32), sco (29), linux (19), that (16), this (15), and (12), from (12), sgi (12), unix (12), had (10), was (9), wikipedia (8), edit (8), source (8), not (7), 2003 (7), these (7), been (7), community (6), all (6), also (6), original (6), question (6), references (5), copying (5), copyright (5), system (5), because (5), time (5), which (5), example (5), page (4), links (4), articles (4), retrieved (4), 2009 (4), fragments (4), group (4), any (4), open (4), while (4), already (4), examples (4), about (3), article (3), navigation (3), more (3), contributions (3), categories (3), with (3), june (3), org (3), out (3), one (3), very (3), were (3), versions (3), early (3), other (3), some (3), used (3), present (3), several (3), analyses (3), literal (3), revealed (3), showed (3), dispute (3), sources (3), view (2), contact (2), privacy (2), policy (2), available (2), under (2), terms (2), non (2), use (2), license (2), august (2), 2021 (2), version (2), pdf (2), information (2), upload (2), file (2), changes (2), tools (2), learn (2), contents (2), search (2), talk (2), unsourced (2), statements (2), lacking (2), reliable (2), 2016 (2), disputes (2), https (2), analysis (2), las (2), vegas (2), evidence (2), between (2), external (2), public (2), domain (2), united (2), usl (2), bsdi (2), see (2), small (2), than (2), lines (2), most (2), claim (2), responded (2), letter (2), claims (2), indeed (2), kernel (2), responds (2), did (2), have (2), law (2), either (2), ken (2), wrote (2), free (2), originated (2), its (2), fact (2), derived (2), origin (2), never (2), only (2), infringing (2), pointed (2), removed (2), duplicated (2), functions (2), during (2), illegal (2), them (2), shown (2), into (2), forum (2), background (2), involved (2), novell (2), ibm (2), jump (2), web (2), sep (2), cookie, statement, statistics, developers, mobile, disclaimers, text, additional, may, apply, using, site, you, agree, registered, trademark, profit, organization, wikimedia, foundation, inc, creative, commons, attribution, sharealike, last, edited, utc, add, languages, printable, download, print, export, wikidata, item, cite, permanent, link, special, pages, related, what, here, recent, portal, help, contribute, donate, random, current, events, main, history, read, views, english, namespaces, log, create, account, logged, personal, menu, hidden, 2008, silicon, graphics, index, php, title, sgi_code_dispute_of_2003, oldid, 1037818462, slide, show, smoking, gun, fizzles, unixware, 2002, dear, enthusiasts, cornell, term, states, controversies, together, three, comprised, 200, million, our, overall, notably, appears, found, previously, placed, meaning, doubtful, has, proprietary, case, october, allegations, rich, altmaier, vice, president, software, inadvertently, included, important, required, effectively, means, protected, additionally, both, released, like, allowing, products, clause, bsd, santa, cruz, operation, originally, know, comments, first, appeared, 6th, edition, definitely, written, since, spent, annotating, almost, comment, earlier, editions, possible, contributed, implementation, happened, 1970s, comparison, reveal, substantial, differences, two, creators, acknowledged, thompson, dennis, ritchie, determined, particularly, bad, mainstream, distributions, relative, sparseness, worldwide, installations, combined, limited, makes, chance, actually, encountering, running, slim, within, hours, started, different, results, differ, slightly, they, confirm, could, possibly, does, necessarily, prove, infringement, copyrights, citation, needed, demonstrate, known, name, contributor, quick, existing, atemalloc, held, publicly, alleged, until, people, who, signed, prohibited, revealing, claimed, infringements, are, divided, four, separate, transfers, derivative, works, obfuscation, nda, mgm, grand, conference, allegedly, copyrighted, quickly, debunked, particular, maintainers, stated, before, but, needlessly, analysts, matter, confirmed, infringed, xinuos, groklaw, darl, mcbride, pamela, jones, ralph, yarro, iii, individuals, companies, red, hat, daimlerchrysler, autozone, litigation, scosource, timeline, overview, how, when, remove, template, message, please, improve, adding, jstor, scholar, books, newspapers, news, find, secondary, tertiary, relies, too, much, primary, redirected, encyclopedia, wayback, machine, http, archive, 20220822045827, wiki, sco_and_sgi, timestamps, capture, fail, success, 2023, 2022, aug, jul, 2004, feb, 2026, captures,

Text of the page (random words):
sco sgi code dispute of 2003 wikipedia 31 captures 11 sep 2004 02 feb 2026 jul aug sep 22 2021 2022 2023 success fail about this capture timestamps the wayback machine http web archive org web 20220822045827 https en wikipedia org wiki sco_and_sgi sco sgi code dispute of 2003 from wikipedia the free encyclopedia redirected from sco and sgi jump to navigation jump to search this article relies too much on references to primary sources please improve this by adding secondary or tertiary sources find sources sco sgi code dispute of 2003 news newspapers books scholar jstor june 2016 learn how and when to remove this template message sco linux disputes overview timeline sco and sgi scosource litigation sco v ibm sco v autozone sco v daimlerchrysler sco v novell red hat v sco companies involved sco group ibm novell individuals involved ralph yarro iii pamela jones darl mcbride other united linux usl v bsdi groklaw xinuos v t e during its sco forum conference of 2003 the sco group sco showed several examples of allegedly illegal copying of copyrighted code into linux the open source community quickly debunked most of the examples shown in particular one example showed that code from unix was indeed used in some of sgi s linux contributions the linux maintainers stated that the code in question had in fact already been removed from linux before the example had been revealed not because it was infringing but because the code in question had needlessly duplicated some functions which were already present in linux sgi and other analysts also responded to this matter and confirmed that the code in question had never infringed at all contents 1 background 2 the origin of the code 3 sgi responds 4 see also 5 references 6 external links background edit during sco forum held on august 17 19 2003 at the mgm grand las vegas sco publicly showed several alleged examples of illegal copying of copyright code in linux until that time these examples had only been available to people who signed an nda which had prohibited them from revealing the information shown to them sco claimed the infringements are divided into four separate categories literal copying obfuscation derivative works and non literal transfers the example used by sco to demonstrate literal copying is also known as the atemalloc example while the name of the original contributor was not revealed by sco quick analysis of the code in question pointed to sgi at this time it was also revealed that the code had already been removed from the linux kernel because it duplicated already existing functions within hours the open source community started several different analyses of the infringing code while the results of these analyses differ slightly they all confirm that the code in question was derived from unix code citation needed these analyses also pointed out that while the code could possibly have originated in unix this does not necessarily prove infringement of copyrights the community was determined that this was a particularly bad example because the code in question had never been used in the mainstream distributions of linux and had been present only in the ia 64 version the relative sparseness of worldwide ia 64 installations combined with the limited time in which the code was present in linux makes the chance of actually encountering a system running this code very slim the origin of the code edit while it is possible that the code contributed to linux originated from unix system v its original implementation happened in the early 1970s comparison of the original unix source code and the unix system v source did not reveal any substantial differences between the two in fact dennis ritchie one of the creators of the original versions of unix acknowledged that either he or ken thompson wrote the original code from which the unix system v code is derived so either ken or i wrote it originally i know that the comments that first appeared by the 6th edition were definitely written by me since i spent some time annotating the almost comment free earlier editions this is very important because the original versions of unix did not have any copyright claim in the source code at that time the law required these copyright claims 1 which effectively means the early unix code is not protected by copyright law additionally both santa cruz operation and the sco group released the source code to early versions of unix 2 under a 4 clause bsd like license allowing the use of the source code in other open source products sgi responds edit october 1 2003 sgi responded to sco s allegations in an open letter to the linux community in this letter rich altmaier vice president of software claims that these small code fragments were indeed inadvertently included in the linux kernel all together these three small code fragments comprised no more than 200 lines out of the more than one million lines of our overall contributions to linux notably it appears that most or all of the system v code fragments we found had previously been placed in the public domain meaning it is very doubtful that the sco group has any proprietary claim to these code fragments in any case 3 see also edit sco linux controversies usl v bsdi references edit copyright term and the public domain in the united states cornell 2009 01 01 retrieved 2009 12 04 dear unix enthusiasts pdf 2002 01 23 retrieved 2009 12 04 to the linux community sgi 2003 10 01 retrieved 2009 12 04 external links edit sco s evidence of copying between linux and unixware sco s evidence this smoking gun fizzles out analysis of sco s las vegas slide show retrieved from https en wikipedia org w index php title sco sgi_code_dispute_of_2003 oldid 1037818462 categories sco linux disputes silicon graphics hidden categories articles lacking reliable references from june 2016 all articles lacking reliable references all articles with unsourced statements articles with unsourced statements from june 2008 navigation menu personal tools not logged in talk contributions create account log in namespaces article talk english views read edit view history more search navigation main page contents current events random article about wikipedia contact us donate contribute help learn to edit community portal recent changes upload file tools what links here related changes upload file special pages permanent link page information cite this page wikidata item print export download as pdf printable version languages add links this page was last edited on 8 august 2021 at 22 15 utc text is available under the creative commons attribution sharealike license 3 0 additional terms may apply by using this site you agree to the terms of use and privacy policy wikipedia is a registered trademark of the wikimedia foundation inc a non profit organization privacy policy about wikipedia disclaimers contact wikipedia mobile view developers statistics cookie statement