summaryrefslogtreecommitdiff
path: root/capability.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@codesourcery.com>2013-07-21 15:35:02 -0400
committerThomas Schwinge <thomas@codesourcery.com>2013-07-21 15:35:02 -0400
commit9933cec0a18ae2a3d752f269d1bb12c19f51199d (patch)
treecc30f2d56b87d3896e460a58b76e964231c0d578 /capability.mdwn
parent65efe654a9cb0b682efa9bf21065469a2e9147f4 (diff)
IRC.
Diffstat (limited to 'capability.mdwn')
-rw-r--r--capability.mdwn20
1 files changed, 18 insertions, 2 deletions
diff --git a/capability.mdwn b/capability.mdwn
index 7219cdce..0ebe5cd4 100644
--- a/capability.mdwn
+++ b/capability.mdwn
@@ -1,5 +1,5 @@
-[[!meta copyright="Copyright © 2007, 2008, 2010, 2011 Free Software Foundation,
-Inc."]]
+[[!meta copyright="Copyright © 2007, 2008, 2010, 2011, 2013 Free Software
+Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -77,6 +77,22 @@ port|microkernel/mach/port]]. As in UNIX (see above), they are not
[[persistent|persistency]].
+## IRC, freenode, #hurd, 2013-07-01
+
+ <nlightnfotis> I have read plenty of documents, and wrapped my head around
+ most Hurd concepts, but I still have not understood well what
+ capabilities are.
+ <youpi> Mmm, which capabilities?
+ <youpi> AIUI, the Hurd doesn't really have a notion of capabilites, just a
+ notion of owning a port right
+ <nlightnfotis> From what I have understood (from the critique) they
+ reference ports so they objects can be referenced via them
+ <youpi> (which provides processes a way for doing things)
+ <youpi> ok, so we are talking about the same thing, I guess
+ <nlightnfotis> ahh, that's cool. I thought there was more to the story that
+ I couldn't understand
+
+
# Further Reading
* [[Mach port|microkernel/mach/port]]