Date: Tue, 4 Feb 2003 08:04:10 +0100 From: Roman Neuhauser <neuhauser@bellavista.cz> To: Doug Reynolds <mav@wastegate.net> Cc: Mike Meyer <mwm-dated-1044669751.969bbb@mired.org>, "freebsd-questions@FreeBSD.ORG" <freebsd-questions@FreeBSD.ORG> Subject: Re: Determining Ram Message-ID: <20030204070410.GG393@freepuppy.bellavista.cz> In-Reply-To: <20030204044422.73BD248463@wastegate.net> References: <15933.52662.836585.531311@guru.mired.org> <20030204044422.73BD248463@wastegate.net>
next in thread | previous in thread | raw e-mail | index | archive | help
# mav@wastegate.net / 2003-02-03 23:44:06 -0500:
> On Sun, 2 Feb 2003 20:02:30 -0600, Mike Meyer wrote:
>
> >In <3E3DBFAE.BDCF0D25@djl.co.uk>, David Larkin <David.Larkin@djl.co.uk> 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?
RELENG_4 does this, too. the system message buffer is not of
infinite length.
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030204070410.GG393>