At 01:20 AM 12/30/99 EST, [EMAIL PROTECTED] wrote [in part]:
>
>I'm not so clear on the distinction of buffers/cache. Could cached
>refer to disused programs waiting to be rerun again? In a just world,
>it would be described in man 5 proc, the section on meminfo, but my man
>pages were written in the dark ages, when buffers was the last entry.
>I'll see if I can find it when I find space to put Slackware 7 - it's
>not on the live CD.
Don't hope for much ... my reasonably up-to-date Debian systems still have a
1996 man page for proc and a 1993 one for free. proc really just refers you
to free for the details, and the details in free are uninformative. Pfui!
I'd love to see a clear explanation of what this means -- I kind of believe
my explanation, but I'm not sure. (BTW, my explanation and your guess about
cached are the same - I think "disused" is a succinct Britishism for what I
tried to say in many more words. That is, I *think* buffers hold the
contents of files that were read as data, and cache holds the contents of
files that were executed (i.e., programs).)
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
