emo/procps
1
0
Fork 0
Code Issues Pull Requests Packages Releases Activity

adapt redhat FAQ for procps-ng

Browse Source
This commit is contained in:
jimmy jam 2011-10-04 12:17:23 -05:00 committed by Sami Kerola
parent ee2e674182
commit d73bd233ca
1 changed files with 22 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
FAQ
View File

@ -57,7 +57,7 @@ without that you will see a single-node view.
Where to I send bug reports?
You may use the Debian bug tracking system or send your report to
procps-feedback@lists.sf.net (no subscription required) instead.
procps@freelists.org (no subscription required) instead.
Why are there so many procps projects?
@ -68,10 +68,27 @@ wrote a new ps program for the package. For the next few years, Albert quietly
helped the Debian package maintainer fix bugs. In 2001, Rik van Riel decided to
do something about what appeared to be the lack of a maintainer. He picked up
the buggy old code in Red Hat's CVS and started adding patches. Meanwhile,
other people have patched procps in a great many ways. In 2002, Albert moved
procps to this site. This was done to ensure that years of testing and bug
fixes would not be lost. The major version number was changed to 3, partly to
avoid confusing users and partly because the top program has been redone.
other people have patched procps in a great many ways.
In 2002, Albert moved procps to http://procps.sourceforge.net. This was done to
ensure that years of testing and bug fixes would not be lost. The major version
number was changed to 3, partly to avoid confusing users and partly because the
top program had been redone.
After development essentially stopped on sourceforge.net, in 2011 the project
found a new home at http://gitorious.org/procps. This represents the Debian,
Fedora and openSUSE fork of procps. To avoid confusion and potential name
clashes the package is now known as procps-ng (next generation), the version
number was raised to 3.3.0 and the library soname changed to libproc-ng-3.3.0.
What is being done to procps-ng at its new home?
All programs are in the process of being modernized, both in terms of coding
style and supporting documentation. Autotools have been integrated and the
library API has been expanded with many new fields supported such as control
groups, supplementary groups, etc. The top program has been rewritten offering
many new capabilities while providing performance improvements up to 300%.
Why does ps get signal 17?