Date: Wed, 18 Apr 2001 23:47:31 -0700 From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: "Kris Kennaway" <kris@obsecurity.org> Cc: "Rahul Siddharthan" <rsidd@physics.iisc.ernet.in>, "David Johnson" <djohnson@acuson.com>, <freebsd-advocacy@FreeBSD.ORG> Subject: RE: Windriver, Slackware and FreeBSD Message-ID: <006601c0c89c$9b9a2dc0$1401a8c0@tedm.placo.com> In-Reply-To: <20010418112830.A36122@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>-----Original Message----- >From: Kris Kennaway [mailto:kris@obsecurity.org] >Sent: Wednesday, April 18, 2001 11:29 AM >To: Ted Mittelstaedt >Cc: Rahul Siddharthan; David Johnson; freebsd-advocacy@FreeBSD.ORG >Subject: Re: Windriver, Slackware and FreeBSD > > >On Wed, Apr 18, 2001 at 08:11:15AM -0700, Ted Mittelstaedt wrote: > >> It used to be that when a company (like Apple) contributed >> code to a UNIX (like BSD) they were allowed to keep their own >> copyright on the code and just have it included in the >> distribution. After the AT&T lawsuit, BSD doesen't allow this >> anymore. If your a company and you want to contribute your >> own copyrighted source to FreeBSD, you can only do this via the >> ports mechanism. (ie: build a port for your stuff) You can not >> get it into the kernel unless you agree to change the copyright >> to give BSD perpetual control over it. > >FreeBSD doesn't require copyright transfer of donated code. > FreeBSD does not use kernel code that carries a copyright that is not BSD-like, ie: a license that basically gives everyone permission to do whatever the hell they want with the code. Actually, the entire BSD licensing thing is getting a bit silly since I don't think that the actual University of California, Berkeley, has paid much attention to FreeBSD or any of the BSD's since they dissolved CSRG. More and more, the term "BSD License" is being used to indicate a license that is unrestrictive, ie: Not GNU, rather than an actual assignment of copyright to the Regents of the University of California, Berkeley. Now, different _applications_ in the distribution are a different matter - in my opinion the C compiler (gcc) is probably one of the biggest problems, kind of like the pink elephant that everyone pretends isn't there. It's a shame because at one time BSD did have it's own C compiler. I don't know if it ever crossed over into the FreeBSD distribution but I've always thought it a shame that we have to depend on GNU software for this task. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com 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?006601c0c89c$9b9a2dc0$1401a8c0>