From owner-freebsd-questions@FreeBSD.ORG Wed Dec 6 19:22:31 2006 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DC25C16A557 for ; Wed, 6 Dec 2006 19:22:31 +0000 (UTC) (envelope-from gibblertron@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id D762743CED for ; Wed, 6 Dec 2006 19:00:27 +0000 (GMT) (envelope-from gibblertron@gmail.com) Received: by py-out-1112.google.com with SMTP id f31so155190pyh for ; Wed, 06 Dec 2006 11:01:05 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=WlV8sA9+mOGq7uIf+66tksz2Q+DASHGbw994WaBODUQtqSdm2qsxZHhTk4XAGLeX2CLXQi8vIokFilcROceJH7jqLhTD5FhAp9cQlZxqQiwqetvN3Xsn9/XkYHVzj22h3JlES9ro+pP/UxwjtNT22VDmtd5Fcg3tfVgYQCG8Uiw= Received: by 10.78.201.15 with SMTP id y15mr805742huf.1165431664132; Wed, 06 Dec 2006 11:01:04 -0800 (PST) Received: by 10.78.13.3 with HTTP; Wed, 6 Dec 2006 11:00:58 -0800 (PST) Message-ID: Date: Wed, 6 Dec 2006 11:00:58 -0800 From: patrick To: questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Any way to tell what the RAM configuration is? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 19:22:32 -0000 I'm wondering if there's any way in FreeBSD (4.x on i386) to tell what the RAM configuration in the system is? ie. Can it show me if I have four 256MB modules versus two 512MB's? Obviously it would be possible to just open up the computer and see for my self, I'm hoping I can save myself a trip and wrecking an uptime of 670 days. :) Thanks, Patrick