From 3f98ec59e0c6287c50cbe34d5df8e69ffd28d754 Mon Sep 17 00:00:00 2001
From: antrik <antrik@users.sf.net>
Date: Thu, 12 Mar 2009 08:18:17 +0100
Subject: secure chroot GSoC task: Add links to ideas/discussions

---
 community/gsoc/project_ideas/secure_chroot.mdwn | 5 +++++
 1 file changed, 5 insertions(+)

(limited to 'community/gsoc')

diff --git a/community/gsoc/project_ideas/secure_chroot.mdwn b/community/gsoc/project_ideas/secure_chroot.mdwn
index f091527a..f5c744e2 100644
--- a/community/gsoc/project_ideas/secure_chroot.mdwn
+++ b/community/gsoc/project_ideas/secure_chroot.mdwn
@@ -23,6 +23,11 @@ translator mechanism.  Some involving a completely different approch to
 `chroot` implementation, using a proxy instead of a special system call in the
 filesystem servers.
 
+See <http://tri-ceps.blogspot.com/2007/07/theory-of-filesystem-relativity.html>
+for some suggestions, as well as the followup discussions on
+<http://lists.gnu.org/archive/html/gnu-system-discuss/2007-09/msg00118.html>
+and <http://lists.gnu.org/archive/html/bug-hurd/2008-03/msg00089.html>.
+
 The task is to pick and implement one approach for fixing chroot.
 
 This task is pretty heavy: it requires a very good understanding of file name
-- 
cgit v1.2.3