mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Doug McNaught <doug@wireboard.com>
To: David Lang <dlang@diginsite.com>
Cc: Felix von Leitner <felix-dietlibc@fefe.de>,
	"Albert D. Cahalan" <acahalan@cs.uml.edu>,
	Greg KH <greg@kroah.com>, <linux-kernel@vger.kernel.org>,
	<andersen@codepoet.org>
Subject: Re: [RFC] klibc requirements
Date: 15 Jan 2002 13:36:59 -0500	[thread overview]
Message-ID: <m34rlnzcj8.fsf@varsoon.denali.to> (raw)
In-Reply-To: <Pine.LNX.4.40.0201151005430.24005-100000@dlang.diginsite.com>
In-Reply-To: David Lang's message of "Tue, 15 Jan 2002 10:06:20 -0800 (PST)"

David Lang <dlang@diginsite.com> writes:

> On 15 Jan 2002, Doug McNaught wrote:
> 
> >
> > > as an example (not for the boot process, but an example of a replacement
> > > libc use) I use the firewall toolkit, it has been around for a _loooong_
> > > time (in software terms anyway) and has a firly odd licence (free for you
> > > to use, source available, cannot sell it) which is not compatable with the
> > > GPL. with glibc staticly linked this makes huge binaries, with libc5 they
> > > were a lot smaller. I would like to try to use this small libc for these
> > > proxies, but if the library is GPL, not LGPL I'm not allowed to.
> >
> > Hmm, I think you can; you just can't redistribute it.  Can you even
> > redistribute fwtk on non-commercial terms?
> >
> nope, only allowed to get it from nai (and they sure don't make it easy to
> find on their website)

Problem solved, then; you can link fwtk with a GPL'd libc on your own
machines and use it all day.  You can't redistribute fwtk, so you
aren't even tempted to violate the GPL.

-Doug
-- 
Let us cross over the river, and rest under the shade of the trees.
   --T. J. Jackson, 1863

  reply	other threads:[~2002-01-15 18:37 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-08 19:24 Greg KH
2002-01-08 20:37 ` Erik Andersen
2002-01-09  4:23 ` Felix von Leitner
2002-01-09  4:34   ` initramfs programs (was [RFC] klibc requirements) Greg KH
2002-01-09  6:10     ` Greg KH
2002-01-09  7:23       ` H. Peter Anvin
2002-01-09  9:33     ` Kai Germaschewski
2002-01-09 10:00     ` Erik Andersen
2002-01-09  4:51   ` [RFC] klibc requirements Greg KH
2002-01-09  5:01     ` H. Peter Anvin
2002-01-09  6:09       ` Greg KH
2002-01-09  7:26         ` H. Peter Anvin
2002-01-10 15:24           ` Matthias Kilian
2002-01-10 17:13             ` H. Peter Anvin
2002-01-10  6:30         ` Rusty Russell
2002-01-10 18:41           ` H. Peter Anvin
2002-01-09 14:15     ` Felix von Leitner
2002-01-09 14:30       ` Lars Brinkhoff
2002-01-09 14:51       ` Erik Andersen
2002-01-09 13:23   ` Juan Quintela
2002-01-09 14:57     ` Erik Andersen
2002-01-15  3:08   ` Albert D. Cahalan
2002-01-15 11:55     ` Felix von Leitner
2002-01-15 14:54       ` David Lang
2002-01-15 16:15         ` Doug McNaught
2002-01-15 18:06           ` David Lang
2002-01-15 18:36             ` Doug McNaught [this message]
2002-01-16 18:36         ` Erik Andersen
2002-01-16  7:50       ` Albert D. Cahalan
2002-01-09 10:38 ` initramfs programs (was [RFC] klibc requirements) Anton Altaparmakov
2002-01-09 15:56   ` Pavel Machek
2002-01-09 16:04     ` Patrick Mochel
2002-01-09 16:26       ` Greg KH
2002-01-09 16:29       ` Pavel Machek
2002-01-09 16:48         ` Andreas Ferber
2002-01-09 21:15   ` Alex Bligh - linux-kernel
2002-01-09 21:34   ` Anton Altaparmakov
2002-01-09 21:40     ` Greg KH
2002-01-09 22:12     ` Alex Bligh - linux-kernel
2002-01-09 21:55   ` Anton Altaparmakov
2002-01-09 22:15     ` Andreas Ferber
2002-01-10  0:25       ` Tom Rini
2002-01-10  0:38         ` Andreas Ferber
2002-01-10  2:42           ` Tom Rini
2002-01-10 14:09             ` Rob Landley
2002-01-10 22:24               ` Tom Rini
2002-01-11  0:15               ` H. Peter Anvin

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=m34rlnzcj8.fsf@varsoon.denali.to \
    --to=doug@wireboard.com \
    --cc=acahalan@cs.uml.edu \
    --cc=andersen@codepoet.org \
    --cc=dlang@diginsite.com \
    --cc=felix-dietlibc@fefe.de \
    --cc=greg@kroah.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

all inboxes | Powered by JetHome®