Even if hostlix guys wanted to help ReactOS team, they couldn't. From
ReactOS Development Policy:
8b) Developers who have had access to proprietary source code that
would have
originally fallen under trade secret protection (including, for
example,
the leaked Microsoft Windows source code) are a special case. The
copyright issues are unchanged, as are the patent issues, but any
developer who has the code is clearly either under an NDA or else does
not have a license to possess the code. In the latter case, there
is a
clear violation of the relevant trade secrets by the developer. As
such,
this kind of code is unsuitable even for research and
understanding. It
is the policy of the Project to not take submissions from
developers who
have or use any such proprietary code in their development efforts for
ReactOS.
All thouse hostlix guys have seen leaked windows source code and can not
contribute to ReactOS.
No changes made to hostlix code can be merged back to ReactOS.
I wrote all my ideas about the new ReactOS page (that came to my mind)
together:
http://reactosde.re.funpic.de/mediadetail.php?sec=Articles&cat=ideas&mdnr=1…
What is your opinion about that?
There are two (or more) possible solutions for the static main pages:
* wiki system that generate the static pages (HTML/XHTML) (maybe language
support problem ?)
* selfwritten simple CMS system (very flexible, easy to use, only a few
php-scripts so fewer bugs, better integration (design, layout), language
support, generate HTML/XHTML, ...)
(* CMS system like the current one)
What system do you prefer? (wiki, CMS, ...)
Compatibility and Package Manager section:
* wiki based (like in the current mediawiki only a long list)
* php based dynamic list (with filter features and tree structur; mysql
database): example: (first alpha page)
http://frik85.fr.funpic.de/packmgr/?page=tree&sec=view&sec2=2
* winehq's application database (or something else; redesign it?)
What system do you prefer? (wiki, dynamic list (tree structur), ...)
I will have time in july/august/sept. to implement the Compatibility-,
Package Manager section and the simple CMS system that can generate the
static pages, if it is okay for you.
But I will wait until I get a "start signal". If someone else want do it
alone or want help me, it will be no problem (for me; then I will have more
time to code for ReactOS).
I wrote this because the current ReactOS page is awful (design and CMS
system) and we need a better and more beautiful page to gain more visitors,
get a bigger ReactOS community (and more devs).
I hope the UI-Team will finalize the layout of the homepage in the next two
months.
Thanks for reading this, and maybe you find time to write your opinion about
that.
Best regards,
Klemens Friedl
(PS: Tomorrow, I will have no time to answer any emails, sorry.)
--
Weitersagen: GMX DSL-Flatrates mit Tempo-Garantie!
Ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl
ion(a)svn.reactos.com wrote:
>PCH for csrss and win32csr, and remove rosrtl usage
>
>Modified: trunk/reactos/subsys/csrss/api/wapi.c
>
>
> *Modified: trunk/reactos/subsys/csrss/api/wapi.c*
>
>--- trunk/reactos/subsys/csrss/api/wapi.c 2005-07-01 02:47:15 UTC (rev 16360)
>+++ trunk/reactos/subsys/csrss/api/wapi.c 2005-07-01 03:03:06 UTC (rev 16361)
>@@ -10,13 +10,8 @@
>
>
> /* INCLUDES ******************************************************************/
>
>
>
>-#include <windows.h>
>-#define NTOS_MODE_USER
>-#include <ndk/ntndk.h>
>-#include <rosrtl/thread.h>
>
>
>+#include "csrss.h"
>
>
>
>
>
>-#include "api.h"
>-
>
>
> #define NDEBUG
> #include <debug.h>
>
>@@ -170,7 +165,7 @@
>
>
>
> /* Close the port and exit the thread */
> NtClose(ServerPort);
>
>
>- RtlRosExitUserThread(STATUS_SUCCESS);
>
>
>+ NtTerminateThread(NtCurrentThread(), STATUS_SUCCESS);
>
>
> }
>
>
>
Hi,
this change is wrong. If you remove RtlRosExitUserThread, you have to
insert the code from RtlRosExitUserThread. With the current code, the
user mode stack from the thread isn't freed. Csrss does crash after a
short time because csrss isn't able to create a stack for a new thread.
This occurs while compiling ros on ros.
- Hartmut
On Wed, Jun 29, 2005 at 01:17:11PM +0200, Rafal Kupiec
wrote:
> K McI wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Rafal Kupiec wrote:
> >
> >>I think, now we're not violating the GPL.
> >>for eg:
>
>>http://svn.berlios.de/wsvn/hostilix/trunk/Sources/apps/notepad/dialog.c?op=…
> >
> >
> > I hope Revision 42 isn't the latest because the
> > URI is invalid (You lost a "w" somewhere from 1 to
> > 42)!
> > (...)
>
> What?
>
The site. The site that the above link points to.
Look at it.
* Copyright(C) 1999-2005r. BetaComp Team
<http://www.betacomp.info/>
becomes
* This file is a part of BetaComp Team Project
<http://ww.betacomp.info/>
Notice the missing W in "ww.betacomp.info".
-- Travis
____________________________________________________
Yahoo! Sports
Rekindle the Rivalries. Sign up for Fantasy Football
http://football.fantasysports.yahoo.com
I have recently acquired some second-hand hardware that will be dedicated to
my testing and development of reactos.
It will, however, not boot either 0.2.6 release or current SVN and I would
appreciate some assistance on how to debug this problem.
The output from the two versions is as follows.
0.2.6
Used memory 131072Kb
(mm/mminit.c:375) Kernel Stack Limits. InitTop = 0x800bb000, Init =
0x800b8000
(mm/virtual.c:214) FIXME: MEMORY_AREA_SYSTEM case incomplete (or possibly
wrong) for NtQueryVirtualMemory()
(ke/bug.c:56) Found Bugcheck Resource Data!
(ke/bug.c:67) Got Pointer to Bugcheck Resource Data!
(ke/clock.c:80) KiInitializeSystemClock()
(ke/clock.c:99) Finished KiInitializeSystemClock()
(ex/timer.c:172) ExpInitializeTimerImplementation()
(io/pnproot.c:676) DeviceID: Root\Ne2000 PDO 80546268
(io/pnproot.c:689) InstanceID: 0000 PDO 80546268
(io/pnproot.c:676) DeviceID: Root\PCI PDO 80546370
(io/pnproot.c:689) InstanceID: 0000 PDO 80546370
DriverBase for \SystemRoot\system32\drivers\pci.sys: 9cdb3000
Peripheral Component Interconnect Bus Driver
SVN (actually r16344 despite what it says)
(ntoskrnl\ke\main.c:294) ---------------------------------------------------
------------
(ntoskrnl\ke\main.c:295) ReactOS 0.3-SVN (Build 20050624-r16253)
Used memory 131072Kb
(ntoskrnl\mm\mminit.c:375) Kernel Stack Limits. InitTop = 0x800f2000, Init
= 0x800ef000
(ntoskrnl\mm\mm.c:327) No current process
In both cases the screen freezes after the line that says loading pci.sys
regards
Mike Lerwill
K McI wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Completely off topic, but a request:
>
> When you're quoting someone (anyone) who signed/encrypted
> their message, can you ax the "----- $% BEGIN PGP SIGNED
> MESSAGE $% -----" line, so ppls GPGPs don't wonder where the
> sign block is?
>
> I know I'm like, the only one here who does it, but I wanted
> to let everyone know, not just for this list.
>
> Thanx again
>
> -uQ
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFCwolc7mze81O92HkRAvyEAJwK6TLtoISfHFY4L+/7Y5o6pdyb1wCdFs1n
> PXsFokONZ4q4DydcS8j1s9Q=
> =Asvj
> -----END PGP SIGNATURE-----
Or even better, could you not turn the PGP sig off for the mailing list?
It does make reading your mails a little more complicated than need be.
You could always link your public key to a key server in a quick signature
if you wanted people to have access.
Ged.
P.s I know my mails from work have that annoying disclaimer. Unfortunately I
can't get rid of it without passing through an external script to remove it
(which would be breaking my company rules)
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Quandary wrote:
>
> On Wed, Jun 29, 2005 at 01:17:11PM +0200, Rafal Kupiec
> wrote:
> > K McI wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > Rafal Kupiec wrote:
> > >
> > >>I think, now we're not violating the GPL.
> > >>for eg:
> >
> >>http://svn.berlios.de/wsvn/hostilix/trunk/Sources/apps/notep
> ad/dialog.
> > >c?op=diff&rev=0&sc=1
> > >
> > >
> > > I hope Revision 42 isn't the latest because the
> > > URI is invalid (You lost a "w" somewhere from 1 to
> > > 42)!
> > > (...)
> >
> > What?
> >
>
> The site. The site that the above link points to.
> Look at it.
>
> * Copyright(C) 1999-2005r. BetaComp Team
> <http://www.betacomp.info/>
>
> becomes
>
> * This file is a part of BetaComp Team Project
> <http://ww.betacomp.info/>
>
> Notice the missing W in "ww.betacomp.info".
>
I still don't understand why they have to put their mark on the code at all.
Is it some kind of ego boost the hostilix team is a after?
Is it because they want people to think they have the skill the ROS devs
have?
Is it because they want people to think they wrote the code?
IMO, if you use code from another project, you leave the code as it is, i.e.
no claiming copyright, no adding headers to claim ownership, or to trick
people into thinking it's your code, or any other type of header just for
the sake of adding it.
The only time you should be adding your own mark is when you have altered
the code in some way. Your mark should then be added, in addition to the
current list of programmers.
To be honest, I find it all rather sad and quite pathetic to need to stoop
to this level.
Just take the damn headers off and all this hostility will end.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
On Tue, Jun 28, 2005 at 05:16:16PM +0200, Eric Kohl
wrote:
> Lucio Diaz wrote:
> >Third post, but, i downloaded their source code,
> >and it seems the original copyright notices are
> >there, so they are not violating the GNU licence.
> >
> >Best regards,
> >Lucio Diaz.
>
> The Hostilix 'developers' are still guilty of
> willful misrepresentation of the copyright because
> 1) They added their copyright to otherwise unchanged
> files and 2) they can only claim a copyright for the
> year 2005 but not from 1999 to 2005.
>
> So they are still violating the GPL.
They aren't violating the GPL by misrepresentation
(per se); they're (likely) violating the underlying
copyright law by making a false claim to ownership.
There's a subtle difference ;).
-- Travis
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
On Wed, Jun 29, 2005 at 11:09:01AM +0200, Rafal Kupiec
wrote:
> I think, now we're not violating the GPL.
> for eg:
>http://svn.berlios.de/wsvn/hostilix/trunk/Sources/apps/notepad/dialog.c?op=…
You know, it would have been WAY simpler if you had
just not screwed with -any- of the file headers in the
first place. Grab the latest ReactOS SVN, export it,
re-import it into your SVN, then DON'T MESS WITH THE
COPYRIGHT NOTICES. I mean, you've obviously had to do
a lot of work to add your name and replace the
contents of the other files, and look at how much good
it's done you?
In reality, the "right" process is really, really
easy. It's not necessary to plaster your name all
over the place, especially if you haven't done
anything in a given file. Whenever you make a change,
just add your copyright to the start of the file. It's
that easy. It means you do 0 work up front, *and* you
don't have angry devs breathing down your neck about
blatently ripping them off. "Branding" all of the
files, to be frank, is a *very* stupid waste of your
time, and has (clearly) only served to piss everyone
off.
Now, that's not to say people still won't be
disgruntled about it, but they'll grumble much more
quietly -- and it's WAY easier for you to cover your
ass by saying "all of the original copyright notices
in the source are intact" (because if you only add
notices, it doesn't remove or alter the existing
notices). Release everything under GPL, and bam...
you shouldn't run into too much trouble.
Cheers,
-- Travis
____________________________________________________
Yahoo! Sports
Rekindle the Rivalries. Sign up for Fantasy Football
http://football.fantasysports.yahoo.com
Hi,.
I'm polish fan of ReactOS. I would like to help you in making ReactOS
better.
I have some developer skills with C++ on Windows (x86, CE) platform but i
don't have enough time to help you in this area (maybe i'm to sluggish :-(
).
At this time i would like to help you with translating ReactOS to Polish
language.
In attachement there is a polish translation of userenv.
Sorry for my poor english.
Sebastian Gasiorek
