summaryrefslogtreecommitdiff
path: root/community
diff options
context:
space:
mode:
authorantrik <antrik@users.sf.net>2008-03-31 04:11:12 +0200
committerantrik <antrik@users.sf.net>2008-03-31 04:11:12 +0200
commit6a6c674e9cee08bfc34687ef98cf58041f7d83ad (patch)
tree66b07c429a08bc7e31c498845bbbf406f4fd99f7 /community
parent75d586636700e5808966db41f6a9db26e40797e0 (diff)
(procfs) Readded list of examples for tools using procfs
Diffstat (limited to 'community')
-rw-r--r--community/gsoc/project_ideas.mdwn3
1 files changed, 2 insertions, 1 deletions
diff --git a/community/gsoc/project_ideas.mdwn b/community/gsoc/project_ideas.mdwn
index 3e453c62..7f3feb8c 100644
--- a/community/gsoc/project_ideas.mdwn
+++ b/community/gsoc/project_ideas.mdwn
@@ -245,7 +245,8 @@ locking works on the Hurd. Only general programming skills are required.
Although there is no standard (POSIX or other) for the layout of the `/proc`
pseudo-filesystem, it turned out a very useful facility in GNU/Linux and other
-systems, and many tools concerned with process management use it.
+systems, and many tools concerned with process management use it. (`ps`, `top`,
+`htop`, `gtop`, `killall`, `pkill`, ...)
Instead of porting all these tools to use [[hurd/libps]] (Hurd's official method for
accessing process information), they could be made to run out of the box, by