From owner-freebsd-hackers  Mon Nov 27 01:33:46 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id BAA17351
          for hackers-outgoing; Mon, 27 Nov 1995 01:33:46 -0800
Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA17345
          for <hackers@freebsd.org>; Mon, 27 Nov 1995 01:33:44 -0800
Received: (from mrcpu@localhost) by schizo.cdsnet.net (8.6.12/8.6.9) id BAA05580; Mon, 27 Nov 1995 01:33:42 -0800
Date: Mon, 27 Nov 1995 01:33:42 -0800 (PST)
From: Jaye Mathisen <mrcpu@cdsnet.net>
To: hackers@freebsd.org
Subject: Why doesn't wc -c < /dev/mem work?
Message-ID: <Pine.BSD/.3.91.951127013229.27732f-100000@schizo.cdsnet.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
Precedence: bulk



I realize the info can be gotten by sysctl, but as I recall, the above is 
a time-honored technique for sizing RAM...

Frankly, I don't really care if it works, I'm just curious as to why it 
seems to have an infinite source of data.  Or maybe /dev/mem doesn't mean 
what it used to...