Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

["Nicolas Mailhot" <nicolas.mailhot@laposte.net>]

Since everyone is having fun, and the kernel includes a few bytes from
yours truly, I figured I could state my opinion too.

1. Linus' "clarifications" of GPL2-only may apply to the kernel work
as a whole, and to patches submitted from the clarification moment,
but not to the individual patches submitted before. A lot of noise is
made about dead author wishes but nobody seems to care about the
wishes of live authors who may not have a hard GPL2-only stance and
have been retroactively tagged GPLv2-only supporters. (that's for all
the diatribes about the evil FSF unduly speaking for others)

2. Seems there are enough GPLv3 supporters to do the heavy legwork and
get clear statements about licensing status of past code submissions
should the  core kernel hackers agree to GPLv3 licensing. So a
licensing change is technically possible

Daniel Hazelton wrote:
> And this is what the FSF, RMS and yes, *YOU*, Alexandre, fail to
realize
> - the GPL covers *ONLY* the software. It has *ZERO* legal standing when
> applied to hardware.

And drm keys are hardware? Nope, they're a string of bytes. Looks like
software to me.

You're the one who's confusing hardware with software, and trying to
apply software legal rules (limited usage rights) to hardware. No law
forbids taking hardware you bought and modifying it outside the
original manufacturer control (including crazy things like turning
cars in boats or planes). In fact many laws especially target attempts
to restrict modification to "blessed" original manufacturer parts
(I'll intentionaly skip over recent creative lawmaking which confused
everyone including the people who rubber-tamped lobby texts)

That may suck but while you can technicaly substitute a cheaper
software implementation to a hardware one, they are not covered by the
same laws. You have a technical continuum but not a legal continuum.

Your software substitute is going to be subject to the software legal
corpus. That means licensing limits. If you wrote your own code you
can use whatever restrictive software license you want. If you didn't
you have to abide with the original author licensing, which may be
something like the GPLv3 that forbids you to extend software
restrictions to hardware (and one is not more amoral than the other)

GPLv3 only controls the software part of the equation. You can still
manufacture hardware however you want. What you can't do any longer is
use software and software exclusive licensing terms to control
hardware (Bear in mind even if you sold a device with a physicaly
welded hood the law allows the buyer to take a hammer and crack it
open. Legal manufacturer control just does not exist past this point.
That should tell you who is crossing the lines in the drm case).

You may still limit modifications if you don't sell a device but rent
it, but many tivo-ing entities around the world want to eat their cake
and keep it by selling hardware and using drm to lock it (trying to
apply software rules to hardware)

If the GPLv3 actually tried to use copyright law to control hardware,
it wouldn't stand in court.

-- 
Nicolas Mailhot

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