From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5896 invoked by alias); 1 Mar 2002 18:08:39 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 5847 invoked from network); 1 Mar 2002 18:08:34 -0000 Received: from unknown (HELO executor.cambridge.redhat.com) (195.224.55.237) by sources.redhat.com with SMTP; 1 Mar 2002 18:08:34 -0000 Received: from sheesh.cambridge.redhat.com (sheesh.cambridge.redhat.com [172.16.18.69]) by executor.cambridge.redhat.com (Postfix) with ESMTP id 8B14BABB09; Fri, 1 Mar 2002 18:08:33 +0000 (GMT) Received: (from bartv@localhost) by sheesh.cambridge.redhat.com (8.11.6/8.11.0) id g21I8XV11052; Fri, 1 Mar 2002 18:08:33 GMT Date: Fri, 01 Mar 2002 10:32:00 -0000 Message-Id: <200203011808.g21I8XV11052@sheesh.cambridge.redhat.com> X-Authentication-Warning: sheesh.cambridge.redhat.com: bartv set sender to bartv@redhat.com using -f From: Bart Veer To: guangbutun@hotmail.com Cc: ecos-discuss@sources.redhat.com In-reply-to: (guangbutun@hotmail.com) Reply-To: bartv@redhat.com References: Subject: Re: [ECOS] ecos licensing FAQ queries X-SW-Source: 2002-03/txt/msg00016.txt.bz2 >>>>> "Butun" == Butun Guang writes: Butun> How do you define a LARGER WORK. It's obvious that it Butun> covers the situation someone develops a product on top of Butun> ecos. How about someone develops an operating system, can Butun> he benefit from ecos packeges, i.g., just includes or Butun> modifies one package (like just one device driver code), Butun> and deliver within their product? Note: I am not a company lawyer so this response should be treated as my personal opinion rather than an official position. The RHEPL applies to the eCos source files individually, not to eCos in its entirety. If you use one or more source files from any eCos package, for example a device driver, with your application then the terms of the RHEPL apply to that use. It does not matter whether or not your application is a typical eCos application, built on top of some eCos HAL and other packages. Bart -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss