Wow, from the queue presentation this OS looks even less usable than DOS (MS aka Q). Why would the CLI terminate when it runs a programme? How do you run more than one programme at once? If each core polls the run queue does that mean that it busy cycles when there is no more work to do? Won't this waste energy? (A sin in the HPC world). Does it do the same for IO? IO request completion on a slow and/or busy disk could take as long as 50ms, for a 2.5GHz CPU for example this is 125 million clock cycles. Will the CPU busy cycle this as well?<p>If you want a simple OS that fits a lot into a small space, why not get a copy of the Lions' Commentary and translate the edition 6 kernel into asm. If you wanted to go gung ho you could add a simple BKL, demand paging and a network stack to complete the job. You could probably do all the above and keep it somewhere close to 20,000 lines of assembly (excluding drivers).<p>If you are looking for an education doing the above will probably do you just as good a job as trying from scratch.<p>Lions' Commentary on UNIX 6th Edition, with Source Code
<a href="http://en.wikipedia.org/wiki/Lions%27_Commentary_on_UNIX_6th_Edition,_with_Source_Code" rel="nofollow">http://en.wikipedia.org/wiki/Lions%27_Commentary_on_UNIX_6th...</a><p>The Art of Computer Programming
<a href="http://en.wikipedia.org/wiki/The_Art_of_Computer_Programming" rel="nofollow">http://en.wikipedia.org/wiki/The_Art_of_Computer_Programming</a>