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
Subject: Re: tighter compression for x86 kernels
Date: Thu, 21 Dec 2000 00:22:40 +0100 [thread overview]
Message-ID: <20001221002240.A1213@var.cx> (raw)
In-Reply-To: <3A412C8D.59DDD9F2@BitWagon.com> <Pine.NEB.4.31.0012202338040.21463-100000@pluto.fachschaften.tu-muenchen.de>
In-Reply-To: <Pine.NEB.4.31.0012202338040.21463-100000@pluto.fachschaften.tu-muenchen.de>; from bunk@fs.tum.de on Thu, Dec 21, 2000 at 12:15:13AM +0100
On Thu, Dec 21, 2000 at 12:15:13AM +0100, Adrian Bunk wrote:
> > 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
>From that page:
UPX and the UCL library are free software; you can redistribute them
and/or modify them under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of
the License, or (at your option) any later version.
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.
--
Frank v Waveren Fingerprint: 0EDB 8787
fvw@[var.cx|dse.nl|stack.nl|chello.nl] ICQ#10074100 09B9 6EF5 6425 B855
Public key: http://www.var.cx/pubkey/fvw@var.cx-gpg 7179 3036 E136 B85D
-
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:53 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 [this message]
2000-12-20 23:27 ` Jens Müller
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=20001221002240.A1213@var.cx \
--to=fvw@var.cx \
--cc=bunk@fs.tum.de \
--cc=jreiser@BitWagon.com \
--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).