The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: j@cnb.uam.es (J. R. Valverde)
Subject: [TUHS] Sad news from IBM...
Date: Mon, 9 May 2005 10:41:10 +0200	[thread overview]
Message-ID: <20050509104110.76e8cfe3.j@cnb.uam.es> (raw)
In-Reply-To: <200505012021.50557.wes.parish@paradise.net.nz>

I was reading Groklaw yesterday night when I came across this. It is a
very sad thought to know that possibly tons of old/ancient code is being
dumped in the trash bin.

More so now since the advent of software patents: it may become very
difficult to avoid a patent on a re-invention of the wheel if previous
knowledge has been dumped.

OK, the quote. It is from "the Todd Shaughnessy affidavit [PDF] from IBM 
that Magistrate Judge Brooke Wells requested they file when they turned 
over all the code and paperwork to SCO":

	28. As I have noted above, IBM does not maintain revision control 
	information for AIX source code pre-dating 1991. To the extent that 
	any code for the AIX operating system (that did not duplicate the 
	code already being produced in CMVC) was found during the search 
	described in Paragraph 26-27 above, it was produced. Paragraphs 
	29-31 below describe additional search efforts IBM undertook to 
	locate pre-1991 versions of AIX code. No versions of AIX pre-dating 
	1991 were found.

	29. In the 1980s and early 1990s, IBM prepared vital records backups 
	of AIX source code and transferred them to a remote storage location. 
	At some point in the 1990s, the AIX vital records tapes were transferred 
	to Austin, Texas. In late 2000, the tapes were determined to be obsolete, 
	and were not retained.

	30. The AIX development organization contacted other IBM employees who 
	were known or believed to have been involved with the development or 
	product release of AIX versions prior to 1991. In addition, IBM 
	managers and attorneys asked current members of the AIX development 
	organization whether they were aware of the location of pre-1991 
	releases of AIX source code. No one asked was aware of any remaining 
	copies of pre-1991 AIX source code.

Perhaps we should do something to raise awareness about the relevance of 
legacy (not only UNIX) source code. And in any case, it is a pity that all
that historical information had been lost forever.

I have always complained about this, and consider it the biggest drawback of
closed proprietary source code: it is OK that law protects developer interests 
with the goal of promoting innovation and the public benefit at large. But it
is a lose for everybody whenever any such "protected" code is dumped into the
bin banning anyone else from further benefitting from or exploiting it, and 
opening the road for opportunists to claim they "newly invented" it.

Sic. Sigh.
				j
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20050509/167fc183/attachment.sig>


      reply	other threads:[~2005-05-09  8:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29 17:59 [TUHS] Mention TUHS in Linux Magazine (US)? Carl Lowenstein
2005-04-29 19:10 ` Jerry Peek
2005-04-30  1:19   ` Kurt Wall
2005-04-30  7:31 ` Wesley Parish
2005-04-30 11:35   ` Tim Shoppa
2005-04-30 18:28   ` Jerry Peek
2005-05-01  8:21     ` Wesley Parish
2005-05-09  8:41       ` J. R. Valverde [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050509104110.76e8cfe3.j@cnb.uam.es \
    --to=j@cnb.uam.es \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).