From: John Reiser <jreiser@BitWagon.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tighter compression for x86 kernels
Date: Thu, 21 Dec 2000 09:08:47 -0800 [thread overview]
Message-ID: <3A42391F.3490D554@BitWagon.com> (raw)
In-Reply-To: <Pine.NEB.4.31.0012202338040.21463-100000@pluto.fachschaften.tu-muenchen.de>
> > Both source (GPLv2) and pre-compiled binary for x86 are available.
> ^^^^^
> That's not true. Read
> http://wildsau.idv.uni-linz.ac.at/mfx/upx-license.html
The UPX team owns all copyright in all of UPX and in each part of UPX.
Therefore, the UPX team may choose which license(s), and has chosen two.
One of them is GPLv2. The UPX team understands, and fully intends
to abide by, its obligations under GPLv2 when any software that is subject
to GPLv2 is contributed to UPX and re-distributed by the UPX team. The
other license is detailed in the LICENSE file, but may be summarized as:
free to use if unmodified, and if used only to invoke the program, and
sublicensable only under the same terms. This permits using UPX to pack
a non-GPL executable. Users of UPX (as distributed by the UPX team)
may choose whether to use UPX according to GPLv2, or according to
the other license.
[I am not subscribed to this mailing list, so CC: or mail me if appropriate.]
--
John Reiser, jreiser@BitWagon.com
-
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-21 17:45 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
2000-12-21 17:08 ` John Reiser [this message]
-- strict thread matches above, loose matches on Subject: below --
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=3A42391F.3490D554@BitWagon.com \
--to=jreiser@bitwagon.com \
--cc=bunk@fs.tum.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