l4-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Part 2: System Structure


From: Pierre THIERRY
Subject: Re: Part 2: System Structure
Date: Fri, 19 May 2006 14:36:38 +0200
User-agent: Mutt/1.5.11+cvs20060403

Scribit Marcus Brinkmann dies 19/05/2006 hora 13:50:
> > It says: if you *redistribute* the modifications *then* you must
> > disclose. It notably does NOT say that if you connect two programs
> > that you run with an IPC pipe then you must disclose.
> But it does also not say that if you connect them only with an IPC
> pipe then you do not need to disclose.

If a license doesn't express a need, it is not needed. That's the very
nature of it.

> The sentence "No permission is given for modes of distribution that
> deny users that run covered works the full exercise of the legal
> rights granted by this License" is pretty clear.

It only applies to a GPLed software. If a non-GPL software is run with
opacity, there is no problem. Even if you run a GPL software in opaque
storage, but have access to the source, I think there still is no
problem, as you are then granted the full exercise of the legal rights
granted by the GPL.

> The second paragraph has a slightly different twist to it.  It
> specifically forbids to use covered works for things like locked-down
> gaming consoles or other proprietary devices, which do not allow
> changes be made by the owner.

Which, it is worth noting it, would not be the case with a
constructor-based system. Though the constructor could help design such
a system.

Legally,
Nowhere man
-- 
address@hidden
OpenPGP 0xD9D50D8A

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]