From: venom@sns.it
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Rik van Riel <riel@conectiva.com.br>, <procps-list@redhat.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] procps 2.0.10
Date: Tue, 8 Oct 2002 18:19:53 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.43.0210081817260.5654-100000@cibs9.sns.it> (raw)
In-Reply-To: <20021008144328.GC1560@werewolf.able.es>
libgpm is present because your libncurses has been
linked with it.
you can use -lcurses -ltermcap insted (if you have old curses installed)
On Tue, 8 Oct 2002, J.A. Magallon wrote:
> Date: Tue, 8 Oct 2002 16:43:28 +0200
> From: J.A. Magallon <jamagallon@able.es>
> To: Rik van Riel <riel@conectiva.com.br>
> Cc: procps-list@redhat.com, linux-kernel@vger.kernel.org
> Subject: Re: [ANNOUNCE] procps 2.0.10
>
>
> On 2002.10.08 Rik van Riel wrote:
> >On Tue, 8 Oct 2002, J.A. Magallon wrote:
> >
> >> It also kills the 'states' part, things are beginning to spread past 80
> >> columns...is it very important ?
> >
> >Yes, things should stay within 80 lines.
> >
>
> You can also kill the commas ',', they look not so important:
>
> CPU0: 0,0% user 0,0% system 0,0% nice 0,0% iowait 100,0% idle
> CPU1: 0,4% user 0,3% system 0,0% nice 0,0% iowait 98,3% idle
>
> >> I am gettin also strange outputs sometimes, with a ton of digits in
> >> decimal parts.
> >
> >Wait... I remember fixing that bug. On 2.4 kernels iowait
> >should always be 0.0% and it always is 0.0% here.
> >
> >I have no idea why it's displaying a wrong value on your
> >system, unless you somehow managed to run against a wrong
> >libproc.so (shouldn't happen).
> >
>
> werewolf:/lib# which top
> /usr/bin/top
> werewolf:/lib# ldd `which top`
> libproc.so.2.0.10 => /lib/libproc.so.2.0.10 (0x1557b000)
> libncurses.so.5 => /lib/libncurses.so.5 (0x15589000)
> libc.so.6 => /lib/i686/libc.so.6 (0x155ce000)
> libgpm.so.1 => /usr/lib/libgpm.so.1 (0x156ee000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x15556000)
>
> ???
>
> Will take a look.
>
> By.
>
> --
> J.A. Magallon <jamagallon@able.es> \ Software is like sex:
> werewolf.able.es \ It's better when it's free
> Mandrake Linux release 9.0 (dolphin) for i586
> Linux 2.4.20-pre9-jam1 (gcc 3.2 (Mandrake Linux 9.0 3.2-1mdk))
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-10-08 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 13:35 [ANNOUNCE] procps 2.0.10 Rik van Riel
2002-10-08 14:31 ` J.A. Magallon
2002-10-08 14:38 ` Rik van Riel
2002-10-08 14:43 ` J.A. Magallon
2002-10-08 16:19 ` venom [this message]
2002-10-08 14:53 ` J.A. Magallon
2002-10-08 15:05 ` Rik van Riel
2002-10-08 16:02 ` J.A. Magallon
2002-10-08 16:46 ` Rik van Riel
2002-10-08 15:31 ` J.A. Magallon
2002-10-11 3:50 ` Brandon Low
2002-10-11 4:04 ` Alexander Viro
2002-10-11 13:54 ` Rik van Riel
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=Pine.LNX.4.43.0210081817260.5654-100000@cibs9.sns.it \
--to=venom@sns.it \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=procps-list@redhat.com \
--cc=riel@conectiva.com.br \
/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;
as well as URLs for NNTP newsgroup(s).