From owner-freebsd-hackers  Sun Feb  9 17:31:42 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA26679
          for hackers-outgoing; Sun, 9 Feb 1997 17:31:42 -0800 (PST)
Received: from tyger.inna.net (root@tyger.inna.net [206.151.66.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA26647
          for <freebsd-hackers@freebsd.org>; Sun, 9 Feb 1997 17:31:09 -0800 (PST)
Received: from dolphin.inna.net (jamie@dolphin.inna.net [206.151.66.2]) by tyger.inna.net (8.8.3/8.7.3) with SMTP id UAA06336; Sun, 9 Feb 1997 20:31:52 -0500 (EST)
Date: Sun, 9 Feb 1997 20:31:00 -0500 (EST)
From: Jamie Bowden <jamie@inna.net>
To: Charles Mott <cmott@srv.net>
cc: freebsd-hackers@freebsd.org
Subject: Re: Bus Errors
In-Reply-To: <Pine.BSF.3.91.970209174624.3664A-100000@darkstar>
Message-ID: <Pine.BSF.3.91.970209203020.4128A-100000@dolphin.inna.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Sun, 9 Feb 1997, Charles Mott wrote:

> What does "Bus error" mean?
> 

Amazingly enough, a buss error is a memory allocation error.  At least it 
was under SunOS.  I am guessing FreeBSD is the same on this.

Jamie Bowden

Network Administrator, TBI Ltd.