• View
• Edit
• History
• Print

Cy/VOS structure and components

Author: Telcontar
See also: Prop.Components

It is proposed to look something like the above when Cy/VOS is being used to run both graphical and command-line/daemon processes.

This is an overly simplified view; however, at least if I post this the kernel hacker will feel obligated to fixx0r the page and post a better version :) Note that the image is also out of date, and is only a rough guide.

In-Depth:

Further details about each of the above can be found in the following pages, although they are not dedicated to the task (better links to come hopefully, wink wink):

Any way of making pmWiki support image maps? The above image would be great if it were made into an image map =]

0. The basics

• The bootloader?
• Boot UI modules
• CLC? -- the The Cy/VOS Lib C
• The microkernel? -- pre-emptive multitasking microkernel supporting message-passing interprocess communication on which the entire system is based

1. Critical components

• The Dispatcher
• The Session Manager
• The Virtual File Server
• The Configuration Server
• Omen Script Language System?
• The Universal Interface Manager

2.5 Defined dispatch bindings

Some services may not be implemented as a single, standard server or manager but as just a standard dispatch binding ID for applications to attach to. e.g.

• Notification Manager -- The user process that allows programs to notify the user both locally and across a network.
• User Process Manager -- The user process responsible for displaying running tasks
• User Launch Manager -- The user process responsible for launching processes on the system; this may be the same process as the above
• Interface Server -- The process responsible for providing the system with a user interface. Programs are patched through to this to display an interface; the process bound to this dispatch binding could implement any kind of interface via the universal interface system, such as CLI, console, graphical or speech.
• File System Navigator -- The program responsible for showing disc views to the user. For example, when a browser wishes to show a downloaded file on disc.

2. Extra components

This page presently deals only with "core" components -- those that are required by the OS to run. Components that are not required for basic operation are covered under Prop.Components.

That's all I can think of right now ... Presumably need to consider where text and language support (localisation etc) comes in, printing, etc.