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.

>>42
I wasn't really trying to make fun of him, but he deserves to be made fun of.  I'm really just in awe of the amount of his life that he's wasted, with absolutely nothing to show for it.

I could spend seven years carving a rock with my fingernails.  I might end up with something that might make one equally ignorant soul say "neat!"  Or, I could just use modern tools and spend an afternoon carving something and move on to the next project.

Your assumptions about my competence are misplaced, as is your urge to defend this nonsense.  The fact that you think he's done something useful speaks volumes about your own competence.