Cisco Cisco IPICS Dispatch Console Información de licencia

mouse-clicks or menu items--whatever suits your program.

 

You should also get your employer (if you work as a programmer) or your

school, if any, to sign a "copyright disclaimer" for the program, if

necessary.  Here is a sample; alter the names:

 

 Yoyodyne, Inc., hereby disclaims all copyright interest in the program

 `Gnomovision' (which makes passes at compilers) written by James Hacker.

 

 <signature of Ty Coon>, 1 April 1989

 Ty Coon, President of Vice

 

This General Public License does not permit incorporating your program into

proprietary programs.  If your program is a subroutine library, you may

consider it more useful to permit linking proprietary applications with the

library.  If this is what you want to do, use the GNU Library General

Public License instead of this License.

Date:Thu, 29 Apr 2004 14:10:41 -0700 (PDT)

From:Linus Torvalds <torvalds@osdl.org>

To:Giuliano Colla

cc:Linux Kernel Mailing List <linux-kernel@vger.kernel.org>

Subject: Re: [hsflinux] [PATCH] Blacklist binary-only modules lying about

their license

Message-ID: <Pine.LNX.4.58.0404291404100.1629@ppc970.osdl.org>

 

On Thu, 29 Apr 2004, Giuliano Colla wrote:

>

> Let's try not to be ridiculous, please.

 

It's not abotu being ridiculous. It's about honoring peoples copyrights.

 

> As an end user, if I buy a full fledged modem, I get some amount of

> proprietary, non GPL, code  which executes within the board or the

> PCMCIA card of the modem. The GPL driver may even support the

> functionality of downloading a new version of *proprietary* code into

> the flash Eprom of the device. The GPL linux driver interfaces with it,

> and all is kosher.

 

Indeed. Everything is kosher, because the other piece of hardware and

software has _nothing_ to do with the kernel. It's not linked into it, it

cannot reasonably corrupt internal kernel data structures with random

pointer bugs, and in general you can think of firmware as part of the

_hardware_, not the software of the machine.

 

> On the other hand, I have the misfortune of being stuck with a

> soft-modem, roughly the *same* proprietary code is provided as a binary

> file, and a linux driver (source provided) interfaces with it. In that

> case the kernel is flagged as "tainted".