ReactOS is quite slow today, are we under a DoS
atack?, maybe related to this ekush guy?.This is
weird.
Lucio Diaz.
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
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 dont 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.
I took a picture of the screen:
http://mike.warpedbelief.com/images/ros-crash.jpg
It crashed immediately after I hit a key during the "Press any key to
boot CD..." prompt.
I can't really figure out if any hardware could cause problems. This
is the configuration:
Pentium 120 MHz
64 MB of RAM
2 GB hard disk (I think it's Western Digital)
2 MB ET4000 video
36x CD-ROM drive
One floppy drive
The hard disk partition scheme is this:
One primary partition. FAT16. Windows NT 4 Server install on it. Takes
up the whole 2 GB.
Hello,
While you guys are working on the website changes I would like to add
that the Wine application database is GPL, in CVS and is done in PHP.
http://cvs.winehq.com/cvsweb/appdb/
Thanks
Steven
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
chorns(a)cvs.reactos.com wrote:
>CVSROOT: /CVS/ReactOS
>Module name: reactos
>Repository: reactos/tools/
>Changes by: chorns(a)mok.osexperts.com 04/10/24 10:51:33
>
>Modified files:
> ./: ChangeLog
> reactos/ntoskrnl/: Makefile
> reactos/regtests/regtests/: regtests.c regtests.def
> reactos/regtests/shared/: regtests.h
> reactos/tools/: regtests.c
>Added files:
> reactos/ntoskrnl/tests/: .cvsignore Makefile setup.c stubs.tst
> reactos/ntoskrnl/tests/tests/: .cvsignore
>
>Log message:
> 2004-10-24 Casper S. Hornstrup <chorns(a)users.sourceforge.net>
>
> * ntoskrnl/Makefile (TARGET_REGTESTS): Define to yes.
> * regtests/regtests/regtests.c (_ExitProcess): Declare.
> * regtests/regtests/regtests.def (_ExitProcess@4): Ditto.
> * regtests/shared/regtests.h (_ExitProcess): Ditto.
> * tools/regtests.c: Exit process using _ExitProcess();
> Properly support fastcall symbols.
> * ntoskrnl/tests: New directory.
> * ntoskrnl/tests/tests: Ditto.
> * ntoskrnl/tests/.cvsignore: New file.
> * ntoskrnl/tests/Makefile: Ditto.
> * ntoskrnl/tests/setup.c: Ditto.
> * ntoskrnl/tests/stubs.tst: Ditto.
> * ntoskrnl/tests/tests/.cvsignore: Ditto.
>
>_______________________________________________
>Ros-cvs mailing list
>Ros-cvs(a)reactos.com
>http://reactos.com/mailman/listinfo/ros-cvs
>
>
>
Hi,
I can't say I'm terribly overjoyed with having the /tests directory in
/ntoskrnl. Would it be possible instead to have a /tests root (on the
new SVN server) where all the tests would go? like /tests/ntoskrnl,
/tests/kmregtests etc...
I think it would make it a bit clearer...it just bugs me to have /tests
in ntoskrnl.
Best regards,
Alex Ionescu
Hi Everyone,
We got very good feedback from LinuxWorld.de and I will be returning
next year. 90% of the people visting our booth left thinking very
highly of our work. All in all the results were much better than the
last expo. I very surprised that so many people came up to us and said
"we have heard of ReactOS or we have tried it out".
Here is my rough list of notes on where I think we need to go from here
after discussion with the developers and users.
1. We need a roadmap for the future.
THIS DOES NOT MEAN THAT THERE ARE FIRM DATES ATTACHED!!!!
But we do need to plan our 0.3, 0.4, 0.5 and 1.0 releases. During a
dinner discussion with some of the dev team I asked the question "What
do we need before we can have a ReactOS Workstation 1.0" and it does
not seem to be to far out of grasp. Dont get me wrong there are LOTS of
little things that must be done but the major things we need to have a
real replacement workstation are below. If you think about what Windows
NT 4 had even with Service Pack 6 we are not that far off. Note I am
not talking about a server replacement here. Just a usable client OS.
- Networking (0.3)
- Samba port needs to implemented (0.4)
- We need to implement Windows style printing support (0.4 or 0.5)
- Most applications need to install..Office 2000/XP, Quicken, etc
(0.4)
- We have to develop our own Hardware Compatibity List (0.5)
- NTFS (????)
- It must be stable (1.0)
2. We have to have regression testing in place.
Lack of stablity and regressions are killing us. We have to have the
Wine tests in ReactOS. We also need a suite of kernel mode tests.
Casper's system seems like its going to work well for the kernel mode
side but most of us seem to be worried about the lack of being able to
use Winehq regression tests for user mode.
3. We need to improve our documentation and website.
After much discussion and two too many beers on my part our discussions
turned to documentation and the website. We all agreed that the current
system is not working and we need to develop a method of storing most
of the website in CVS so that people can send us a patch. Same thing
with the documentation....none of us wants to use ezPublish to develop
documentation when we can all use docbook right out of cvs and submit
diffs. Most of us even like the Wiki system as its not hassle and can
maintain a history as well.
4. We need to develop relationships with vendors.
This ties in to getting ReactOS stable and usable. Once we have 0.3 out
the door I expect things will change for us in ways no one can see. I
am going to focus more on this in the coming months, first in the way
of hardware donations.
5. Moving to subversion.
There still seems to be some problems with this and while we all seem
to look forward to it, CVS is doing its job for the moment. GvG has
offered to setup a CVS mirror to help with some of the bandwith
problems of mok.
In closing it was very cool to get to meet all of the developers that
were able to make it, I feel like we are going in the right direction
and I look forward to your feedback.
Thanks
Steven
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
