From: Dan Kegel <dkegel@ixiacom.com>
To: linux-kernel@vger.kernel.org
Subject: procps 2.x vs. procps 3.x
Date: Thu, 12 Dec 2002 17:53:13 -0800 [thread overview]
Message-ID: <3DF93D89.3000704@ixiacom.com> (raw)
Albert Cahalan wrote in message "[ANNOUNCE] procps 3.1.3":
> This release includes user selection in top, the sysctl -e
> option needed to support the Red Hat 8.0 boot scripts, and
> the use of /proc/*/wchan on recent 2.5.xx kernels.
>
> For those of you still upgrading from procps 2.0.xx releases,
> you can expect:
> ...
> There's a procps-feedback@lists.sf.net mailing list you can
> use for feature requests, bug reports, and so on. Use it!
and
Robert Love wrote in message "[announce] procps 2.0.11":
> Rik and I are pleased to announce version 2.0.11 of procps, the package
> that contains ps, top, free, vmstat, etc.
>
> Newer versions of procps are required for 2.5 kernels.
> ...
>
> Procps discussion, bugs, and patches are welcome at:
> procps-list@redhat.com
Which one should distributions use?
Or is that a matter of taste?
- Dan
next reply other threads:[~2002-12-13 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 1:53 Dan Kegel [this message]
2002-12-13 2:09 ` procps 2.x vs. procps 3.x Brandon Low
-- strict thread matches above, loose matches on Subject: below --
2002-12-13 15:14 Albert D. Cahalan
2002-12-13 22:10 ` Brandon Low
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DF93D89.3000704@ixiacom.com \
--to=dkegel@ixiacom.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.