Return to BSD News archive
Xref: sserve comp.os.linux:34721 comp.os.386bsd.questions:1701 Newsgroups: comp.os.linux,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!usc!elroy.jpl.nasa.gov!decwrl!netcomsv!netcom.com!yci From: adam@netcom.com (Adam J. Richter) Subject: Re: Summary of Linux vs. 386BSD vs. Commercial Unixes Message-ID: <yciC5nK4H.FsG@netcom.com> Sender: yci@netcom.com (Yggdrasil Computing) Organization: Yggdrasil Computing, Incorporated References: <1qo0lq$1hm4@hal.gnu.ai.mit.edu> <1993Apr17.161516.2794@serval.net.wsu.edu> <1993Apr17.175431.25015@coe.montana.edu> Date: Sun, 18 Apr 1993 00:02:41 GMT Lines: 24 In article <1993Apr17.175431.25015@coe.montana.edu> nate@cs.montana.edu (Nate Williams) writes: >And then Linux and the GNU folks will take what 386BSD has done and >restrict it. Now, isn't that nice....... taking my work and restricting >it. I always thought that was awful kind of them. (NOT!) When speaking at SVNet meetings, Bill Jolitz has repeatedly stated that he sees 386BSD as a sort of publicly accessible research vehicle for operating systems. The 386BSD core distribution is not designed for the average end user. Instead, the 386BSD copyright is unrestricted specifically for the purpose of allowing the results of 386BSD to be assimilated into any other operating system project, such as Windows, turnkey BSD distributions or Linux. The public benefit is supposed to come from this assimilation, not unlike the way most unix users now benefit from the Berkeley filesystem and networking work. Assimilating 386BSD software into Linux without Linux having to give up its copyright policy is more than just allowed; it is specifically the point of 386BSD. -- Adam J. Richter Yggdrasil Computing, Incorporated 409 Evelyn Ave., Apt. 312, Albany CA 94706 PO Box 8418, Berkeley CA 94707-8418 (510) 528-3209 (510) 526-7531, fax: (510) 528-8508 adam@netcom.com yggdrasil@netcom.com Another member of the League for Programming Freedom (lpf@uunet.uu.net).