I confess to submitting the patch to Linus to remove the compatability
lines when 2.5.0 was created.
The change that made the first two lines redundant was originally made in
1.3.68[1], and the intention was that they would removed -- the comment
in get_meminfo had:
Tagged format, for easy grepping and expansion. The above will go away
eventually, once the tools have been updated.
As I had an application that parsed /proc/meminfo around the time of
the change, I wrote the parser to handle the new format in preparation
for the old format going away. Others would have done the same.
Someone mentioned that this compatability was still present during
2.4 development, so I made a mental note to submit a patch when 2.5
development started.
> I'm a firm believer that adding something new to a system should
> never break existing functionality unless absolutely necessary. Was it
> necessary in this case, or was it done because someone was offended that
> it wasn't "clean" enough?
Where possible, interfaces should not be changed for the sake of change,
but you shouldn't keep old interfaces because that way lies bloat.
One of the beauties of Linux (IMO) is that broken interfaces don't have
to be maintained ad-infinitum. It should be expected that interfaces
may be broken during the development series of kernels, and the tools
have a chance to catch up during this cycle.
The interface that gtop (implicitly) required is that "Swap:" should be
the 3rd line in /proc/meminfo. You'll never get anyone to admit that
this is the interface to /proc/meminfo that should be maintained.
-
[1] http://groups.google.com/groups?selm=4glagm%24pno%40treflan.shout.net
-- `O O' | Nick.Holloway@pyrites.org.uk // ^ \\ | http://www.pyrites.org.uk/ - 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/