public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: John Mills <Jmills@TGA.com>
To: 'Jim Belton' <jhb@microplex.com>
Cc: eCos Discuss <ecos-discuss@sourceware.cygnus.com>,
	John Mills <Jmills@TGA.com>,
	"'Dr. Joel Sherrill, OAR Corp.'" <joel.sherrill@OARCorp.com>
Subject: RE: [ECOS] TCP/IP and RTEMS
Date: Tue, 28 Sep 1999 12:38:00 -0000	[thread overview]
Message-ID: <FD7521AABD30D2118284006008AE0B6E03C0B6@ns1.tga.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]

Title: RE: [ECOS] TCP/IP and RTEMS





Jim -


JB- Is RTEMS is shipped with the unmodified GPL, or do 
JB- they add the "special exception" in the text of the  
JB- license they ship?  I'd like a legal opinion on 
JB- whether linking with RTEMS puts my code under GPL, 
JB- because of the way the RTEMS license is written.


I can't give you legal advice or interpretations. You may wish to download RTEMS sources and check their license wording first-hand. My non-expert understanding is that both groups are attempting to achieve much the same thing. You may also wish to ask Dr. Sherrill of OAR Corp. [ mailto:joel.sherrill@OARcorp.com ], and naturally to seek legal advice as to the nuances of each license.

Regards -


  John Mills, Sr. Software Engineer
  TGA Technologies, Inc.
  100 Pinnacle Way, Suite 140
  Norcross, GA 30071-3633
  e-mail: jmills@tga.com
  Phone: 770-441-2100 ext.124 (voice)
         770-449-7740 (FAX)




             reply	other threads:[~1999-09-28 12:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-28 12:38 John Mills [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-09-28 11:12 John Mills
1999-09-28 11:58 ` Jim Belton
1999-09-28  9:48 Jim Belton

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=FD7521AABD30D2118284006008AE0B6E03C0B6@ns1.tga.com \
    --to=jmills@tga.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jhb@microplex.com \
    --cc=joel.sherrill@OARCorp.com \
    /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).