path: root/mechanism.mdwn
diff options
authorGNU Hurd wiki engine <>2007-08-19 14:38:07 +0000
committerGNU Hurd wiki engine <>2007-08-19 14:38:07 +0000
commit8378363b3de23f6c45b659399a82c2310a955973 (patch)
treefd4946b8ab0e33130da704a5028c162564e33ff2 /mechanism.mdwn
parent7dacd493ecc8e7cde37e358354e85ff9efd32686 (diff)
web commit by NealWalfield: Create.
Diffstat (limited to 'mechanism.mdwn')
1 files changed, 22 insertions, 0 deletions
diff --git a/mechanism.mdwn b/mechanism.mdwn
new file mode 100644
index 00000000..fb4c9d55
--- /dev/null
+++ b/mechanism.mdwn
@@ -0,0 +1,22 @@
+The Collaborative International Dictionary of English v.0.48
+defines a mechanism as:
+> The series of causal relations that operate to produce an
+> effect in any system; as, the mechanism of a chemical
+> reaction.
+This is, a mechanism is a function that produces some result.
+As mechanisms determine the type of result, they necessarily
+impose some [[policy]] (rules). Mechanisms that are referred
+to as policy-free are those that minimally impose policy.
+A process can be used to encapsulate a program instance. On Unix,
+a process is associated with a UID. This UID, in part, determines
+what the process is authorized to do. On a [[microkernel]],
+the policy that controls what resources a process may access
+are realized separately. This may achieved through the use of
+UIDs, however need not. Thus, the processes mechanism on such
+microkernels impose less policy than on Unix. A process is not
+policy free as it is possible to use other mechanisms to
+encapsulate a program instance, e.g., [[SFI]] and tainting
+ala [[Asbestos]]. \ No newline at end of file