From owner-freebsd-current Fri Apr 14 19:17:33 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA22329 for current-outgoing; Fri, 14 Apr 1995 19:17:33 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA22314 for ; Fri, 14 Apr 1995 19:17:21 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id TAA02308; Fri, 14 Apr 1995 19:14:29 -0700 From: "Rodney W. Grimes" Message-Id: <199504150214.TAA02308@gndrsh.aac.dev.com> Subject: Re: Interesting (and odd) effect in -current To: davidg@Root.COM Date: Fri, 14 Apr 1995 19:14:28 -0700 (PDT) Cc: phk@ref.tfs.com, cmf@ins.infonet.net, current@FreeBSD.org In-Reply-To: <199504150204.TAA00579@corbin.Root.COM> from "David Greenman" at Apr 14, 95 07:04:43 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 670 Sender: current-owner@FreeBSD.org Precedence: bulk > > >But I have digressed, if the BIOS didn't manage to get this write at > >power on, you would get NMI interrupts no matter what OS you ran. I > >don't see a reason to add code to FreeBSD that really belongs in the > >BIOS in the off chance that some really rare broken motherboard could > >then work. > > I agree, but I think clearing memory has other merits. Yes, setting it to 0xDeadBeef is a very good idea, that way you can find out some times when you pick up a wild pointer by the value in it :-). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD