Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Apr 1999 16:10:03 +0930
From:      Greg Lehey <grog@lemis.com>
To:        Alfred Perlstein <bright@rush.net>, advocacy@FreeBSD.ORG
Subject:   Re: You can take my source.  (fwd)
Message-ID:  <19990420161003.Y40482@lemis.com>
In-Reply-To: <Pine.BSF.3.96.990420015239.11384G-100000@cygnus.rush.net>; from Alfred Perlstein on Tue, Apr 20, 1999 at 01:53:17AM -0500
References:  <Pine.BSF.3.96.990420015239.11384G-100000@cygnus.rush.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 20 April 1999 at  1:53:17 -0500, Alfred Perlstein wrote:
>
>  * (c) UNIX System Laboratories, Inc.
>  * All or some portions of this file are derived from material licensed
>  * to the University of California by American Telephone and Telegraph
>  * Co. or Unix System Laboratories, Inc. and are reproduced herein with
>  * the permission of UNIX System Laboratories, Inc.
>
> Am i doing my part?  :)

I'm not sure.  I would think you could have chosen a better example.
If you have really sent this to Microsoft, I think you should at least
retract your statement.

Greg

> ---------- Forwarded message ----------
> Date: Tue, 20 Apr 1999 01:52:08 -0500 (EST)
> From: Alfred Perlstein <bright@rush.net>
> To: flux@microsoft.com
> Subject: You can take my source.
>
>
> In re: http://www.microsoft.com/mind/0599/flux/flux0599.htm
>
> I think you need to take into account that not all "free software"
> is copylefted or 'GPL'
>
> You conviently neglect to mention (as most people do) the BSD license.
>
> The BSD license allows for closed source swallowing of the code
> it protects, however makes two stipulations:
>
> a) credit is given somehow (redistributed source must retain the
>    copyright)
> b) you can't hold the author liable for the program's behavior,
>    (similar to what EVERY piece of commercial software out there
>    makes you sign an agreement on)
>
> here is a sample of the BSD "open source" license:
>
> /*
>  * Copyright (c) 1982, 1986, 1989, 1991, 1993
>  *      The Regents of the University of California.  All rights reserved.
>  * (c) UNIX System Laboratories, Inc.
>  * All or some portions of this file are derived from material licensed
>  * to the University of California by American Telephone and Telegraph
>  * Co. or Unix System Laboratories, Inc. and are reproduced herein with
>  * the permission of UNIX System Laboratories, Inc.
>  *
>  * Redistribution and use in source and binary forms, with or without
>  * modification, are permitted provided that the following conditions
>  * are met:
>  * 1. Redistributions of source code must retain the above copyright
>  *    notice, this list of conditions and the following disclaimer.
>  * 2. Redistributions in binary form must reproduce the above copyright
>  *    notice, this list of conditions and the following disclaimer in the
>  *    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.
>  * 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.
>  *
>  * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
>  * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
>  * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
>  * ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
>  * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
>  * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
>  * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
>  * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
>  * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
>  * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
>  * SUCH DAMAGE.
>  *
>  *      @(#)kern_exit.c 8.7 (Berkeley) 2/12/94
>  * $Id: kern_exit.c,v 1.78 1999/04/17 08:36:04 peter Exp $
>  */
>
> Several high performance appliances are based on BSD code with BSD
> licensing, (NetAPP, Whistle's "Interjet", cisco, BSDI's bsd/os)
>
> By lumping all free software into one catagory you do the BSD community
> a big disservice, please do more research next time.
>
> You can start at http://www.freebsd.org, http://www.netbsd.org,
> http://www.openbsd.org
>
> I also have to say that your prediction that open source will doom the
> software industry is absurd.  Just think about how much more in R&D
> (the most expensive part of making software) is spent because companies
> are afraid to share code amongst themselves?
>
> I have nothing against propriatary software when it works and has all
> the features I need, but when something trully needs fixing it's
> a godsend to have source availble.
>
> Wouldn't it be nice to get emails with patches to fix bugs in Windows
> rather than call after call, after call for support?
>
> Oh, wait... I just remeber, you guys are now 100% pay per incident....
>
> *sigh*
>
> -Alfred Perlstein
>
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-advocacy" in the body of the message

--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-advocacy" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990420161003.Y40482>