Hey All,

Let me get this right. Is this the architecture we are looking at:

+------------------------------------------+
|              Applications                |
+------------------------------------------+
|              Assemblies                  |
+------------------------------------------+
|     Drivers                              |
+-----------------+                        |
| Abstraction     |                        |
+-----------------+------------------------+
|               Kernel                     |
+------------------------------------------+

I propose:

+------------------------------------------+
|A             Applications                | -> Includes CAS/MSIL
+------------------------------------------+
|A             Assemblies                  | -> Includes CAS/MSIL
+------------------------------------------+
|U             Unification                 | -> Last layer of CAS. Hardcoded
security checks.
+------------------------------------------+
|     Drivers  Runtime                    S| -> Can only be accessed by
unification.
+-----------------+                       S| -> GAC/JIT etc.
| Abstraction    S|                       S| -> Machine code is valid.
+-----------------+------------------------+
|               Kernel                    K| -> Can only be accessed by
layer above. Pure Machine code.
+------------------------------------------+

As such, we would have the following layers (letters in above diagram):

Kernel
System
Unification
Application

Each only able to access the one directly below it. In a classical
filesystem this would relate to:

K: /Assembly/Kernel/image.bin : Needs WriteKernel privelage enforced in U
S: /Assembly/System/*         : Needs WriteSystem privelage enforced in U
U: /Assembly/Unification/*    : Needs WriteUnification privelage
A: /Assembly/Application/*    : Needs Install privelage
A: /Programs/*                : Needs Install privelage

Jonathan Chayce Dickinson




-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers

Reply via email to