Realtime Multitasking OS Trakian Based on Managers it is thus extensible and can be modified and adapts to the environment and events, most automatically. Some Managers are required for the OS to be functionnal. This is the case of the "kernel" delivering services to others. Its also the case of the Memory Manager, in charge to furnish memory space to anyone requesting it. And the 2 are almost all what MUST be available permanently. For a PC the Memory Manager is about 4 kb and the kernel about 12 kb. To run a Trakian system need to be loaded and fired. This is almost all what is required to run SOME Trakians. To run in multitasking Trakian needs another Manager, the Clock Manager in charge to schedule the tasks and Managers. It results that on an i86 system the minimal size of a Trakian OS is about 20 kb for a multitasking system and much less for DSP or RISC processors. Many other functions can be required by applications. For Trakian, all are Managers. For example files are in charge of many Managers. Each type of "file" has one or many Managers taking this type in charge. And files can be memory space in RAM or ROM or disk files. The theory specifying that a Manager can use other services, such Managers have a low level interfacing to the physical system and higher level Managers for access by the users (programs). So, something comparable to the BIOS & DOS functions but also above DOS. Other IO's are similar, like serials or networks. Thus: low level interfacing to the IO chips...; or Managers. But also, if needed, to other softwares like another BIOS for PCs. And Managers in charge of protocols like PPP, IP, ... And above the later can exist Servers and Clients Managers. With a complete IO suite and Servers/Clients SMTP,
POP, HTTP,... Rem.:
|
|||||||||||||||||||||||||
