IBM's Defense Against SCO's Copyright Infringement Claims Continues

07-17-2010

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

IBM's Defense Against SCO's Copyright Infringement Claims Continues - Part 2, as text

Here's Part 2 of the 2006 IBM document Redacted Memorandum in Support of its Motion for Summary Judgment on its Claim for Declaratory Judgment of Non-Infringement [PDF] IBM'S Tenth Counterclaim, as text, the document where IBM presents all the reasons why SCO's claims of copyright infringement in Linux are bogus. If ever SCO or Son of SCO waives a list of allegedly infringed code, this is the document to have on hand.
Part 1 listed the reasons why IBM did nothing wrong, in that it has multiple licenses to use the code, for one thing, and this part continues that argument, but it then focuses on the files that SCO presented to the court, stating point blank that they are not protectable under copyright law. If you are not a programmer, and you see a list of header files allegedly infringed and don't know who is right, this is the document that will explain it all to you.
Just as we thought, SCO sued over essentially nothing at all, or as IBM puts it:

Despite SCO's grandiose description of its alleged evidence of IBM's infringement, it is now clear that SCO does not have (and never has had) any such evidence.

Is that not appalling?

More...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

TCS(1) General Commands Manual TCS(1) NAME
tcs - translate character sets SYNOPSIS
tcs [ -slcv ] [ -f ics ] [ -t ocs ] [ file ... ] DESCRIPTION
Tcs interprets the named file(s) (standard input default) as a stream of characters from the ics character set or format, converts them to runes, and then converts them into a stream of characters from the ocs character set or format on the standard output. The default value for ics and ocs is utf, the UTF encoding described in utf(6). The -l option lists the character sets known to tcs. Processing continues in the face of conversion errors (the -s option prevents reporting of these errors). The -c option forces the output to contain only cor- rectly converted characters; otherwise, 0x80 characters will be substituted for UTF encoding errors and 0xFFFD characters will substituted for unknown characters. The -v option generates various diagnostic and summary information on standard error, or makes the -l output more verbose. Tcs recognizes an ever changing list of character sets. In particular, it supports a variety of Russian and Japanese encodings. Some of the supported encodings are utf The Plan 9 UTF encoding, known by ISO as UTF-8 utf1 The deprecated original UTF encoding from ISO 10646 ascii 7-bit ASCII 8859-1 Latin-1 (Central European) 8859-2 Latin-2 (Czech .. Slovak) 8859-3 Latin-3 (Dutch .. Turkish) 8859-4 Latin-4 (Scandinavian) 8859-5 Part 5 (Cyrillic) 8859-6 Part 6 (Arabic) 8859-7 Part 7 (Greek) 8859-8 Part 8 (Hebrew) 8859-9 Latin-5 (Finnish .. Portuguese) koi8 KOI-8 (GOST 19769-74) jis-kanji ISO 2022-JP ujis EUC-JX: JIS 0208 ms-kanji Microsoft, or Shift-JIS jis (from only) guesses between ISO 2022-JP, EUC or Shift-Jis gb Chinese national standard (GB2312-80) big5 Big 5 (HKU version) unicode Unicode Standard 1.0 tis Thai character set plus ASCII (TIS 620-1986) msdos IBM PC: CP 437 atari Atari-ST character set EXAMPLES
tcs -f 8859-1 Convert 8859-1 (Latin-1) characters into UTF format. tcs -s -f jis Convert characters encoded in one of several shift JIS encodings into UTF format. Unknown Kanji will be converted into 0xFFFD char- acters. tcs -lv Print an up to date list of the supported character sets. SOURCE
/sys/src/cmd/tcs SEE ALSO
ascii(1), rune(2), utf(6). TCS(1)

UNIX and Linux RSS News

IBM's Defense Against SCO's Copyright Infringement Claims Continues - Part 2, as text

LEARN ABOUT DEBIAN

tcs