by homeworld.cygnus.com with SMTP; 29 Nov 1998 16:14:22 -0000
	by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id LAA00567;
	Sun, 29 Nov 1998 11:14:12 -0500 (EST)
	(envelope-from adrian@lorax.ubergeeks.com)
Date: Sun, 29 Nov 1998 11:14:12 -0500 (EST)
From: ADRIAN Filipi-Martin <adrian@ubergeeks.com>
Reply-To: Adrian Filipi-Martin <adrian@ubergeeks.com>
To: Greg Lehey <grog@lemis.com>
cc: netbsd-advocacy@NetBSD.ORG,
        FreeBSD advocacy list <FreeBSD-advocacy@FreeBSD.ORG>,
        advocacy@openbsd.org
Subject: Re: Merging Net/Free/Open-BSD together against Linux
In-Reply-To: <19981127190855.A468@freebie.lemis.com>
Message-ID: <Pine.BSF.3.96.981129110831.388C-100000@lorax.ubergeeks.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi folks,

	Someone made the point on this thread a few days ago about there
being incompatable copyrights for the three non-commercial BSD's and that
each group has slightly different adgendae.

	Well, this is apoint to seriously look into if a /usr unification
is undertaken.  Below are the diffs for the COPYRIGHT files found on each
of the OS's.  Note how small the differences are.  NetBSD/FreeBSD hardly
differ at all.  OpenBSD differes form the others because it still seems to
use the Net/2 copyright.  If they still use Net/2 source, it would
generally need to be updated to the BSD-Lite versions.  (Of course
including any OpenBSD improvements.)

	In summary, I do not think the copyrights in general will be a
problem.  If there are files with special additionaly copyrights, then
they are to be delt with specially.  It's that simple. 

	Adrian
--
[ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ]

--- COPYRIGHT.freebsd	Sat Nov 28 13:41:52 1998
+++ COPYRIGHT.netbsd	Sat Nov 28 13:47:13 1998
@@ -1,3 +1,4 @@
+#	$NetBSD: COPYRIGHT,v 1.2 1997/02/15 10:02:07 mikel Exp $
 #	@(#)COPYRIGHT	8.2 (Berkeley) 3/21/94
 
 All of the documentation and software included in the 4.4BSD and 4.4BSD-Lite

--- COPYRIGHT.netbsd	Sat Nov 28 13:47:13 1998
+++ COPYRIGHT.openbsd	Wed Oct 18 04:44:22 1995
@@ -1,11 +1,11 @@
-#	$NetBSD: COPYRIGHT,v 1.2 1997/02/15 10:02:07 mikel Exp $
-#	@(#)COPYRIGHT	8.2 (Berkeley) 3/21/94
+#	@(#)COPYRIGHT	5.1 (Berkeley) 7/1/91
 
-All of the documentation and software included in the 4.4BSD and 4.4BSD-Lite
-Releases is copyrighted by The Regents of the University of California.
+All of the documentation and software included in the second BSD Networking
+Software Release is copyrighted by The Regents of the University of California.
 
-Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
-	The Regents of the University of California.  All rights reserved.
+Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991 The Regents of the
+University of California.
+All rights reserved.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions
@@ -17,8 +17,8 @@
    documentation and/or other materials provided with the distribution.
 3. All advertising materials mentioning features or use of this software
    must display the following acknowledgement:
-This product includes software developed by the University of
-California, Berkeley and its contributors.
+	This product includes software developed by the University of
+	California, Berkeley and its contributors.
 4. Neither the name of the University nor the names of its contributors
    may be used to endorse or promote products derived from this software
    without specific prior written permission.
@@ -59,7 +59,10 @@
 Suite 500, Washington, DC 20001-2178.  The developmental work of
 Programming Language C was completed by the X3J11 Technical Committee.
 
-The views and conclusions contained in the software and documentation are
-those of the authors and should not be interpreted as representing official
-policies, either expressed or implied, of the Regents of the University
-of California.
+Portions of the manual reflect system enhancements made at Berkeley and
+sponsored in part by the Defense Advanced Research Projects Agency (DoD),
+Arpa Order No. 4871 monitored by the Naval Electronics Systems Command
+under contract No. N00039-84-C-0089.  The views and conclusions contained
+in these documents are those of the authors and should not be interpreted
+as representing official policies, either expressed or implied, of the
+Defense Research Projects Agency or of the US Government.