This image shows a simplified view of the overall design of Linux.

>>60015324
>Linux
>Win32 / OS/2
Doesn't compute

everything in templeos runs in kernel mode and can just write wherever the fuck they want in memory, including the kernel memory spaces.

>>60015361
*Windows.

also maybe read the source code.

I'm sure there is a scheduler.holyc whatever

>>60015399
Is it possible to make a diagram or description of each component of TempleOS?

I want to know which system / API is responsible for handling the display, and which is for handling the file system, etc...

File: 1485999577070.png (14KB, 667x865px) Image search: [Google]

14KB, 667x865px

>>60015324
literally like this

>>60015464
what is there to diagram?

I bet it doesn't even have a pre-empting scheduler and no multitasking outside of the windowing system.

>>60015718
>pre-empting scheduler and no multitasking
What are these? How do they work?
What other design decisions factor into the TempleOS Operating System?

>>60015780
scheduler is literally just a collection of tasks waiting for CPU time and have some associated cpu register map or other stateful information attached.

preemption just implies the kernel decides when a process is done executing instead of allowing the software the privilege of relinquishing control when it wants to.

>>60015684
this. it's a godsend

>>60015684
pretty sure it has an actual layout and api and stuff, although u can go straight to hardware like that if u want

>>60015718
>no multitasking outside of the windowing system.
eh? windowing system has nothing to do with multitasking capability, in fact only tasks on CPU0 even have windows.

>>60015324
If anyone else is legitimately interested, since Terry puts the effort into documenting everything:

https://www.youtube.com/watch?v=l9Ed8hWjnO0
http://www.templeos.org/Wb/Doc/MultiCore.html

>>60015324
>This image shows a simplified view of the overall design of Linux

https://en.wikipedia.org/wiki/Architecture_of_Windows_NT