Date: Mon, 29 Apr 2019 00:40:42 -0500 From: Benjamin Kaduk <kaduk@mit.edu> To: James Larrowe <larrowe.semaj11@gmail.com> Cc: freebsd-doc@freebsd.org Subject: Re: Incorrect information Message-ID: <20190429054042.GL60332@kduck.mit.edu> In-Reply-To: <CAEfvv4%2BQb3Z-h_pj_LkO2wmDnrN6_3ACjYZNRKghxzcqg_%2BjDA@mail.gmail.com> References: <CAEfvv4%2BQb3Z-h_pj_LkO2wmDnrN6_3ACjYZNRKghxzcqg_%2BjDA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi James, On Wed, Apr 24, 2019 at 07:50:47PM -0400, James Larrowe wrote: > This page > <https://www.freebsd.org/doc/en_US.ISO8859-1/articles/bsdl-gpl/origins-lgpl.html>; > contains > invalid information. The correct version is included below. Perhaps you could say a bit more about what motivates the changes and why you believe they are more correct than the current text at the location you linked to? Clarifying that Linux is under GPLv2 is relatively straightforward, and adding links and shuffling text around are editorial changes, of course, but I'm not sure I can explain the changes in the final paragraph in the same way you intended. Thanks, Ben > While the commercial Unix wars raged, the Linux kernel was developed as a > PC Unix clone. Linus Torvalds credits the existence of the GNU C compiler > and the associated GNU tools for the existence of Linux. He put the Linux > kernel under the GPLv2. > > Remember that the GPL requires anything that statically links to any code > under the GPL also be placed under the GPL. The source for this code must > thus be made available to the user of the program. Pressure to put > proprietary applications on Linux became overwhelming. Such applications > often must link with system libraries. This resulted in a modified version > of the GPL called the LGPL > <http://www.opensource.org/licenses/lgpl-license.php>; ("Library", since > renamed to "Lesser", GPL). The LGPL allows proprietary code to be linked to > the GNU C library, glibc. Dynamic linking is not considered a violation of > the LGPL. You do not have to release the source to code which has been > dynamically linked to an LGPLed library. > > If you statically link an application with glibc, such as is often required > in embedded systems, either the source or linkable object files must be > released. Both the GPL and LGPL require any modifications to the code > directly under the license to be released. > _______________________________________________ > freebsd-doc@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190429054042.GL60332>