From owner-freebsd-questions  Tue Jan 13 16:27:02 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA00575
          for questions-outgoing; Tue, 13 Jan 1998 16:16:01 -0800 (PST)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from luke.cpl.net (luke.cpl.net [209.150.73.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01966
          for <questions@FreeBSD.ORG>; Tue, 13 Jan 1998 16:02:51 -0800 (PST)
          (envelope-from shawn@luke.cpl.net)
Received: from localhost (shawn@localhost) by luke.cpl.net (8.8.8/8.6.12) with SMTP id XAA21437; Mon, 12 Jan 1998 23:18:05 -0800 (PST)
Date: Mon, 12 Jan 1998 23:18:05 -0800 (PST)
From: Shawn Ramsey <shawn@luke.cpl.net>
To: Doug White <dwhite@resnet.uoregon.edu>
cc: questions@FreeBSD.ORG
Subject: Re: beeping!
In-Reply-To: <Pine.BSF.3.96.980112213058.22079E-100000@gdi.uoregon.edu>
Message-ID: <Pine.BSF.3.95.980112231651.21435A-100000@luke.cpl.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk

> > didnt do this when Windows was on it... any ideas short of taking out the
> > speaker?
> 
> You need to find the source of the beeping.  Check the console or
> currently active vty.
> 
> Or else pull the speaker out if it's not soldered on the motherboard ;)

I found the problem. It was apparantly something on the console(no monitor
is connected). I removed everything in /etc/syslog.conf that had
/dev/console and changed it to a log file. :) That fixed it. I still don't
know what was actually causing the beep.