From owner-freebsd-current Fri Apr 14 19:20:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA22426 for current-outgoing; Fri, 14 Apr 1995 19:20:21 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA22409 for ; Fri, 14 Apr 1995 19:20:00 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id TAA19083; Fri, 14 Apr 1995 19:19:43 -0700 From: Poul-Henning Kamp Message-Id: <199504150219.TAA19083@ref.tfs.com> Subject: Re: Interesting (and odd) effect in -current To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Fri, 14 Apr 1995 19:19:41 -0700 (PDT) Cc: davidg@Root.COM, cmf@ins.infonet.net, current@FreeBSD.org In-Reply-To: <199504150214.TAA02308@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Apr 14, 95 07:14:28 pm Content-Type: text Content-Length: 780 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 :-). Except that in our case is should be 0x00coffee, "No coffee" :-) -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'