--- Alex Ionescu <ionucu(a)videotron.ca> wrote:
> Two issues I see here:
>
> 1) Developers. Do you mean that each developer will be paid? How will
> this be done? equally shared? Not to sound like an ass, but there may be
> times when a developer does absolutely nothing (read: me for the next
> month), while someone else is hacking away 100KLOC of code. Or someone
> that generally only does little fixes (which can be really useful, and
> is all the useful time he can offer due to work/family/school) versus
> someone which already has assured income and spends 24 hours a day
> working on Reactos. Would it be fair to pay everyone the same amount of
> money? Sorry if I'm misunderstanding the issue, but I just want to be
> fair. Besides, I'm sure many developers might want to refuse getting
> paid. Working for free is sometimes a personal choice, and the offers
> certain tangible and psycoligcal advantages. I don't know about others,
> but I myself would feel bad in many ways to receive money by working on
> ReactOS. I would feel as if any bugs ormistakes that I make now have
> monetary losses associated with them.
The idea is to start with the ReactOS Foundation does two things in terms of paying developers.
1. Offers bounties for certain features or bugs in bugzilla. Call them 1 time cash prizes.
2. Acts as a escrow or broker for third parties wanting to offer a bounty. (see 1)
I don't think this will discourage development. There are tons of little features I would like to
see that no one is working on atm where a bounty system would be nice. If I had $500 spare I would
put up a bounty for the 3com driver or for the NMake backend for the xmlbuildsystem. Also single
user contributions could be pooled for a bug. NOTE: I DO NOT WANT A PLEDGE SYSTEM. THEY DON'T
WORK.
IF YOU REALLY WANT TO CONTRIBUTE MONEY TO A BUG THEN THIS WILL BE THE BEST WAY!
Think about the following
-------------------------------------------
Steven Edwards Enters bug #311337
"Make ReactOS have a 3com Vortext (959/930) driver"
Alex gives $50 earmarked bug #311337
Steven gives $100 to bug #311337
Some random user throws in $200 for bug #311337
Someone decides "hey $350 will pay for a nice weekend at the beach! I'll take it!"
And they start coding. They get a working driver and it passes QA so it goes in SVN.
The ReactOS Foundation then writes a check for $350 to said developer.
-------------------------------------------
> 2) I think expos should get more then 5%. An expo of 4 people would cost
> around 2000$ (assuming 150$/night * 3 nights, plus food and other needs,
> *4 people). Now at minimum we'll probably want to attend a North
> American and a European conference, meaning 4000$. The European one is
> bound to have more then 4 people anyways, so with 6 people, it'll up the
> cost to 6000$. 5% means that we would need 80 000$ in donations. Seems a
> lot to me at this stage. Then again, we probably won't want to pay the
> full cost of an expo at this point, but whatever, I'm just giving ideas
> and I hope they help!
Nothing is set in stone as we have $0 cash flow atm. It will be up to the board to decide on a
final budget. I just want to have a rough plan in place as I am going to start soliciting help for
funding.
> I would love to be on the board. I think I have some pretty good ideas
> for moving forward, and it'll be a good short break from coding when
> I'll happen.
I want to get something up on foundation.reactos.org and then have a discussion on the
ros-foundation list on what needs to be ammended in the bylaws and we can vote on restructure,
memebers, etc.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com
Hi all,
Buiding Reactos on a Win98 machine does noy work anymore ( at least for
me) . It was working several ago.
The make clean fails as well with these error messages :
-----------------------------
netstat: [CLEAN]
ping: [CLEAN]
route: [CLEAN]
telnet: [CLEAN]
whois: [CLEAN]
regtests: [CLEAN]
tshared: [CLEAN]
RM] /include/roscfg.h
trop de paramètres - buildno.exe
==== Too many parameters
fichier introuvable
=== File not found
trop de paramètres - wine2ros.exe
trop de paramètres - winebuild.exe
trop de paramètres - bin2res.exe
wpp: [CLEAN]
unicode: [CLEAN]
C:\Svn\reactos>mingw32-make
--------------------------------
Anybody may confirm ?
Thanks
Gerard
Then this is a make.exe bug, which should use %COMSPEC%...
--- Hartmut Birr <hartmut.birr(a)gmx.de> wrote:
> The windows 98 problem has nothing to do with a bug in binutils.
> Make.exe uses cmd to process all pipe commands on windows, but windows
> 98 doesn't have a cmd program. You should copy command.com to cmd.com or
> cmd.exe.
>
> - Hartmut
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
Hi!
This was not unexpected. I noticed last night csrss was over 11000K bytes in size.
The memory leak in csrss is handles, some of them do not close. So the number goes
from ~80 to 2000+ after two days of building ros over and over. You can try to close
the windows but the handle count is the same so~~~~~.
Thanks,
James
(KERNEL32:mem/global.c:412) Memory Load: 59
(KERNEL32:mem/global.c:412) Memory Load: 59
(mm/npool.c:1626) Trying to allocate 16 bytes from nonpaged pool - nothing suita
ble found, returning NULL
KeBugCheck at mm/rmap.c:382
A problem has been detected and ReactOS has been shut down to prevent damage to
your computer.
The bug code is undefined. Please use an existing code instead.
Technical information:
*** STOP: 0x00000000 (0x00000000,0x00000000,0x00000000,0x00000000)
Frames:
<ntoskrnl.exe:dbe3 (ke/bug.c:459 (KeBugCheckEx))>
<ntoskrnl.exe:dc03 (ke/bug.c:479 (KeBugCheck))>
<ntoskrnl.exe:87911 (mm/rmap.c:382 (MmInsertRmap))>
<ntoskrnl.exe:740aa (mm/anonmem.c:385 (MmNotPresentFaultVirtualMemory))>
<ntoskrnl.exe:7e8f8 (mm/mm.c:387 (MmNotPresentFault))>
<ntoskrnl.exe:befc (mm/i386/pfault.c:66 (MmPageFault))>
<ntoskrnl.exe:1927 (ke/i386/exp.c:543 (KiTrapHandler))>
<ntoskrnl.exe:399d (/tmp/ccc7YZmh.s:235 (KiTrapProlog))>
<ntdll.dll:24118 (/tmp/ccuotceE.s:35 (memset))>
Entered debugger on embedded INT3 at 0x0008:0x800064be.
kdb:>
Lock up no keyboard!
royce(a)svn.reactos.com wrote:
>patch by kjk::hyperion, fix syntax of gcc inline asm
>
>
>Updated files:
>trunk/reactos/hal/halx86/include/hal.h
>
>
This is not acceptable solution IMHO...there are problems with certain
GCC versions assigning AMD64 registers on i386. See revision 13587 and
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10153.
- Filip
essentially, I've tracked down the problem to SerialPnpStartDevice()
being called with ResourceList == NULL.
Here's the details, if ya want 'em:
serial.sys
exception not handled
stop 1e ( c0000005, 9d2f9019, 0, 0 )
serial.sys address 9d2f9019 base 9d2f6000
page fault 14(0)
cs:eip 8:9d2f9019 <serial.sys: 3019> pnp.c:168
cr2 0 cr3 27000 proc: 8084ad00 Pid: 4 <System> Thrd: 8084b828 Tid: 0
DS,ES,GS=10 FS=30
eax 808a7660
ebx 0
ecx 808a7580
edx 808a7828
ebp 800bc9b4
esi 808a77b8
esp 800be808
edi 0
eflags 00210292
kesp 800be808
kernel stack base 800bd000
frames:
<serial.sys: 352b> pnp.c:341, SerialPnP() calling SerialPnpStartDevice()
<ntoskrnl.exe: 329c5> io/irp.c:212, IofCallDriver() calling indirect
<ntoskrnl.exe: 329e1> io/irp.c:226, IoCallDriver() calling IofCallDriver()
<ntoskrnl.exe: 34975> io/pnpmgr.c:665, IopInitiatePnpIrp() calling
IoCallDriver()
<ntoskrnl.exe: 2d151> io/device.c:78, IopInitializeDevice() calling
IopInitiatePnpIrp()
<ntoskrnl.exe: 2fa9d> io/driver.c:1890, NtLoadDriver() calling
IopInitializeDevice()
<ntoskrnl.exe: 318b> ke/i386/syscall.S:178
<ntoskrnl.exe: 2536d> ex/zw.S:771, ZwLoadDriver()
<ntoskrnl.exe: 2efa1> io/driver.c:1378, IopInitializeSystemDrivers()
calling IopLoadDriver()
<8007cc61> ??? only possibility is: IoInit3() calling
IopInitializeSystemDrivers()
<8007d7ac> ??? only possibility is: ExpInitializeExecutive() calling
IoInit3()
<ntoskrnl.exe: d04c> ke/main.c:104, KiSystemStartup() calling
ExpInitializeExecutive()
<80079290> ke/main.c:283, _main() calling KiSystemStartup();
<ntoskrnl.exe: 104b> ke/i386/main.S:51
now, serial.sym:
13019: 8b 07 mov (%edi),%eax
C:\cvs\reactos\drivers\dd\serial>addr2line -e serial.nostrip.sys 13019
C:/cvs/reactos/drivers/dd/serial/pnp.c:168
C:/cvs/reactos/drivers/dd/serial/pnp.c:168:
for (i = 0; i < ResourceList->Count; i++)
notice edi is NULL, which is holding the value of ResourceList, which
traces it's origin back to:
IoGetCurrentIrpStackLocation(Irp)->Parameters.StartDevice.AllocatedResources
which in turn comes from:
DeviceNode->BootResources at ntoskrnl/io/device.c:68 in
IopInitializeDevice()
there's a FIXME on the line above:
/* FIXME: Should be DeviceNode->ResourceList */
hpoussin, or anybody else? should serial.sys handle a NULL ResourceList
gracefully ( imho it should probably have some SEH in there ), or is it
a bug for it to be getting a NULL ResourceList?
Hi,
--- Robert K�pferl <rob(a)koepferl.de> wrote:
> it might seem stupid or girlish, but I want to invite any of you to
> visit me in Vienna (wien.AT) for a couple of days. I would like to just
> see some of these people (and of course have freeky kernel talks) who
> make up this project. Get to know personally. Don't be shy and have a
> try with my private email. (possibly use gpg/x.509).
> If you think this Vienna is too far away - maybe next year I live less
> far away from you.
Some of us will be meeting at WineConf at the end of the month.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com
Hi!
hbirr(a)svn.reactos.com wrote:
> Initialize the maximum length of the device description to allocate more than map register.
>
>
>
> Updated files:
> trunk/reactos/drivers/storage/floppy/floppy.c
>
Does this fix floppy support? I haven't had floppy working for 6+ months!
ha! floppy working!
James
hbirr(a)svn.reactos.com wrote:
> - Use IoBuildAsynchronousFsdRequest instead IoBuildSynchronousFsdRequest in NtRead/WriteFile.
> - Guard the calls to IoBuildAsynchronousFsdRequest with an exception frame.
>
> Modified: trunk/reactos/ntoskrnl/io/rw.c
I dont understand these changes... Why did you change from sync. to
asycn. version, and whats the point with try/except around
IoBuildAsynchronousFsdRequest???
Gunnar
http://reactos.com:8080/archives/public/ros-svn/2005-April/002066.html
or run
"ARCH=i386 make bootcd"
--- ea <ea(a)iol.it> wrote:
> Hi all,
>
> I can't build the bootable cd image.
> Is it just my local repository broken (14488)?
>
> ---
> 3: directory ./../bootcd/disk\reactos\system32\
> 3: file ./../bootcd/disk\reactos\system32\ntdll.dll
> 3: file ./../bootcd/disk\reactos\system32\smss.exe
> Can't open ./../bootcd/disk/../isoboot.bin
>
> make: *** [bootcd_makecd] Error 1
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev
>
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word