Archives are refreshed every 30 minutes - for details, please visit the main index.
You can also download the archives in mbox format.

l4-hurd (date)

[Thread Index][Top][All Lists]

Advanced

[Prev Period]

Last Modified: Sun Apr 30 2006 23:56:33 -0400 Messages in reverse chronological order

[Next Period]

---

• April 30, 2006
  • Re: How to add confinement to the Hurd?, Jonathan S. Shapiro, 23:56
  • Re: Challenge: Find potential use cases for non-trivial confinement, Marcus Brinkmann, 23:54
  • Re: Challenge: Find potential use cases for non-trivial confinement, Jonathan S. Shapiro, 23:48
  • Re: bit-split, or: the schizophrenia of trusted computing, Jonathan S. Shapiro, 23:47
  • Re: Challenge: Find potential use cases for non-trivial confinement, Pierre THIERRY, 23:46
  • Re: Challenge: Find potential use cases for non-trivial confinement, Marcus Brinkmann, 23:44
  • Re: bit-split, or: the schizophrenia of trusted computing, Marcus Brinkmann, 23:39
  • Re: How to add confinement to the Hurd?, Marcus Brinkmann, 23:34
  • Re: Challenge: Find potential use cases for non-trivial confinement, Pierre THIERRY, 23:33
  • Re: How to add confinement to the Hurd?, Jonathan S. Shapiro, 23:33
  • Re: bit-split, or: the schizophrenia of trusted computing, Marcus Brinkmann, 23:24
  • Re: Challenge: Find potential use cases for non-trivial confinement, Pierre THIERRY, 23:23
  • Re: Challenge: Find potential use cases for non-trivial confinement, Jonathan S. Shapiro, 23:13
  • Re: Challenge: Find potential use cases for non-trivial confinement, Jonathan S. Shapiro, 23:08
  • Re: bit-split, or: the schizophrenia of trusted computing, Pierre THIERRY, 23:02
  • Re: How to add confinement to the Hurd?, Pierre THIERRY, 22:49
  • Re: Challenge: Find potential use cases for non-trivial confinement, Marcus Brinkmann, 22:44
  • Re: bit-split, or: the schizophrenia of trusted computing, Marcus Brinkmann, 22:24
  • Re: bit-split, or: the schizophrenia of trusted computing, Jonathan S. Shapiro, 22:08
  • Re: How to add confinement to the Hurd?, Jonathan S. Shapiro, 21:52
  • Re: Challenge: Find potential use cases for non-trivial confinement, Jonathan S. Shapiro, 21:44
  • Re: Design principles and ethics, Marcus Brinkmann, 21:34
  • Re: bit-split, or: the schizophrenia of trusted computing, Pierre THIERRY, 21:24
  • Re: How to add confinement to the Hurd?, Marcus Brinkmann, 21:09
  • Re: Challenge: Find potential use cases for non-trivial confinement, Marcus Brinkmann, 20:44
  • Re: Design principles and ethics, Jonathan S. Shapiro, 20:20
  • Re: How to add confinement to the Hurd?, Jonathan S. Shapiro, 19:55
  • Re: The gun analogy (Was: Design Principles), Jonathan S. Shapiro, 19:50
  • Re: How to add confinement to the Hurd?, Marcus Brinkmann, 19:34
  • Re: The gun analogy (Was: Design Principles), Marcus Brinkmann, 19:24
  • Re: Challenge: Find potential use cases for non-trivial confinement, Jonathan S. Shapiro, 19:01
  • Re: Design principles and ethics, Jonathan S. Shapiro, 18:59
  • Re: Design principles and ethics, Marcus Brinkmann, 18:39
  • Re: Design principles and ethics, Marcus Brinkmann, 18:34
  • Re: How to add confinement to the Hurd?, Jonathan S. Shapiro, 18:24
  • Re: The gun analogy (Was: Design Principles), Jonathan S. Shapiro, 18:21
  • Re: Design principles and ethics, Jonathan S. Shapiro, 18:13
  • Re: Design principles and ethics, Jonathan S. Shapiro, 18:12
  • Re: The gun analogy (Was: Design Principles), Marcus Brinkmann, 17:59
  • Challenge: Find potential use cases for non-trivial confinement, Marcus Brinkmann, 17:19
  • Re: Physical access without ultimate power? (was Re: Design principles and ethics (was [...]))), Bas Wijnen, 16:50
  • Re: Design principles and ethics, Bas Wijnen, 16:49
  • Re: Design principles and ethics, Marcus Brinkmann, 16:44
  • Re: How to add confinement to the Hurd?, Marcus Brinkmann, 16:29
  • Re: The gun analogy (Was: Design Principles), Marcus Brinkmann, 16:24
  • Re: Design principles and ethics, Pierre THIERRY, 16:07
  • bit-split, or: the schizophrenia of trusted computing, Marcus Brinkmann, 15:39
  • Re: Design principles and ethics, Tom Bachmann, 15:25
  • Re: Design principles and ethics, Tom Bachmann, 15:21
  • Re: Design principles and ethics, Pierre THIERRY, 15:14
  • Re: Design principles and ethics, Jonathan S. Shapiro, 15:02
  • Re: The gun analogy (Was: Design Principles), Jonathan S. Shapiro, 14:58
  • Re: Design principles and ethics, Tom Bachmann, 14:48
  • Re: Design principles and ethics, Jonathan S. Shapiro, 14:46
  • How to add confinement to the Hurd?, Pierre THIERRY, 14:33
  • Physical access without ultimate power? (was Re: Design principles and ethics (was [...]))), Pierre THIERRY, 14:14
  • Re: Design principles and ethics, Bas Wijnen, 14:08
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Bas Wijnen, 14:01
  • Re: Design principles and ethics, Tom Bachmann, 13:58
  • Re: Design principles and ethics, Bas Wijnen, 13:52
  • Re: Design principles and ethics, Tom Bachmann, 13:18
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Bas Wijnen, 12:53
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Marcus Brinkmann, 11:54
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Marcus Brinkmann, 11:19
  • Re: The gun analogy (Was: Design Principles), Marcus Brinkmann, 10:59
  • Re: The gun analogy (Was: Design Principles), Marcus Brinkmann, 10:49
  • Re: Design principles and ethics, Tom Bachmann, 10:34
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 10:23
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 10:20
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Jonathan S. Shapiro, 10:18
  • Re: Design principles and ethics, Tom Bachmann, 10:11
  • Re: The gun analogy (Was: Design Principles), Tom Bachmann, 10:05
  • Re: The gun analogy (Was: Design Principles), Jonathan S. Shapiro, 10:04
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Jonathan S. Shapiro, 10:03
  • Re: The gun analogy (Was: Design Principles), Jonathan S. Shapiro, 10:00
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Marcus Brinkmann, 09:14
  • Re: Reliability of RPC services, Marcus Brinkmann, 08:29
  • Re: Reliability of RPC services, Marcus Brinkmann, 08:29
  • Re: Reliability of RPC services, Bas Wijnen, 06:25
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Bas Wijnen, 06:17
  • Adding contont to tho wiki, Tom Bachmann, 06:13
  • Re: The gun analogy (Was: Design Principles), Tom Bachmann, 05:45
  • Re: The gun analogy (Was: Design Principles), Peter 'p2' De Schrijver, 05:33
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Tom Bachmann, 04:41
  • Re: The gun analogy (Was: Design Principles), Tom Bachmann, 03:26
• April 29, 2006
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 22:24
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Jonathan S. Shapiro, 22:23
  • Re: Reliability of RPC services, Bas Wijnen, 22:04
  • Re: Reliability of RPC services, Bas Wijnen, 21:58
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 21:53
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Bas Wijnen, 21:52
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 21:50
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 21:48
  • Re: performance or anything that can replace it., Jonathan S. Shapiro, 21:46
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 21:28
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 21:26
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Jonathan S. Shapiro, 20:08
  • Re: The gun analogy (Was: Design Principles), Jonathan S. Shapiro, 19:47
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Bas Wijnen, 13:38
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Tom Bachmann, 13:28
  • Re: Design principles and ethics, Bas Wijnen, 13:20
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Bas Wijnen, 13:18
  • Re: Design principles and ethics, Tom Bachmann, 13:02
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Pierre THIERRY, 12:55
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Bas Wijnen, 08:22
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Pierre THIERRY, 06:49
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Bas Wijnen, 05:21
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Marcus Brinkmann, 05:16
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Jonathan S. Shapiro, 01:22
• April 28, 2006
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Pierre THIERRY, 22:02
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Pierre THIERRY, 13:15
  • Re: Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Pierre THIERRY, 13:07
  • Re: Backups vs. privacy (was Re: Directories traversal (was [...])), Pierre THIERRY, 12:55
  • Ethics (was: Re: Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Marcus Brinkmann, 10:54
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Marcus Brinkmann, 10:19
  • Re: Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Ludovic Courtès, 10:12
  • Re: Backups vs. privacy (was Re: Directories traversal (was [...])), Bas Wijnen, 09:42
  • Re: Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Pierre THIERRY, 09:25
  • Re: Design principles and ethics (was Re: Execute without read (was [...])), Bas Wijnen, 09:22
  • Backups vs. privacy (was Re: Directories traversal (was [...])), Pierre THIERRY, 08:56
  • Design principles and ethics (was Re: Execute without read (was [...])), Pierre THIERRY, 08:49
  • Re: Child killing UI (was Re: Reliability of RPC services), Jonathan S. Shapiro, 08:38
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Jonathan S. Shapiro, 08:36
  • Re: Child killing UI (was Re: Reliability of RPC services), Marcus Brinkmann, 08:34
  • Re: Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Marcus Brinkmann, 08:34
  • Re: Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Jonathan S. Shapiro, 08:34
  • Re: Child killing UI (was Re: Reliability of RPC services), Pierre THIERRY, 08:28
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Bas Wijnen, 08:08
  • Re: Child killing UI (was Re: Reliability of RPC services), Bas Wijnen, 08:04
  • Re: Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Bas Wijnen, 08:01
  • Re: Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Marcus Brinkmann, 07:59
  • Re: Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Marcus Brinkmann, 07:59
  • Re: Child killing UI (was Re: Reliability of RPC services), Pierre THIERRY, 07:53
  • Re: Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Bas Wijnen, 07:53
  • Re: Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Pierre THIERRY, 07:48
  • Re: Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Pierre THIERRY, 07:37
  • Re: Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Bas Wijnen, 06:13
  • Re: Child killing UI (was Re: Reliability of RPC services), Bas Wijnen, 05:34
• April 27, 2006
  • Re: Child killing UI (was Re: Reliability of RPC services), Marcus Brinkmann, 20:04
  • Re: Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Marcus Brinkmann, 20:04
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Jonathan S. Shapiro, 19:50
  • Re: Execute without read (was Re: the deadly hypercube of death, or: handling permissions), Marcus Brinkmann, 19:50
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Pierre THIERRY, 19:31
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Pierre THIERRY, 19:29
  • Re: Child killing UI (was Re: Reliability of RPC services), Pierre THIERRY, 19:27
  • Re: Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Pierre THIERRY, 19:20
  • Execute without read (was Re: the deadly hypercube of death, or: handling permissions), Pierre THIERRY, 19:14
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Jonathan S. Shapiro, 19:12
  • Re: the deadly hypercube of death, or: handling permissions, Jonathan S. Shapiro, 19:10
  • Re: Escaping it's parents (was Re: Process Management (was: Re: Reliability of RPC services)), Marcus Brinkmann, 19:09
  • Re: Child killing UI (was Re: Reliability of RPC services), Marcus Brinkmann, 18:59
  • Re: Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Marcus Brinkmann, 18:54
  • Re: the deadly hypercube of death, or: handling permissions, Marcus Brinkmann, 18:49
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Pierre THIERRY, 18:42
  • Escaping it's parents (was Re: Process Management (was: Re: Reliability of RPC services)), Pierre THIERRY, 18:41
  • Child killing UI (was Re: Reliability of RPC services), Pierre THIERRY, 18:38
  • Directories traversal (was Re: the deadly hypercube of death, or: handling permissions), Pierre THIERRY, 18:24
  • Re: Process Management (was: Re: Reliability of RPC services), Marcus Brinkmann, 17:19
  • Re: the deadly hypercube of death, or: handling permissions, Pierre THIERRY, 17:16
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Tom Bachmann, 16:15
  • Re: Process Management (was: Re: Reliability of RPC services), Jonathan S. Shapiro, 16:05
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Jonathan S. Shapiro, 16:00
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Jonathan S. Shapiro, 15:59
  • Process Management (was: Re: Reliability of RPC services), Marcus Brinkmann, 15:14
  • Re: Reliability of RPC services, Filip Brcic, 14:41
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Tom Bachmann, 14:25
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Pierre THIERRY, 13:41
  • Re: the deadly hypercube of death, or: handling permissions, Pierre THIERRY, 12:53
  • Re: Reliability of RPC services, Marcus Brinkmann, 12:49
  • Re: the deadly hypercube of death, or: handling permissions, Marcus Brinkmann, 12:39
  • Re: the deadly hypercube of death, or: handling permissions, Marcus Brinkmann, 12:34
  • Re: Reliability of RPC services, Bas Wijnen, 12:12
  • RE: the deadly hypercube of death, or: handling permissions, Christopher Nelson, 11:45
  • Re: the deadly hypercube of death, or: handling permissions, Pierre THIERRY, 11:41
  • Re: Reliability of RPC services, Michal Suchanek, 11:35
  • RE: Reliability of RPC services, Christopher Nelson, 11:00
  • Re: the deadly hypercube of death, or: handling permissions, Ludovic Courtès, 10:43
  • Re: the deadly hypercube of death, or: handling permissions, Tom Bachmann, 10:34
  • Re: the deadly hypercube of death, or: handling permissions, Ludovic Courtès, 10:24
  • Re: Reliability of RPC services, Michal Suchanek, 09:24
  • Re: the deadly hypercube of death, or: handling permissions, Marcus Brinkmann, 09:15
  • Re: the deadly hypercube of death, or: handling permissions, Marcus Brinkmann, 09:05
  • Re: the deadly hypercube of death, or: handling permissions, Jonathan S. Shapiro, 09:01
  • Re: the deadly hypercube of death, or: handling permissions, Marcus Brinkmann, 08:59
  • Re: the deadly hypercube of death, or: handling permissions, Ludovic Courtès, 08:59
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Jonathan S. Shapiro, 08:59
  • Re: the deadly hypercube of death, or: handling permissions, Pierre THIERRY, 08:46
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Pierre THIERRY, 08:33
  • Re: the deadly hypercube of death, or: handling permissions, Marcus Brinkmann, 08:24
  • Re: the deadly hypercube of death, or: handling permissions, Pierre THIERRY, 08:02
  • Re: the deadly hypercube of death, or: handling permissions, Marcus Brinkmann, 06:29
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Jonathan S. Shapiro, 06:29
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Pierre THIERRY, 05:41
  • Re: Reliability of RPC services, Pierre THIERRY, 05:22
  • Re: Cancellation forwarding protocol (was Re: Reliability of RPC services), Jonathan S. Shapiro, 05:17
  • Cancellation forwarding protocol (was Re: Reliability of RPC services), Pierre THIERRY, 05:12
  • Re: the deadly hypercube of death, or: handling permissions, Ludovic Courtès, 03:29
• April 26, 2006
  • Correctness (was: Re: Reliability of RPC services), olafBuddenhagen, 23:32
  • Re: Reliability of RPC services, Jesse D. McDonald, 21:36
  • Re: Reliability of RPC services, Marcus Brinkmann, 20:59
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 20:55
  • Re: Reliability of RPC services, Jesse D. McDonald, 20:40
  • Re: Reliability of RPC services, Marcus Brinkmann, 20:19
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 20:17
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 20:13
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 20:08
  • Re: Reliability of RPC services, Jesse D. McDonald, 20:05
  • RE: Reliability of RPC services, Christopher Nelson, 19:22
  • RE: Reliability of RPC services, Christopher Nelson, 19:16
  • RE: Reliability of RPC services, Christopher Nelson, 19:11
  • Re: Reliability of RPC services, Michal Suchanek, 18:58
  • Re: Reliability of RPC services, Marcus Brinkmann, 18:24
  • Re: Performance, olafBuddenhagen, 17:35
  • RE: Reliability of RPC services, Christopher Nelson, 16:57
  • Re: Reliability of RPC services, Bas Wijnen, 16:38
  • the deadly hypercube of death, or: handling permissions, Marcus Brinkmann, 15:14
  • Re: [Hurd-NG] Error in dir_rename pseudo-code, Marcus Brinkmann, 14:59
  • RE: Reliability of RPC services, Christopher Nelson, 14:49
  • Re: Reliability of RPC services, Bas Wijnen, 14:21
  • Re: Reliability of RPC services, Pierre THIERRY, 12:49
  • Re: Reliability of RPC services, Michal Suchanek, 12:44
  • RE: Reliability of RPC services, Christopher Nelson, 12:40
  • Re: Performance, Tom Bachmann, 12:28
  • Re: Reliability of RPC services, Pierre THIERRY, 12:06
  • RE: Reliability of RPC services, Christopher Nelson, 11:52
  • Re: Reliability of RPC services, Pierre THIERRY, 11:34
  • Re: [Hurd-NG] Error in dir_rename pseudo-code, Pierre THIERRY, 11:29
  • RE: Performance, Christopher Nelson, 10:46
  • Re: Performance, Ognyan Kulev, 10:31
  • RE: Reliability of RPC services, Christopher Nelson, 10:25
  • Re: [Hurd-NG] Error in dir_rename pseudo-code, Marcus Brinkmann, 08:54
  • Re: [Hurd-NG] Error in dir_rename pseudo-code, Pierre THIERRY, 08:09
  • Re: Reliability of RPC services, Michal Suchanek, 08:01
  • Re: [Hurd-NG] Missing in-argument in dir_get_entries, Marcus Brinkmann, 07:44
  • Re: [Hurd-NG] Error in dir_rename pseudo-code, Marcus Brinkmann, 07:44
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 07:44
  • Re: Reliability of RPC services, Marcus Brinkmann, 07:34
  • Re: Reliability of RPC services, Michal Suchanek, 05:08
  • Re: Reliability of RPC services, Michal Suchanek, 04:57
  • Re: Reliability of RPC services, Peter 'p2' De Schrijver, 04:20
  • Re: Reliability of RPC services, Bas Wijnen, 04:00
• April 25, 2006
  • [Hurd-NG] Missing in-argument in dir_get_entries, Pierre THIERRY, 22:18
  • [Hurd-NG] Error in dir_rename pseudo-code, Pierre THIERRY, 22:16
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 19:31
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 19:28
  • Re: Reliability of RPC services, Bas Wijnen, 17:57
  • Re: Reliability of RPC services, Bas Wijnen, 17:54
  • Re: Reliability of RPC services, Bas Wijnen, 17:50
  • Re: Reliability of RPC services, Bas Wijnen, 16:46
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 16:33
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 16:32
  • Re: Reliability of RPC services, Bas Wijnen, 16:06
  • Re: Reliability of RPC services, Tom Bachmann, 14:42
  • Re: Reliability of RPC services, Marcus Brinkmann, 14:09
  • RE: Reliability of RPC services, Christopher Nelson, 13:54
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 13:50
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 13:49
  • Re: Strange wording about io_t->io_map method, Pierre THIERRY, 13:29
  • Re: Reliability of RPC services, Pierre THIERRY, 13:07
  • Re: Reliability of RPC services, Pierre THIERRY, 13:06
  • Re: Reliability of RPC services, Pierre THIERRY, 13:02
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 12:56
  • Re: Reliability of RPC services, Pierre THIERRY, 12:48
  • Re: Reliability of RPC services, Marcus Brinkmann, 12:44
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 12:31
  • Re: Strange wording about io_t->io_map method, Marcus Brinkmann, 12:29
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 12:29
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 12:24
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 12:22
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 12:18
  • Re: Reliability of RPC services, Pierre THIERRY, 12:18
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 12:17
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 12:16
  • Re: Reliability of RPC services, Marcus Brinkmann, 12:14
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 12:12
  • RE: Reliability of RPC services, Christopher Nelson, 12:06
  • Re: Reliability of RPC services, Michal Suchanek, 11:47
  • Re: Reliability of RPC services, Pierre THIERRY, 11:42
  • Re: Reliability of RPC services, Marcus Brinkmann, 11:34
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 11:30
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 11:28
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 11:25
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 11:22
  • Re: Reliability of RPC services, Marcus Brinkmann, 11:09
  • Re: Reliability of RPC services, Marcus Brinkmann, 10:59
  • Re: Reliability of RPC services, Bas Wijnen, 10:51
  • Re: Reliability of RPC services, Bas Wijnen, 10:47
  • Re: Reliability of RPC services, Bas Wijnen, 10:25
  • Re: Reliability of RPC services, Bas Wijnen, 10:09
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 10:00
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 10:00
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 09:56
  • Re: Strange wording about io_t->io_map method, Tom Bachmann, 08:59
  • Re: Reliability of RPC services, Tom Bachmann, 08:45
  • Re: Reliability of RPC services, Michal Suchanek, 08:32
  • Re: Reliability of RPC services, Tom Bachmann, 08:08
  • Re: Strange wording about io_t->io_map method, Yoshinori K. Okuji, 08:06
  • Re: Reliability of RPC services, Bas Wijnen, 07:47
  • Re: Reliability of RPC services, Marcus Brinkmann, 07:19
  • Re: Reliability of RPC services, Marcus Brinkmann, 07:09
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 07:00
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 06:53
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 06:51
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 06:50
  • A few questions about the hurd-ng draft, Michal Suchanek, 06:33
  • Re: Reliability of RPC services, Bas Wijnen, 06:29
  • Re: Reliability of RPC services, Bas Wijnen, 06:22
  • Re: Strange wording about io_t->io_map method, Marcus Brinkmann, 06:19
  • Re: Reliability of RPC services, Michal Suchanek, 06:19
  • Re: Reliability of RPC services, Marcus Brinkmann, 06:10
  • Re: Reliability of RPC services, Bas Wijnen, 04:56
  • Re: Reliability of RPC services, Michal Suchanek, 04:38
  • Re: Reliability of RPC services, Michal Suchanek, 04:32
• April 24, 2006
  • Strange wording about io_t->io_map method, Pierre THIERRY, 22:49
  • Re: A short note on microkernels, Pierre THIERRY, 21:45
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 21:21
  • Re: A short note on microkernels, Jonathan S. Shapiro, 21:17
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 20:48
  • Re: Reliability of RPC services, Bas Wijnen, 18:46
  • Re: A short note on microkernels, Pierre THIERRY, 18:22
  • Re: Reliability of RPC services, Pierre THIERRY, 18:02
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 16:38
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 16:35
  • Re: Reliability of RPC services, Marcus Brinkmann, 16:35
  • Re: Reliability of RPC services, Tom Bachmann, 16:16
  • Re: Reliability of RPC services, Marcus Brinkmann, 16:05
  • Re: Reliability of RPC services, Tom Bachmann, 15:42
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 15:32
  • Re: Reliability of RPC services, Tom Bachmann, 14:46
  • Re: Reliability of RPC services, Marcus Brinkmann, 13:40
  • Re: Reliability of RPC services, Marcus Brinkmann, 13:35
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 12:16
  • Re: Reliability of RPC services, Michal Suchanek, 11:58
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 11:41
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 11:08
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 11:07
  • Re: Google's Summer of Code 2006, Thomas Schwinge, 10:40
  • Re: Google's Summer of Code 2006, Thomas Schwinge, 10:30
  • Re: Reliability of RPC services, Pierre THIERRY, 07:04
  • Re: Performance, Pierre THIERRY, 07:02
  • Re: Reliability of RPC services, Marcus Brinkmann, 05:16
  • Re: Reliability of RPC services, Bas Wijnen, 05:12
  • Re: Performance, Michal Suchanek, 05:07
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 00:39
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 00:24
• April 23, 2006
  • Re: Nurd-NG io_t, Marcus Brinkmann, 20:26
  • Nurd-NG io_t, Pierre THIERRY, 19:35
  • Re: performance or anything that can replace it., Tom Bachmann, 16:45
  • Re: Reliability of RPC services, Tom Bachmann, 16:44
  • Re: Performance, Tom Bachmann, 16:41
  • Re: Reliability of RPC services, Marcus Brinkmann, 16:16
  • Re: Reliability of RPC services, Tom Bachmann, 15:15
  • Re: Reliability of RPC services, Marcus Brinkmann, 15:05
  • Re: Reliability of RPC services, Marcus Brinkmann, 14:46
  • Re: Reliability of RPC services, Marcus Brinkmann, 14:32
  • Re: Reliability of RPC services, Marcus Brinkmann, 14:32
  • Re: Performance (was: Re: Is there any benchmark of coyotos vs. l4?), Marcus Brinkmann, 14:32
  • Re: Reliability of RPC services, Marcus Brinkmann, 14:07
  • Re: Reliability of RPC services, Marcus Brinkmann, 14:07
  • performance or anything that can replace it., MT Rezaie, 12:24
  • Performance (was: Re: Is there any benchmark of coyotos vs. l4?), olafBuddenhagen, 11:24
  • Re: Reliability of RPC services, Pierre THIERRY, 11:22
  • Re: Reliability of RPC services, Bas Wijnen, 06:50
  • Re: Reliability of RPC services, Tom Bachmann, 05:24
  • Re: Google's Summer of Code 2006, Gianluca Guida, 04:43
  • Re: Reliability of RPC services, Bas Wijnen, 04:37
• April 22, 2006
  • Re: Reliability of RPC services, Pierre THIERRY, 22:21
  • Re: Reliability of RPC services, Pierre THIERRY, 20:23
  • Re: Reliability of RPC services, Bas Wijnen, 18:31
  • Re: Reliability of RPC services, Bas Wijnen, 17:31
  • Re: Is there any benchmark of coyotos vs. l4?, Michal Suchanek, 16:43
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 14:06
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 13:57
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 13:53
  • Re: Reliability of RPC services, Marcus Brinkmann, 13:26
  • Re: Reliability of RPC services, Marcus Brinkmann, 13:22
  • Re: Reliability of RPC services, Pierre THIERRY, 11:53
  • Re: Reliability of RPC services, Pierre THIERRY, 11:39
  • Re: A short note on microkernels, Jonathan S. Shapiro, 11:11
  • Re: Google's Summer of Code 2006, Alexandre Buisse, 10:42
  • Re: A short note on microkernels, Pierre THIERRY, 10:33
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 10:22
  • Re: Google's Summer of Code 2006, Marco Gerards, 09:24
  • Re: Is there any benchmark of coyotos vs. l4?, Tom Bachmann, 08:26
  • Is there any benchmark of coyotos vs. l4?, MT Rezaie, 08:22
  • Re: A short note on microkernels, Tom Bachmann, 05:10
  • Re: Reliability of RPC services, Marcus Brinkmann, 04:31
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 00:40
• April 21, 2006
  • Re: Reliability of RPC services, Marcus Brinkmann, 21:55
  • Re: Reliability of RPC services, Marcus Brinkmann, 21:54
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 20:23
  • Re: Reliability of RPC services, Jonathan S. Shapiro, 20:16
  • Re: Reliability of RPC services, Marcus Brinkmann, 20:10
  • Re: A short note on microkernels, Jonathan S. Shapiro, 19:48
  • Reliability of RPC services, Marcus Brinkmann, 19:45
  • Re: A short note on microkernels, Alfred M. Szmidt, 18:45
  • A short note on microkernels, Marcus Brinkmann, 18:40
  • Re: hurd wiki buggered, Jonathan S. Shapiro, 15:36
  • hurd wiki buggered, Jonathan S. Shapiro, 15:32
  • A few questions about the hurd-ng draft, Michal Suchanek, 14:22
  • Re: New top-level category in HURD wiki, Pierre THIERRY, 08:16
• April 20, 2006
  • Google's Summer of Code 2006, Thomas Schwinge, 13:26
• April 19, 2006
  • Re: The Hurd wiki, Alfredo Beaumont, 08:03
• April 18, 2006
  • Re: The Hurd wiki, B. Douglas Hilton, 22:03
  • The Hurd wiki, Thomas Schwinge, 13:24
  • Re: Hurd and microkernels, Barry deFreese, 11:38
  • Re: Writing down design documents, Tom Bachmann, 11:29
  • Re: Hurd and microkernels, Tom Bachmann, 11:20
• April 17, 2006
  • Re: Hurd and microkernels (was: Re: A simple question), bahadir balban, 11:20
• April 15, 2006
  • Re: Hurd and microkernels, Kristoffer Nyborg Gregertsen, 18:37
  • Re: Hurd and microkernels (was: Re: A simple question), Pierre THIERRY, 16:00
  • Re: Writing down design documents, Pierre THIERRY, 10:27
  • Re: Hurd and microkernels (was: Re: A simple question), Jonathan S. Shapiro, 10:23
  • Re: A simple question, Bas Wijnen, 03:44
  • Re: A simple question, olafBuddenhagen, 00:05
  • Hurd and microkernels (was: Re: A simple question), olafBuddenhagen, 00:05
  • Re: A simple question, olafBuddenhagen, 00:05
• April 14, 2006
  • New top-level category in HURD wiki, Pierre THIERRY, 10:17
  • Re: Writing down design documents, Marcus Brinkmann, 10:10
  • Re: A simple question, Zbynek Michl, 08:13
  • Re: Writing down design documents, Jonathan S. Shapiro, 06:24
  • Re: Writing down design documents, Gustav van der Merwe, 04:53
  • Re: Writing down design documents, Thomas Schwinge, 04:42
  • Re: Writing down design documents, Bas Wijnen, 04:35
  • Re: Writing down design documents, Justin Emmanuel, 03:38
• April 13, 2006
  • Writing down design documents, Pierre THIERRY, 22:55
  • Re: A simple question, Jonathan S. Shapiro, 10:48
  • Re: A simple question, MT Rezaie, 08:20
  • Re: A simple question, Bas Wijnen, 04:27
• April 12, 2006
  • Re: A simple question, olafBuddenhagen, 20:44
  • Re: A simple question, olafBuddenhagen, 20:44
  • Re: A simple question, olafBuddenhagen, 20:44
  • Re: A simple question, Lluis, 08:24
  • Re: A simple question, Jouke Witteveen, 02:47
• April 11, 2006
  • Re: A simple question, Leonardo Pereira, 22:00
  • Re: A simple question, Wei Shen, 21:36
  • Re: A simple question, Tom Bachmann, 14:06
  • Re: A simple question, Bas Wijnen, 13:42
  • Re: A simple question, Espen Skoglund, 10:55
  • Re: A simple question, Matheus Morais, 10:52
  • Re: A simple question, Tom Bachmann, 10:48
  • RE: A simple question, Jayabalan_Aaron, 10:44
  • Re: A simple question, Matheus Morais, 10:15
  • Re: A simple question, Tom Bachmann, 07:33
  • Re: A simple question, Zbynek Michl, 06:31
• April 10, 2006
  • A simple question, Wei Shen, 21:39
• April 01, 2006
  • GNU Mach and L4 differences, Zbynek Michl, 09:04

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc