From owner-freebsd-questions@FreeBSD.ORG Sat May 21 14:52:05 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 443F216A4CE for ; Sat, 21 May 2005 14:52:05 +0000 (GMT) Received: from mail23.sea5.speakeasy.net (mail23.sea5.speakeasy.net [69.17.117.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFF7743D77 for ; Sat, 21 May 2005 14:52:04 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 16218 invoked from network); 21 May 2005 14:52:04 -0000 Received: by simscan 1.1.0 ppid: 16198, pid: 16211, t: 0.1865s scanners: clamav: 0.84/m:31/d:888 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail23.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 21 May 2005 14:52:04 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 843DB30; Sat, 21 May 2005 10:52:03 -0400 (EDT) Sender: lowell@be-well.ilk.org To: "Chad Leigh -- Shire.Net LLC" References: <8124D4F3-3F79-4C42-B16E-7E617A5AA7D1@shire.net> From: Lowell Gilbert Date: 21 May 2005 10:52:03 -0400 In-Reply-To: <8124D4F3-3F79-4C42-B16E-7E617A5AA7D1@shire.net> Message-ID: <44wtpsocmk.fsf@be-well.ilk.org> Lines: 10 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: bsd Subject: Re: any way to tell memory config of a machine? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 May 2005 14:52:05 -0000 "Chad Leigh -- Shire.Net LLC" writes: > I was wondering if there was any way to tell the memory configuration > of a server running FBSD 5 (while running). By this I mean: can I > tell if 2GB is 2x1GB or 4x512MB etc? Obviously I can shut it down > and either look at the BIOS or physically look inside, but I would > rather not do that. With most systems, there is no way to do this. On many, there isn't even a way for the BIOS to tell...