are impliedly licensed to any licensee. As such, the only way Company

\compB{} can benefit from Company \compA's implied patent license, is if it,

itself, distributes Company \compA's software program and grants an

implied patent license to any of its patents that cover that program.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\chapter{Defending Freedom on Many Fronts}

Chapters~\ref{run-and-verbatim} and~\ref{source-and-binary} presented the

core freedom-defending provisions of GPLv2\@, which are in GPLv2~\S\S0--3.

GPLv2\S\S~4--7 of the GPLv2 are designed to ensure that GPLv2~\S\S0--3 are

not infringed, are enforceable, are kept to the confines of copyright law but

entirely separate legal systems.  In short, while GPLv2~\S\S0--3 are the parts

of the license that defend the freedoms of users and programmers,

GPLv2~\S\S4--7 are the parts of the license that keep the playing field clear

so that \S\S~0--3 can do their jobs.

\section{GPLv2~\S4: Termination on Violation}

\label{GPLv2s4}

GPLv2~\S4 is GPLv2's termination clause.  Upon first examination, it seems

strange that a license with the goal of defending users' and programmers'

freedoms for perpetuity in an irrevocable way would have such a clause.

However, upon further examination, the difference between irrevocability

\section{GPLv2~\S10: Relicensing Permitted}

\label{GPLv2s10}

GPLv2~\S10 reminds the licensee of what is already implied by the nature of

copyright law.  Namely, the copyright holder of a particular software

program has the prerogative to grant alternative agreements under separate

copyright licenses.

\section{GPLv2~\S11: No Warranty}

\label{GPLv2s11}

\href{http://www.law.cornell.edu/ucc/2/2-316}{Uniform Commercial

  Code~\S2-316} requires that disclaimers of warranty be ``conspicuous''.

There is apparently general acceptance that \textsc{all caps} is the

preferred way to make something conspicuous, and that has over decades worked

its way into the voodoo tradition of warranty disclaimer writing.

That said, there is admittedly some authority under USA law suggesting that

capitalization and is absent when a disclaimer has the same typeface as the

terms surrounding it (see \textit{Stevenson v.~TRW, Inc.}, 987 F.2d 288, 296

(5th Cir.~1993)).  While GPLv3's drafters doubted that such authority would

apply to copyright licenses like the GPL, the FSF has nevertheless left

warranty and related disclaimers in \textsc{all caps} throughout all versions

of GPL\@\footnote{One of the authors of this tutorial, Bradley M.~Kuhn, has

  often suggested the aesthetically preferable compromise of a

  \textsc{specifically designed ``small caps'' font, such as this one, as an

    alternative to} WRITING IN ALL CAPS IN THE DEFAULT FONT (LIKE THIS),

  since the latter adds more ugliness than conspicuousness.  Kuhn once

  engaged in reversion war with a lawyer who disagreed, but that lawyer never

  answered Kuhn's requests for case law that argues THIS IS INHERENTLY MORE