web commit by http://madhusudancs.myvidoop.com/

1 files changed, 41 insertions, 7 deletions

diff --git a/community/procfs.mdwn b/community/procfs.mdwn
index a1b38eb5..093c3369 100644
--- a/community/procfs.mdwn
+++ b/community/procfs.mdwn
@@ -18,6 +18,8 @@ is included in the section entitled
 
 GNU/Linux compatible procfs pseudo-filesystem
 
+------
+
  Project Description
 ----
 I wish to provide a sophisticated procfs pseudo-filesystem to “the Hurd”. An implementation of /proc pseudo-filesystem already exists in hurdextras repository. After skimming through the code it is clear that it needs a lot 
@@ -27,34 +29,60 @@ so that its not only reliable and robust but also more importantly it is fully c
 The project thus aims at making the GNU/Linux process management tools  like top, sysctl, kill, 
 skill, nice, snice, pgrep, free, tload, uptime, fuser, killall, pidof, pstree, etc., to run out of the box.
 
+------
+
  Mentor
 ----
 
 Olaf Buddenhagen
 
+------
+
  Project Schedule
 ----
 
      1. Initial preparation and migration (Community Bonding Period: has already started – May 25th)
-This phase involves improving my translator programming skills by gaining hands-on experience in it and becoming well versed in it. I will also go through the Hurd code to understand its architecture in depth and will read documentations related to obtaining process related information in Hurd. This phase also involves the migration of existing procfs to use libnetfs.
+
+      This phase involves improving my translator programming skills by gaining
+      hands-on experience in it and becoming well versed in it. I will also go
+      through the Hurd code to understand its architecture in depth and will read
+      documentations related to obtaining process related information in Hurd.
+      This phase also involves the migration of existing procfs to use libnetfs.
 
      2. Analysis and Design (May 26th – June 11th )
-This phase involves the analysis of previous migration. Also involves interacting with the mentor, the Hurd community and other people involved in development of ps. tools to draw the exact design of the proposed procfs including the algorithms required for coding.
+      This phase involves the analysis of previous migration. Also involves 
+      interacting with the mentor, the Hurd community and other people involved
+      in development of ps. tools to draw the exact design of the proposed procfs
+      including the algorithms required for coding.
 
      3.  Coding Stage I (June 12th – June 22nd )
-Finishing up the migration to libnetfs based on the finalized design and making necessary changes to the  existing procfs. Coding up to /proc/<pid>/exe in the features list.
+      Finishing up the migration to libnetfs based on the finalized design and
+      making necessary changes to the  existing procfs. Coding up to
+      /proc/<pid>/exe in the features list.
 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.&nbsp;Coding Stage II (June 23rd – July 13th)
-Involves coding of the features from /proc/<pid>/environ, up to /proc/<pid>/maps. These contain most of the information required for ps. tools and hence form the heart of the project. Will be completed by mid-term evaluation deadline.
+      Involves coding of the features from /proc/<pid>/environ, up to 
+      /proc/<pid>/maps. These contain most of the information required for ps.
+      tools and hence form the heart of the project. Will be completed by
+      mid-term evaluation deadline.
 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5. &nbsp;Coding Stage III (July 14th – July 26th )
-Coding the rest of the features in the list including any necessary features that may be added in the analysis phase.
+      Coding the rest of the features in the list including any necessary
+      features that may be added in the analysis phase.
 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6. &nbsp;Final Testing and evaluation (July 27th – August 8th )
-Closely interacting with the community and requesting them to help me in overall testing and reviewing and making changes as per their suggestions. Also involves testing with the ps. tools and consolidating the documentation.
+      Closely interacting with the community and requesting them to help me
+      in overall testing and reviewing and making changes as per their 
+      suggestions. Also involves testing with the ps. tools and consolidating 
+      the documentation.
 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7. &nbsp;Packaging and Wrap-up (August 9th - August 18th )
-Final phase of testing and fixing remaining bugs. Working with the community to merge the project with the CVS HEAD of Hurd. Documentation reviews, making necessary changes as per the suggestions and wrapping up the documentation.
+      Final phase of testing and fixing remaining bugs. Working with the
+      community to merge the project with the CVS HEAD of Hurd. Documentation
+      reviews, making necessary changes as per the suggestions and wrapping 
+      up the documentation.
+
+------
 
  Deliverables
 ----
@@ -65,6 +93,8 @@ Final phase of testing and fixing remaining bugs. Working with the community to
 Non-code deliverables include an exhaustive Documentation. This documents the code of the Hurd's procfs which explains in detail the implementation of each of the functionalities of procfs implemented
 during the course of this project.
 
+------
+
  Code Repository
 ----
 
@@ -72,6 +102,8 @@ during the course of this project.
 
 Clone URL: [git://github.com/madhusudancs/procfs.git](git://github.com/madhusudancs/procfs.git)
 
+------
+
  Progress
 ----
 
@@ -84,6 +116,8 @@ Clone URL: [git://github.com/madhusudancs/procfs.git](git://github.com/madhusuda
 1. [http://www.gnu.org/software/hurd/hacking-guide/hhg.html Hurd Hacking Guide (Have mainly concentrated on Translators Section)]
 2. [http://users.sosdg.org/~qiyong/lxr/source/Documentation/filesystems/proc.txt Linux Kernel Implementation of procfs]
 
+------
+
  Contact Details
 ----