public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: lwip, ppp, advertising clause
Date: Thu, 15 Apr 2004 14:48:00 -0000	[thread overview]
Message-ID: <407EA0C4.2020604@eCosCentric.com> (raw)
In-Reply-To: <20040415075724.GC23252@biferten.ma.tech.ascom.ch>

Andrew Lunn wrote:
> Hi Jifl
> 
> I've taken a quick look at lwip to see if we can import it. The PPP
> code has an advertising clause. How does that affect eCos? As far as i
> know the rest of eCos is all free of these clauses. So should we leave
> ppp out or lwip? 

It can depend on the advertising clause for a start. The original UCB 
advertising clause can be removed (see 
<http://www.gnu.org/philosophy/bsd.html>). However other nutters have 
sometimes modified files, and put in their own advertising clause 
(short-sighted!).

As a result, we already have some files affected by the advertising clause 
in the net stack which is why the net stack doesn't have the eCos GPL on 
it. Given that, there's no reason why we can't include more code in 
principle although without advertising clause would be a lot better. The 
code would like the net stack not be GPL'd, but use the same header as the 
net stack (if one is going to be added).

I gather some people in the *BSD projects have been contacting original 
authors to get them to rescind the advertising clause on their files, so 
it's possible we could go back and check what they've come up with; but I 
don't know the state of that and it would take a little time to run through 
every affected file.

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

      reply	other threads:[~2004-04-15 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15  7:57 Andrew Lunn
2004-04-15 14:48 ` Jonathan Larmour [this message]

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=407EA0C4.2020604@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).