From owner-freebsd-questions Tue Feb 4 8: 1:20 2003 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 0958737B401 for ; Tue, 4 Feb 2003 08:01:19 -0800 (PST) Received: from mired.org (ip68-97-54-220.ok.ok.cox.net [68.97.54.220]) by mx1.FreeBSD.org (Postfix) with SMTP id 8D3E343F79 for ; Tue, 4 Feb 2003 08:01:14 -0800 (PST) (envelope-from mwm-dated-1044806469.1eb766@mired.org) Received: (qmail 73902 invoked from network); 4 Feb 2003 16:01:09 -0000 Received: from localhost.mired.org (HELO guru.mired.org) (127.0.0.1) by localhost.mired.org with SMTP; 4 Feb 2003 16:01:09 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15935.58308.600228.379186@guru.mired.org> Date: Tue, 4 Feb 2003 10:01:08 -0600 To: "Doug Reynolds" Cc: "freebsd-questions@FreeBSD.ORG" Subject: Re: Determining Ram In-Reply-To: <20030204044422.73BD248463@wastegate.net> References: <15933.52662.836585.531311@guru.mired.org> <20030204044422.73BD248463@wastegate.net> X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: Mike Meyer X-Delivery-Agent: TMDA/0.68 (Shut Out) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In <20030204044422.73BD248463@wastegate.net>, Doug Reynolds typed: > On Sun, 2 Feb 2003 20:02:30 -0600, Mike Meyer wrote: > >In <3E3DBFAE.BDCF0D25@djl.co.uk>, David Larkin typed: > >> Dragoncrest wrote: > >> > I've got a rather odd question, but I'm looking for the easiest way to > >> > determin how much ram I have on a given system without rebooting it. I'm > >> > sure that there is some kind of console command that tells me that info, > >> > but I have no idea where to begin looking to find out. Does anybody > >> > know? Thanks. > >> use the command dmesg > >It may no longer be available there. The dmesg at boot time is > >preserved in /var/run/dmesg.boot. The information should be there, > >even if it's gone from dmesg. > thats is kinda of odd, is that with 5.0-release? > any clues on why? That's with any version of FreeBSD. And the kernel dmesg buffer is only so big. As other messages come in, older ones get flushed. SO if you've been up long enough, you can lose the original boot messages. If you boot single user and work there before going multiuser, you can lose them in /var/run/dmesg.boot, even. http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message