This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: HD file system?
- From: Jonathan Larmour <jifl at eCosCentric dot com>
- To: Eric Verlind <eric dot verlind at streamconcept dot be>
- Cc: Nick Garnett <nickg at ecoscentric dot com>,ecos-discuss at sources dot redhat dot com
- Date: Sat, 01 Mar 2003 22:45:04 +0000
- Subject: Re: [ECOS] HD file system?
- References: <001e01c2df65$cfaa9870$010a0a0a@bardolino><m37kbkngxo.fsf@balti.calivar.com><000901c2df85$c478f120$010a0a0a@bardolino> <m33cm7nzag.fsf@balti.calivar.com> <001501c2dff7$17276890$010a0a0a@bardolino>
Eric Verlind wrote:
Okay, that's important to realise.
Suppose my company has its own code S, which is containing the company's
patented IP, constituting the basis of the company's existence. With that we
make a product called P, which consists of a single, statically linked image
with eCos used as OS. How sure can I be that patents of my company relating
to S are not endangered?
If you are using eCos with the eCos licence (the GPL *with* the exception)
then that's okay. If you incorporate any GPL'd code, e.g. from Linux in
your application, then everything must be distributed including your
application.
And about patents, the GPL says: "we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all."
and
"For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program."
So you could write the program incorporating GPL'd code.... you "just"
wouldn't be able to give it to anyone!
What about modifications to the code of eCos itself. Suppose that we make
modifications to -for example- the scheduler and build in a special,
patented, scheduling scheme of our own. How secure would that be from
exposal?
It wouldn't. eCos's licence says you must distribute all code derived in
any way from eCos code and it would be essentially impossible to do that
with a new scheduler, so you would either have a choice of permitting all
users of eCos to using and in turn redistributing that (patented) code
under eCos's licence, or not distributing it at all.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss