Date: Wed, 24 Apr 2019 19:50:47 -0400 From: James Larrowe <larrowe.semaj11@gmail.com> To: freebsd-doc@freebsd.org Subject: Incorrect information Message-ID: <CAEfvv4%2BQb3Z-h_pj_LkO2wmDnrN6_3ACjYZNRKghxzcqg_%2BjDA@mail.gmail.com>
index | next in thread | raw e-mail
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. 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.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAEfvv4%2BQb3Z-h_pj_LkO2wmDnrN6_3ACjYZNRKghxzcqg_%2BjDA>