From: Nick.Holloway@pyrites.org.uk (Nick Holloway)
To: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.5.17
Date: 22 May 2002 12:49:59 +0100 [thread overview]
Message-ID: <acg0l7$klk$1@alfie.demon.co.uk> (raw)
In-Reply-To: <86256BC1.001146A6.00@smtpnotes.altec.com>
In <86256BC1.001146A6.00@smtpnotes.altec.com> Wayne.Brown@altec.com writes:
> I can live with not building, crashing, or even eating filesystems. Those
> things will be fixed sooner or later. But breaking userspace programs -- that
> may well be permanent.
Looking at the source code to libgtop-1.0.6 (the version I have
easy access to), the parser used to extract the swap information from
/proc/meminfo is extremely fragile (read: broken). Rather than looking
at the tag at the start of each line for the one it requires, it assumes
that the "Swap:" details are on the 3rd line (and doesn't even verify
the label).
You can't expect the kernel to keep compatability for such poor user-space
code (especially during a development cycle).
The change to /proc/meminfo came about in 2.5.1, and this removed
the first two lines from the old, inflexible layout (that has been
deprecated for a while, and should probably been removed during the
2.1.x development cycle).
--
`O O' | Nick.Holloway@pyrites.org.uk
// ^ \\ | http://www.pyrites.org.uk/
next prev parent reply other threads:[~2002-05-22 11:50 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 3:02 Linux-2.5.17 Wayne.Brown
2002-05-22 7:12 ` Linux-2.5.17 Zwane Mwaikambo
2002-05-22 11:49 ` Nick Holloway [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-22 20:00 Linux-2.5.17 Wayne.Brown
2002-05-23 12:17 ` Linux-2.5.17 Nick Holloway
2002-05-21 23:20 Linux-2.5.17 Wayne.Brown
2002-05-21 23:29 ` Linux-2.5.17 Russell King
2002-05-21 23:33 ` Linux-2.5.17 Joel Jaeggli
2002-05-21 18:52 Linux-2.5.17 Wayne.Brown
2002-05-21 21:30 ` Linux-2.5.17 David S. Miller
2002-05-22 7:36 ` Linux-2.5.17 Helge Hafting
2002-05-21 5:16 Linux-2.5.17 Linus Torvalds
2002-05-21 13:58 ` Linux-2.5.17 Roman Zippel
2002-05-21 16:06 ` Linux-2.5.17 Linus Torvalds
2002-05-21 18:36 ` Linux-2.5.17 Roman Zippel
2002-05-21 18:53 ` Linux-2.5.17 Linus Torvalds
2002-05-21 23:35 ` Linux-2.5.17 Roman Zippel
2002-05-22 0:10 ` Linux-2.5.17 Linus Torvalds
2002-05-22 0:31 ` Linux-2.5.17 Roman Zippel
2002-05-22 0:54 ` Linux-2.5.17 Linus Torvalds
2002-05-22 2:17 ` Linux-2.5.17 David S. Miller
2002-05-22 2:40 ` Linux-2.5.17 Linus Torvalds
2002-05-22 2:57 ` Linux-2.5.17 David S. Miller
2002-05-22 3:21 ` Linux-2.5.17 Linus Torvalds
2002-05-22 8:06 ` Linux-2.5.17 David Lang
2002-05-22 14:14 ` Linux-2.5.17 Dave McCracken
2002-05-22 16:10 ` Linux-2.5.17 Linus Torvalds
2002-05-22 13:45 ` Linux-2.5.17 Roman Zippel
2002-05-22 16:08 ` Linux-2.5.17 Linus Torvalds
2002-05-22 10:54 ` Linux-2.5.17 Martin Dalecki
2002-05-22 12:04 ` Linux-2.5.17 Alexander Viro
2002-05-22 13:07 ` Linux-2.5.17 Martin Dalecki
2002-05-22 14:38 ` Linux-2.5.17 Alexander Viro
2002-05-22 13:42 ` Linux-2.5.17 Martin Dalecki
2002-05-22 16:55 ` Linux-2.5.17 Jan Kara
2002-05-22 12:14 ` Linux-2.5.17 Russell King
2002-05-22 12:36 ` Linux-2.5.17 Martin Dalecki
2002-05-22 16:02 ` Linux-2.5.17 Linus Torvalds
2002-05-22 15:04 ` Linux-2.5.17 Martin Dalecki
2002-05-22 16:58 ` Linux-2.5.17 Jan Kara
2002-05-22 16:08 ` Linux-2.5.17 Martin Dalecki
2002-05-22 17:56 ` Linux-2.5.17 Jan Kara
2002-05-22 16:56 ` Linux-2.5.17 Martin Dalecki
2002-05-22 18:17 ` Linux-2.5.17 Jan Kara
2002-05-22 18:36 ` Linux-2.5.17 Russell King
2002-05-22 13:06 ` Linux-2.5.17 Alan Cox
2002-05-22 11:19 ` Linux-2.5.17 Russell King
2002-05-22 11:27 ` Linux-2.5.17 David S. Miller
2002-05-22 16:23 ` Linux-2.5.17 Linus Torvalds
2002-05-24 13:59 ` Linux-2.5.17 Martin Dalecki
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='acg0l7$klk$1@alfie.demon.co.uk' \
--to=nick.holloway@pyrites.org.uk \
--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
all inboxes | Powered by JetHome®