diff options
| author | antrik <antrik@users.sf.net> | 2009-03-10 21:35:18 +0100 |
|---|---|---|
| committer | antrik <antrik@users.sf.net> | 2009-03-10 23:56:56 +0100 |
| commit | 297c7451dbf7ae312e7785f3aeb107c8d220b815 (patch) | |
| tree | fbd3244b986fe7ae6a34d3a32eb525383918f826 | |
| parent | e5074632db9e87f39a57298ce2a9537f50113ac5 (diff) | |
Network stack GSoC task: Fix sentence
| -rw-r--r-- | community/gsoc/project_ideas/tcp_ip_stack.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/community/gsoc/project_ideas/tcp_ip_stack.mdwn b/community/gsoc/project_ideas/tcp_ip_stack.mdwn index b8fb76df..b1a2536f 100644 --- a/community/gsoc/project_ideas/tcp_ip_stack.mdwn +++ b/community/gsoc/project_ideas/tcp_ip_stack.mdwn @@ -14,7 +14,7 @@ The Hurd presently uses a [[TCP/IP_stack|hurd/translator/pfinet]] based on code This works, but lacks some rather important features (like PPP/PPPoE), and the design is not hurdish at all. -A true hurdish network stack will use a set of stack of [[hurd/translator]] processes, +A true hurdish network stack will use a set of [[hurd/translator]] processes, each implementing a different protocol layer. This way not only the implementation gets more modular, but also the network stack can be used way more flexibly. Rather than just having the standard socket interface, plus some |