From: Brandon Low <lostlogic@gentoo.org>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: procps 2.x vs. procps 3.x
Date: Fri, 13 Dec 2002 16:10:49 -0600 [thread overview]
Message-ID: <20021213161049.D407@lostlogicx.com> (raw)
In-Reply-To: <200212131514.gBDFEhL268190@saturn.cs.uml.edu>; from acahalan@cs.uml.edu on Fri, Dec 13, 2002 at 10:14:43AM -0500
> If nobody else knows about it, it's not too likely to get fixed.
> Send bug reports to procps-feedback@lists.sf.net please.
>
Sorry about that, sent bug report and link to our bug track on it.
> Before you do: "certain characters" will need some explaining.
> (position? value? completely gone or turned into a space?)
In the bug report.
>
> > but the 3.x series is much prettier and
> > feature rich than the 2.x series. On the other hand, 2.x is
> > consistently more up to date with kernel changes since RML and Riel
> > maintain it and are intimately familiar with current kernel
> > development.
>
> I just got the last bit, /proc/*/wchan usage on 2.5.xx kernels.
> Oddly, I'm ahead right now. I have a vmstat that uses a fast O(1)
> algorithm on 2.5.xx kernels and reports the IO-wait time. I also
> have a sysctl that handles the 2.5.xx VLAN interfaces.
Amazing work, thanks! I hope to get your procps into Gentoo Stable RSN :)
--Brandon
next prev parent reply other threads:[~2002-12-13 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 15:14 procps 2.x vs. procps 3.x Albert D. Cahalan
2002-12-13 22:10 ` Brandon Low [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-13 1:53 Dan Kegel
2002-12-13 2:09 ` 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=20021213161049.D407@lostlogicx.com \
--to=lostlogic@gentoo.org \
--cc=acahalan@cs.uml.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox