From: "Jens Müller" <jens@unfaehig.de>
To: <linux-kernel@vger.kernel.org>
Subject: Re: tighter compression for x86 kernels
Date: Thu, 21 Dec 2000 00:27:03 +0100 [thread overview]
Message-ID: <006401c06adc$5c6a65c0$87dde23e@enode> (raw)
In-Reply-To: <3A412C8D.59DDD9F2@BitWagon.com> <Pine.NEB.4.31.0012202338040.21463-100000@pluto.fachschaften.tu-muenchen.de> <20001221002240.A1213@var.cx>
----- Original Message -----
From: "Frank v Waveren" <fvw@var.cx>
To: "Adrian Bunk" <bunk@fs.tum.de>
Cc: "John Reiser" <jreiser@BitWagon.com>; <linux-kernel@vger.kernel.org>
Sent: Thursday, December 21, 2000 12:22 AM
Subject: Re: tighter compression for x86 kernels
> Seems GPL2 to me. I haven't read all of the rest of the page, but
> that'd either be dual licensing stuff, or further restrictions, which
> would be in contradiction with the GPL.
>
Seems to be kind of dual licensing:
"The stub which is imbedded in each UPX compressed program is part
of UPX and UCL, and contains code that is under our copyright. The
terms of the GNU General Public License still apply as compressing
a program is a special form of linking with our stub.
As a special exception we grant the free usage of UPX for all
executables, including commercial programs.
See below for details and restrictions."
It extends the scope of the license to _linking_ with commercial
software.
Jens
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-20 23:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-20 22:02 tighter compression for x86 kernels John Reiser
2000-12-20 23:15 ` Adrian Bunk
2000-12-20 23:22 ` Frank v Waveren
2000-12-20 23:27 ` Jens Müller [this message]
2000-12-21 17:08 ` John Reiser
2001-01-02 22:25 Rob Landley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='006401c06adc$5c6a65c0$87dde23e@enode' \
--to=jens@unfaehig.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).