Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA2354 ; Mon, 01 Mar 93 10:55:29 EST Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!howland.reston.ans.net!usenet.ins.cwru.edu!odin!chet From: chet@odin.ins.cwru.edu (Chet Ramey) Newsgroups: comp.os.386bsd.questions Subject: Re: 386BSD vs BSDI Date: 27 Feb 1993 19:12:30 GMT Organization: Case Western Reserve University, Cleveland OH (USA) Lines: 25 Message-ID: <1moeeuINNoo1@usenet.INS.CWRU.Edu> References: <HALEY.93Feb23030107@husc11.harvard.edu> <1mdar0INNn5n@usenet.INS.CWRU.Edu> <6407@krafla.rhi.hi.is> <1993Feb25.221456.14935@advtech.uswest.com> NNTP-Posting-Host: odin.ins.cwru.edu >They also say that NET2 was produced by people who themselfs were >"tainted" by prolonged exposure to USL propriatary code. This is >taintamount to saying that these people (including many of the best >minds in the computer industry) are themselfs "USL propriatary", and >any code they produce which is remotely like anything found in unix(*) >belongs to USL. >From a letter sent to the USENIX Association over the signature of Roel Piper (President and CEO of USL): Someone who has been exposed to USL's confidential information has always been required to keep that information in confidence. But that does not mean USL would try to stop people who have seen USL source code from working for a competitor or independently developing competitive software. It merely means that in that job they will not be permitted to use USL's confidential information to create code that is copied or derived from UNIX System source code. And, the issue will normally arise only when, in that job, they produce software substantially similar to UNIX System software. -- ``The use of history as therapy means the corruption of history as history.'' -- Arthur Schlesinger Chet Ramey, Case Western Reserve University Internet: chet@po.CWRU.Edu