Besides that, it an Indian or African developer wanted to contribute, they could do so. That's the beauty of it all. Oh, and how many of them do? Well, that's probably why Linus hasn't appointed them to be maintainers.
You really don't keep track of anything beyond your state lines do you? There are quite a number of Indian _and_ African developers contributing (Me being one). Perhaps if you drove out further than your local grocery store you might actually meet interesting people out there.
NT kernal is; at pretty much any time you can give the three finger salute and get the 'stuff to do' dialog. When you see a blue screen, that's NT having caught an exception that worries it enough to *voluntarily* halt itself, because it can no longer guarentee that it's working with valid data. It also spews out a large amount of debug data. Most such bluescreen occur due to hardware drivers.
This is similar to a UNIX kernal spewing a bunch of kernal panic messages and the like to the syscon, then halting.
Very rarely will you see an NT derived kernal simply 'freeze.'
Exceptions don't have anything to do with a kernel being preemptive. I would hope any modern OS had exception handling. And the "3 finger salute" is actually handled by an interrupt handler, and those can preempt any kernel code regardless of wether you have a preemptive kernel or not (Hence the reason why DOS can use ctrl-alt-del too)
I remember reading that Ingo Molnar, who wrote a giant low-latency patch that worked this way, agreed with Linus that his low-latency patch was just too ugly and huge and should not be included in the main source tree.
That would be Andrew Morton's Full low latency patch. He currently is maintaining a mini-LL patch as well. There are reports from various people (Alan Cox being one) stating that they have found no noticeable difference between running -preempt and -ll, and in some cases -ll providing better average latencies.
Slashdot Mirror
http://function.linuxpower.ca/dmesg-smpu nction.linuxpower.ca/top-4way
http://f
Besides that, it an Indian or African developer wanted to contribute, they could do so. That's the beauty of it all. Oh, and how many of them do? Well, that's probably why Linus hasn't appointed them to be maintainers.
You really don't keep track of anything beyond your state lines do you? There are quite a number of Indian _and_ African developers contributing (Me being one). Perhaps if you drove out further than your local grocery store you might actually meet interesting people out there.
NT kernal is; at pretty much any time you can give the three finger salute and get the 'stuff to do' dialog. When you see a blue screen, that's NT having caught an exception that worries it enough to *voluntarily* halt itself, because it can no longer guarentee that it's working with valid data. It also spews out a large amount of debug data. Most such bluescreen occur due to hardware drivers. This is similar to a UNIX kernal spewing a bunch of kernal panic messages and the like to the syscon, then halting. Very rarely will you see an NT derived kernal simply 'freeze.'
Exceptions don't have anything to do with a kernel being preemptive. I would hope any modern OS had exception handling. And the "3 finger salute" is actually handled by an interrupt handler, and those can preempt any kernel code regardless of wether you have a preemptive kernel or not (Hence the reason why DOS can use ctrl-alt-del too)
I remember reading that Ingo Molnar, who wrote a giant low-latency patch that worked this way, agreed with Linus that his low-latency patch was just too ugly and huge and should not be included in the main source tree. That would be Andrew Morton's Full low latency patch. He currently is maintaining a mini-LL patch as well. There are reports from various people (Alan Cox being one) stating that they have found no noticeable difference between running -preempt and -ll, and in some cases -ll providing better average latencies.
Port which way? AtheOS -> Linux ? or Linux -> AtheOS. Do note that the AtheOS FS is a 64bit journaling filesystem whilst ext2 is erm.. well ;)
Regards
kernel 2.4.5 has know vm issues, 2.4.6 is MUCH better. I can vouch for both cases.