Ekush

[Ge van Geldorp]

Ekush (http://www.ekush.com) published some binaries. Surprise, surprise, it
looks like ReactOS very much (Check e.g. the radio buttons on the "Accept
License" screen during 2nd stage setup). Their readme.rtf
(epc/doc/Readme.rtf) has these entries:

<quote start>

Q. Is the OS completely written from scratch?
A. Not really in many cases, at least 50% of the components has been shared
or taken from some other projects. In fact, we mostly get the ideas and
writing them for ours. Eventually we are coding them new folks are based on
something else (in wish list) and slowly-slowly they will be removed from
our main source tree.

Q. You guys says “Project published under the GPL” but why don’t you
published sources?
A. Initially we decided that, EKUSH should be published under the GPL. But,
still there is some confusion within the team. We are now sharing sources
between team members only and unless the confusion goes removed we cannot
publish sources. 
Finally, we decided to use a BSD styled license for Ekush and sources or
binaries whatever we publish should be free to public and covered by the
same license (until a functional edition is released).

Information sources and Wish List:

Bochs, Wine, QEMU, Freetype, React OS, Nova OS, Minuet OS, Flask, Athe OS,
FreeBSD, Systernals, Flik OS, Plan 9, Fravee, V2 OS, Uranium, Fhreed JS,
Free Dos, OP OS, Jlink Wrap, NETrove, Fedora, LFS, Tiny OS, Pear PC, BartPE,
KDesktop, Line, WinPenguins, 3D Desktop, 
Dr. Anil Basu, Jason Robin, William Harry, Luiz Quarteiro, Fernando Adantas,
Sergio Luiz Silva, John Abraham, Little Robin, Lina Sen, Maria, Adnan, James
Bukan, Dr. Piera and Project 21 Team."

<quote end>

My guess is they are in violation of the GPL by using (some of) our source
and not publishing their source.

Gé van Geldorp.

[Ge van Geldorp]

Well, some string searching in their binaries reveals:

$ strings -a ntoskrnl.exe | grep Ros
CcRosInternalFreeCacheSegment failed, status = %x
CcRosUnmapCacheSegment failed, status = %x
CCRosUnmapCacheSegment failed, status = %x
CcRosInitializeFileCache
CcRosReleaseFileCache
KeRosDumpStackFrames
KeRosPrintAddress

$ strings -a ver.dll | grep ReactOS
OS2 Images not supported under ReactOS at this time.

I think we should inform them they are in violation of the GPL and thereby
breaking copyright law. Jason, maybe you can send them an email?

Gé.

[Jason Filby]

On Tue, 9 Nov 2004 13:10:18 +0100, Ge van Geldorp [e-mail] wrote:
> I think we should inform them they are in violation of the GPL and thereby
> breaking copyright law. Jason, maybe you can send them an email?

I will write them a letter explaining our position (when their site is
back up) with appropriate links to fsf.org and perhaps eff.org.

Cheers
Jason

[Aliberti Emanuele]

Jason Filby wrote:
> On Tue, 9 Nov 2004 13:10:18 +0100, Ge van Geldorp [e-mail] wrote:
> > I think we should inform them they are in violation of the GPL and thereby
> > breaking copyright law. Jason, maybe you can send them an email?
>
> I will write them a letter explaining our position (when their site is
> back up) with appropriate links to fsf.org and perhaps eff.org.

This page my be of interest: http://www.gnu.org/licenses/gpl-violation.html

Emanuele

[Filip Navara]

Ge van Geldorp wrote:
> I think we should inform them they are in violation of the GPL and thereby
> breaking copyright law. Jason, maybe you can send them an email?

AFAIK they actually don't violate the GPL as long as they will send the 
source code on request (see GPL section 3). This doesn't mean that we 
shouldn't mail them and clear out the situation though...

Regards,
Filip

[Thomas Weidenmueller]

Filip Navara wrote:
> AFAIK they actually don't violate the GPL as long as they will send 
> the source code on request (see GPL section 3). This doesn't mean that 
> we shouldn't mail them and clear out the situation though...

But i really doubt it's legal to remove copyright information. Remember, 
we still own the copyright, we just permit others to use the sources as 
the license says. Which, as I understand it, implies they must not 
remove copyrights, neither from binaries nor from sources. We don't have 
access to the sources but they changed all copyright information in the 
file properties of the binaries. What they do is not just insolent (by 
not giving credit to the real creators) but also illegal.

Regards
Thomas

[Filip Navara]

Thomas Weidenmueller wrote:
> Filip Navara wrote:
> > AFAIK they actually don't violate the GPL as long as they will send 
> > the source code on request (see GPL section 3). This doesn't mean 
> > that we shouldn't mail them and clear out the situation though...
>
> But i really doubt it's legal to remove copyright information. 
> Remember, we still own the copyright, we just permit others to use the 
> sources as the license says. Which, as I understand it, implies they 
> must not remove copyrights, neither from binaries nor from sources. We 
> don't have access to the sources but they changed all copyright 
> information in the file properties of the binaries. What they do is 
> not just insolent (by not giving credit to the real creators) but also 
> illegal.

True, it's illegal to misrepresent the origin and remove copyright 
information. I haven't seen the released binaries, so I reacted only 
based on the information in the mails...

Regards,
Filip

[Filip Navara]

Filip Navara wrote:
> Thomas Weidenmueller wrote:
> > Filip Navara wrote:
> > > AFAIK they actually don't violate the GPL as long as they will send 
> > > the source code on request (see GPL section 3). This doesn't mean 
> > > that we shouldn't mail them and clear out the situation though...
> >
> > But i really doubt it's legal to remove copyright information. 
> > Remember, we still own the copyright, we just permit others to use 
> > the sources as the license says. Which, as I understand it, implies 
> > they must not remove copyrights, neither from binaries nor from 
> > sources. We don't have access to the sources but they changed all 
> > copyright information in the file properties of the binaries. What 
> > they do is not just insolent (by not giving credit to the real 
> > creators) but also illegal.
>
> True, it's illegal to misrepresent the origin and remove copyright 
> information. I haven't seen the released binaries, so I reacted only 
> based on the information in the mails...

Now I got the binaries too. Not that they only misrepresent the origin 
of ReactOS, but they also did the same with QEMU. It looks like they got 
the 0.6 release, renamed QEMU to EmuPC and changed the copyright strings 
in it.

- Filip

[Ge van Geldorp]

> From: Ge van Geldorp
>
> Ekush (http://www.ekush.com) published some binaries. 
> Surprise, surprise, it looks like ReactOS very much (Check 
> e.g. the radio buttons on the "Accept License" screen during 
> 2nd stage setup).
> Some string searching in their binaries reveals:
>
> $ strings -a ver.dll | grep ReactOS
> OS2 Images not supported under ReactOS at this time.

Shortly after I sent this email to ros-dev yesterday the Ekush website went
down. Today they are back, with a slightly changed set of binaries. The
strings I reported yesterday are gone now (well, except for the
CcRosInitializeFileCache and CcRosReleaseFileCache exports from NTOSKRNL,
maybe changing the name of an exported symbol was too difficult???). There's
still plenty of other evidence of the ReactOS heritage though. I guess since
I only reported about ReactOS they forgot to remove the references to Wine
(except ofcourse the copyright notices, those are gone).

This pisses me off bigtime. I can only explain it as a deliberate attempt to
use the work of Qemu, FreeType, Wine and ReactOS without giving credit.

Gé van Geldorp.

"Ge van Geldorp" [e-mail] wrote:
> Shortly after I sent this email to ros-dev yesterday the Ekush website

went
> down. Today they are back, with a slightly changed set of binaries. The
> strings I reported yesterday are gone now (well, except for the
> CcRosInitializeFileCache and CcRosReleaseFileCache exports from NTOSKRNL,
> maybe changing the name of an exported symbol was too difficult???).

There's
> still plenty of other evidence of the ReactOS heritage though. I guess

since
> I only reported about ReactOS they forgot to remove the references to Wine
> (except ofcourse the copyright notices, those are gone).
>
> This pisses me off bigtime. I can only explain it as a deliberate attempt

to
> use the work of Qemu, FreeType, Wine and ReactOS without giving credit.

Hi!

I downloaded the old ekush package from a mirror and had a closer look at
it:

IMO, the fdc.sys driver is a hacked Microsoft driver because it uses 'INIT'
and 'PAGE' sections, which are not used in our drivers. This driver does not
contain any debug information as the other drivers do. And the name
'Lianasoft' has the same length as 'Microsoft' so patching the .exe file is
pretty easy.

I could identify most of the other components as ReactOS components because
of unique names in the debug section of the components, like AtapiPolledRead
in atapi.sys or uart_detect in serial.sys and serenum.sys.

I also noticed that the domain ekush.com seem to be registered by Siemens
Bangladesh Ltd. Maybe we should also contact them because Siemens, a
multi-national corporation, should be interested in respecting copyright
law.

Regards,
Eric

[Magnus Olsen]

I got the orginal zip from yestday of ekush.com
if that should be any help

----- Original Message ----- 
From: "Ge van Geldorp" [e-mail]
To: "'ReactOS Development List'" [e-mail];
[e-mail]
Sent: Wednesday, November 10, 2004 10:16 AM
Subject: [ros-dev] Ekush
> From: Ge van Geldorp
>
> Ekush (http://www.ekush.com) published some binaries.
> Surprise, surprise, it looks like ReactOS very much (Check
> e.g. the radio buttons on the "Accept License" screen during
> 2nd stage setup).
> Some string searching in their binaries reveals:
>
> $ strings -a ver.dll | grep ReactOS
> OS2 Images not supported under ReactOS at this time.

Shortly after I sent this email to ros-dev yesterday the Ekush website went
down. Today they are back, with a slightly changed set of binaries. The
strings I reported yesterday are gone now (well, except for the
CcRosInitializeFileCache and CcRosReleaseFileCache exports from NTOSKRNL,
maybe changing the name of an exported symbol was too difficult???). There's
still plenty of other evidence of the ReactOS heritage though. I guess since
I only reported about ReactOS they forgot to remove the references to Wine
(except ofcourse the copyright notices, those are gone).

This pisses me off bigtime. I can only explain it as a deliberate attempt to
use the work of Qemu, FreeType, Wine and ReactOS without giving credit.

Gé van Geldorp.

_______________________________________________
Ros-dev mailing list
[e-mail]
http://reactos.com:8080/mailman/listinfo/ros-dev

On Wed, Nov 10, 2004 at 10:16:06AM +0100, Ge van Geldorp wrote:
> This pisses me off bigtime. I can only explain it as a deliberate attempt to
> use the work of Qemu, FreeType, Wine and ReactOS without giving credit.

It happened to pearpc a few weeks ago (or allegedly it happened, i never
heard any final verdict), but people will recognize it, and the people
who do this will only get a bad reputation.

On the other hand, look at it this way:

1) they consider this stuff of reactos mature enough to build a product
   upon.
2) they're integrating it. I haven't seen the product yet, but there
   might be an oppertunity here to learn from their integration.

Mark

(and of course i agree they're wrong)

[Alex Ionescu]

Mark IJbema wrote:
> On Wed, Nov 10, 2004 at 10:16:06AM +0100, Ge van Geldorp wrote:
> > This pisses me off bigtime. I can only explain it as a deliberate attempt to
> > use the work of Qemu, FreeType, Wine and ReactOS without giving credit.
>
> It happened to pearpc a few weeks ago (or allegedly it happened, i never
> heard any final verdict), but people will recognize it, and the people
> who do this will only get a bad reputation.
>
> On the other hand, look at it this way:
> they consider this stuff of reactos mature enough to build a product
>
> upon.
> 2) they're integrating it. I haven't seen the product yet, but there
>   might be an oppertunity here to learn from their integration.

The only thing they are integrating is our source code with Microsoft's.
> Mark
>
> (and of course i agree they're wrong)

Best regards,
Alex Ionescu

On Wed, Nov 10, 2004 at 07:21:37AM -0500, Alex Ionescu wrote:
> Mark IJbema wrote:
> > On Wed, Nov 10, 2004 at 10:16:06AM +0100, Ge van Geldorp wrote:
> > > This pisses me off bigtime. I can only explain it as a deliberate attempt 
> > > to
> > > use the work of Qemu, FreeType, Wine and ReactOS without giving credit.
> >
> > It happened to pearpc a few weeks ago (or allegedly it happened, i never
> > heard any final verdict), but people will recognize it, and the people
> > who do this will only get a bad reputation.
> >
> > On the other hand, look at it this way:
> > they consider this stuff of reactos mature enough to build a product
> >
> > upon.
> > 2) they're integrating it. I haven't seen the product yet, but there
> >  might be an oppertunity here to learn from their integration.
>
> The only thing they are integrating is our source code with Microsoft's.

Didn't they integrate it with qemu as well, or did i misunderstand that.
But i don't think we should get all too pissed about stuff like this,
since it will probably happen again, again and again.

Mark

[Filip Navara]

----- PŮVODNÍ ZPRÁVA -----
Od: "Ge van Geldorp" [e-mail]
Komu: "'ReactOS Development List'"
[e-mail],[e-mail] Předmět: [ros-dev]
Ekush
Datum: 10.11.2004 - 10:45:57

[snip]
> This pisses me off bigtime. I can only explain it as a

deliberate > attempt to
> use the work of Qemu, FreeType, Wine and ReactOS without giving
> credit.

It pisses me too! I sent a mail to the owner of the domain (the
siemens guy) requesting him to take down the site or remove the
binaries until the legal situation will be cleared out...

Regards,
Filip
-- 
A za kolik kupujete ELEKTRO Vy?
http://www.MALL.cz/penezenka
Ověřte si přes SMS, kolik se dá UŠETŘIT!

[Royce Mitchell III]

Ge van Geldorp wrote:
> Shortly after I sent this email to ros-dev yesterday the Ekush website went
> down. Today they are back, with a slightly changed set of binaries. The
> strings I reported yesterday are gone now (well, except for the
> CcRosInitializeFileCache and CcRosReleaseFileCache exports from NTOSKRNL,
> maybe changing the name of an exported symbol was too difficult???). There's
> still plenty of other evidence of the ReactOS heritage though. I guess since
> I only reported about ReactOS they forgot to remove the references to Wine
> (except ofcourse the copyright notices, those are gone).
>
> This pisses me off bigtime. I can only explain it as a deliberate attempt to
> use the work of Qemu, FreeType, Wine and ReactOS without giving credit.

Keep a copy of every set of binaries they release. You'll have 
documentation of what they're doing so we can take legal action.
> Gé van Geldorp.
>
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev
>
> .
-- 
------------------------
http://wecanstopspam.org

[Magnus Olsen]

I will keep the first release and second releas
orignal zip files.
If any one need these file I can send them or put on a webserver

----- Original Message ----- 
From: "Royce Mitchell III" [e-mail]
To: "ReactOS Development List" [e-mail]
Sent: Wednesday, November 10, 2004 2:38 PM
Subject: Re: [ros-dev] Ekush

Ge van Geldorp wrote:
> Shortly after I sent this email to ros-dev yesterday the Ekush website went
> down. Today they are back, with a slightly changed set of binaries. The
> strings I reported yesterday are gone now (well, except for the
> CcRosInitializeFileCache and CcRosReleaseFileCache exports from NTOSKRNL,
> maybe changing the name of an exported symbol was too difficult???).

There's
> still plenty of other evidence of the ReactOS heritage though. I guess

since
> I only reported about ReactOS they forgot to remove the references to Wine
> (except ofcourse the copyright notices, those are gone).
>
> This pisses me off bigtime. I can only explain it as a deliberate attempt

to
> use the work of Qemu, FreeType, Wine and ReactOS without giving credit.

Keep a copy of every set of binaries they release. You'll have
documentation of what they're doing so we can take legal action.
> Gé van Geldorp.
>
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev
>
> .
-- 
------------------------
http://wecanstopspam.org

_______________________________________________
Ros-dev mailing list
[e-mail]
http://reactos.com:8080/mailman/listinfo/ros-dev

[Jakob Eriksson]

Magnus Olsen wrote:
> I will keep the first release and second releas
> orignal zip files.
> If any one need these file I can send them or put on a webserver

Don't do that. It might be considered Microsoft "warez" and then
you are in trouble.

regards,
Jakob

[Rick Parrish]

If it is contra-band as Jacob suggests ... put your copy(ies) in a safe 
place and contact the authorities. Do not delete or erase them - that 
would be destroying evidence.

(in my humble I'm-not-a-lawyer-in-any-country option)

-rick

Jakob Eriksson wrote:
> Don't do that. It might be considered Microsoft "warez" and then you 
> are in trouble.

[James Tabor]

Royce Mitchell III wrote:
> Ge van Geldorp wrote:
> > Shortly after I sent this email to ros-dev yesterday the Ekush website 
> > went
> > down. Today they are back, with a slightly changed set of binaries. The
> > strings I reported yesterday are gone now (well, except for the
> > CcRosInitializeFileCache and CcRosReleaseFileCache exports from NTOSKRNL,
> > maybe changing the name of an exported symbol was too difficult???). 
> > There's
> > still plenty of other evidence of the ReactOS heritage though. I guess 
> > since
> > I only reported about ReactOS they forgot to remove the references to 
> > Wine
> > (except ofcourse the copyright notices, those are gone).
> >
> > This pisses me off bigtime. I can only explain it as a deliberate 
> > attempt to
> > use the work of Qemu, FreeType, Wine and ReactOS without giving credit.
>
> Keep a copy of every set of binaries they release. You'll have 
> documentation of what they're doing so we can take legal action.

Their site was up last night, I have the ekush.zip file if anyone needs it.
> > Gé van Geldorp.

Ekush had a one year road map and it was a very fast one year of development.
Micro kernel from Oct - Jan 03 to fully operational product. I guess Leaked
Source + ROS + Wine, was their development model!

Money Scam!
James

[Rick Parrish]

Ge van Geldorp wrote:
> Shortly after I sent this email to ros-dev yesterday the Ekush website went
> down. Today they are back, with a slightly changed set of binaries.

Is there anyone on this list that lives in Bangladesh that could pursue 
legal action in the juristiction where it occurred?

On a side note, I'm more concerned about these guys drawing the wrath of 
Microsoft and - in so doing - impacting this project in a negative way.

-rick

[Anich Gregor]

On Wednesday 10 November 2004 14:52, Rick Parrish wrote:
> Ge van Geldorp wrote:
> > Shortly after I sent this email to ros-dev yesterday the Ekush website
> > went down. Today they are back, with a slightly changed set of binaries.
>
> Is there anyone on this list that lives in Bangladesh that could pursue
> legal action in the juristiction where it occurred?

Microsoft? (they stole their floppy driver didnt they?)
> On a side note, I'm more concerned about these guys drawing the wrath of
> Microsoft and - in so doing - impacting this project in a negative way.
>
> -rick

Look what I found in Ekush' ntoskrnl:
http://blight.eu.org/reactos/ekush-tskswitch.html

;-)

-blight

[James Tabor]

Ge van Geldorp wrote:
> Ekush (http://www.ekush.com) published some binaries. Surprise, surprise, it
> looks like ReactOS very much (Check e.g. the radio buttons on the "Accept
> License" screen during 2nd stage setup). Their readme.rtf
> (epc/doc/Readme.rtf) has these entries:
>
> <quote start>
>
> Q. Is the OS completely written from scratch?
> A. Not really in many cases, at least 50% of the components has been shared
> or taken from some other projects. In fact, we mostly get the ideas and
> writing them for ours. Eventually we are coding them new folks are based on
> something else (in wish list) and slowly-slowly they will be removed from
> our main source tree.
>
> Q. You guys says “Project published under the GPL” but why don’t you
> published sources?
> A. Initially we decided that, EKUSH should be published under the GPL. But,
> still there is some confusion within the team. We are now sharing sources
> between team members only and unless the confusion goes removed we cannot
> publish sources. 
> Finally, we decided to use a BSD styled license for Ekush and sources or
> binaries whatever we publish should be free to public and covered by the
> same license (until a functional edition is released).
>
> Information sources and Wish List:
>
> Bochs, Wine, QEMU, Freetype, React OS, Nova OS, Minuet OS, Flask, Athe OS,
> FreeBSD, Systernals, Flik OS, Plan 9, Fravee, V2 OS, Uranium, Fhreed JS,
> Free Dos, OP OS, Jlink Wrap, NETrove, Fedora, LFS, Tiny OS, Pear PC, BartPE,
> KDesktop, Line, WinPenguins, 3D Desktop, 
> Dr. Anil Basu, Jason Robin, William Harry, Luiz Quarteiro, Fernando Adantas,
> Sergio Luiz Silva, John Abraham, Little Robin, Lina Sen, Maria, Adnan, James
> Bukan, Dr. Piera and Project 21 Team."
>
> <quote end>
>
> My guess is they are in violation of the GPL by using (some of) our source
> and not publishing their source.
>
> Gé van Geldorp.

WOOOOW! What happen to the site?

Site temporarily down for maintenance work.

Please visit at a later time.

LOL,
James

[J.M.Piulachs]

These guys are not aware of google cache ;) 
http://216.239.59.104/search?q=cache:zVauACrLkV8J:www.akshor.com/+&hl=ca

----- Original Message ----- 
From: "James Tabor" [e-mail]
To: "ReactOS Development List" [e-mail]
Sent: Tuesday, November 09, 2004 2:50 PM
Subject: Re: [ros-dev] Ekush
> Ge van Geldorp wrote:
> > Ekush (http://www.ekush.com) published some binaries. Surprise, surprise, 
> > it
> > looks like ReactOS very much (Check e.g. the radio buttons on the "Accept
> > License" screen during 2nd stage setup). Their readme.rtf
> > (epc/doc/Readme.rtf) has these entries:
> >
> > <quote start>
> >
> > Q. Is the OS completely written from scratch?
> > A. Not really in many cases, at least 50% of the components has been 
> > shared
> > or taken from some other projects. In fact, we mostly get the ideas and
> > writing them for ours. Eventually we are coding them new folks are based 
> > on
> > something else (in wish list) and slowly-slowly they will be removed from
> > our main source tree.
> >
> > Q. You guys says “Project published under the GPL” but why don’t you
> > published sources?
> > A. Initially we decided that, EKUSH should be published under the GPL. 
> > But,
> > still there is some confusion within the team. We are now sharing sources
> > between team members only and unless the confusion goes removed we cannot
> > publish sources. Finally, we decided to use a BSD styled license for 
> > Ekush and sources or
> > binaries whatever we publish should be free to public and covered by the
> > same license (until a functional edition is released).
> >
> > Information sources and Wish List:
> >
> > Bochs, Wine, QEMU, Freetype, React OS, Nova OS, Minuet OS, Flask, Athe 
> > OS,
> > FreeBSD, Systernals, Flik OS, Plan 9, Fravee, V2 OS, Uranium, Fhreed JS,
> > Free Dos, OP OS, Jlink Wrap, NETrove, Fedora, LFS, Tiny OS, Pear PC, 
> > BartPE,
> > KDesktop, Line, WinPenguins, 3D Desktop, Dr. Anil Basu, Jason Robin, 
> > William Harry, Luiz Quarteiro, Fernando Adantas,
> > Sergio Luiz Silva, John Abraham, Little Robin, Lina Sen, Maria, Adnan, 
> > James
> > Bukan, Dr. Piera and Project 21 Team."
> >
> > <quote end>
> >
> > My guess is they are in violation of the GPL by using (some of) our 
> > source
> > and not publishing their source.
> >
> > Gé van Geldorp.
>
> WOOOOW! What happen to the site?
>
> Site temporarily down for maintenance work.
>
> Please visit at a later time.
>
> LOL,
> James
> _______________________________________________
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev

[Wesley Parish]

Well, I'm now on akshor.com and downloading ekush.zip.  Via google cache, of 
course.  (EmuPC's disappeared, of course.)

Should I forward it to the relevant copyright holders?  (It's 6.1 MB large)

Wesley Parish

On Wed, 10 Nov 2004 07:50, J.M.Piulachs wrote:
> These guys are not aware of google cache ;)
> http://216.239.59.104/search?q=cache:zVauACrLkV8J:www.akshor.com/+&hl=ca
>
> ----- Original Message -----
> From: "James Tabor" [e-mail]
> To: "ReactOS Development List" [e-mail]
> Sent: Tuesday, November 09, 2004 2:50 PM
> Subject: Re: [ros-dev] Ekush
> > Ge van Geldorp wrote:
> > > Ekush (http://www.ekush.com) published some binaries. Surprise,
> > > surprise, it
> > > looks like ReactOS very much (Check e.g. the radio buttons on the
> > > "Accept License" screen during 2nd stage setup). Their readme.rtf
> > > (epc/doc/Readme.rtf) has these entries:
> > >
> > > <quote start>
> > >
> > > Q. Is the OS completely written from scratch?
> > > A. Not really in many cases, at least 50% of the components has been
> > > shared
> > > or taken from some other projects. In fact, we mostly get the ideas and
> > > writing them for ours. Eventually we are coding them new folks are based
> > > on
> > > something else (in wish list) and slowly-slowly they will be removed
> > > from our main source tree.
> > >
> > > Q. You guys says “Project published under the GPL” but why don’t you
> > > published sources?
> > > A. Initially we decided that, EKUSH should be published under the GPL.
> > > But,
> > > still there is some confusion within the team. We are now sharing
> > > sources between team members only and unless the confusion goes removed
> > > we cannot publish sources. Finally, we decided to use a BSD styled
> > > license for Ekush and sources or
> > > binaries whatever we publish should be free to public and covered by the
> > > same license (until a functional edition is released).
> > >
> > > Information sources and Wish List:
> > >
> > > Bochs, Wine, QEMU, Freetype, React OS, Nova OS, Minuet OS, Flask, Athe
> > > OS,
> > > FreeBSD, Systernals, Flik OS, Plan 9, Fravee, V2 OS, Uranium, Fhreed JS,
> > > Free Dos, OP OS, Jlink Wrap, NETrove, Fedora, LFS, Tiny OS, Pear PC,
> > > BartPE,
> > > KDesktop, Line, WinPenguins, 3D Desktop, Dr. Anil Basu, Jason Robin,
> > > William Harry, Luiz Quarteiro, Fernando Adantas,
> > > Sergio Luiz Silva, John Abraham, Little Robin, Lina Sen, Maria, Adnan,
> > > James
> > > Bukan, Dr. Piera and Project 21 Team."
> > >
> > > <quote end>
> > >
> > > My guess is they are in violation of the GPL by using (some of) our
> > > source
> > > and not publishing their source.
> > >
> > > Gé van Geldorp.
> >
> > WOOOOW! What happen to the site?
> >
> > Site temporarily down for maintenance work.
> >
> > Please visit at a later time.
> >
> > LOL,
> > James
> > _______________________________________________
> > Ros-dev mailing list
> > [e-mail]
> > http://reactos.com:8080/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev
-- 
Wesley Parish
* * *
Clinersterton beademung - in all of love.  RIP James Blish
* * *
Mau e ki, "He aha te mea nui?"
You ask, "What is the most important thing?"
Maku e ki, "He tangata, he tangata, he tangata."
I reply, "It is people, it is people, it is people."