LoseThos

http://forum.osdev.org/viewtopic.php?f=15&t=24190

In LoseThos, core 0 is master and the rest are slaves.  Also, LoseThos is for single-user home systems, not multiuser mainframes or servers. 

It is multitasking, but, for example, does not break 100 block disk reads into pieces, so drive is locked and other tasks waiting on drive starve.  I plan to keep it that way -- it's simpler.

I turn interrupts off during some parts of code AND employ a spin lock.  Conceptually, turning-off interrupts instantly gives you mutex... exclusion from other tasks (on that core).  For multicore, you need to go beyond, so I employ separate spin locks for everything.  Technically, a spin lock alone is good enough without turning-off interrutps, but, I donno, just because I think it's more efficient, I turn-off interrupts, too.  In almost all cases, applications are single core and run on core 0, so CLI provides no-waste solutions to mutual exclusion.  My spin locks Yield CPU on failure, which is unacceptible for large-number-of-tasks systems.  Go use Linux if you want that.  If you want simpler, use LoseThos.

>>43
To make something new, you have to kill something old and ugly.
No, you don't.  You might find it hard to believe, but programmers in the real world generally just fire up an IDE or a text editor, write some code, compile it, run it, debug it, and call it a day.  And they manage to do this without killing anything.

Microsoft
Really?  This is your one example?  You do know that a program written for an 8086 (late seventies) will run on your Win7 box, right?  Microsoft is actually the prime example of a company that has sacrificed tremendous functionality in favor of backwards compatibility.  Shit.  IHBT.  Well, fuck you.