RE: Additional clauses to GPL in network drivers

[David Schwartz]

> "David Schwartz" <davids@xxxxxxxxxxxxx> writes:

> > 	It occurs to me that it might not be a bad idea to have a
> > short blurb that
> > could be included in individual files that clarifies that the
> > file is part
> > of a GPL'd distribution but that's clear that it doesn't impose any
> > additional restrictions. Here's a stab at such a notice just
> > off the top of
> > my head:

> [snip]
>
> I don't understand the desire for a notice that is clearly redundant.
> Due to the nature of the GPL (version 1 or 2), licensing an entire work
> under it is exactly equivalent to licensing all of the component parts
> individually under it.

	It is definitely redundant. The idea is that if a portion of the
distribution ever winds up somewhere, the terms are still clear. For
example, one often finds modified header files or implementation files
available that don't contain a copy of the GPL or, for that matter, any
indication that the files included are covered by the GPL.

	For this reason, I think it makes sense for files to carry some indication
that they are covered by the GPL. Look, for example, at
ftp://ftp.scyld.com/pub/network/tulip.c

	If this file is to be made available for download by itself, it must
contain some notice that it is covered by the GPL. The current notice,
however, is broken:

	This software may be used and distributed according to the terms of
	the GNU General Public License (GPL), incorporated herein by reference.
	Drivers based on or derived from this code fall under the GPL and must
	retain the authorship, copyright and license notice.  This file is not
	a complete program and may only be used when the entire operating
	system is licensed under the GPL.

	So I'm suggesting a fixed notice that could replace the broken notice.

	DS


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/