From owner-freebsd-questions  Sat May 20 13:57:42 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id NAA08681
          for questions-outgoing; Sat, 20 May 1995 13:57:42 -0700
Received: from easynet.com (easy1.easynet.com [199.2.26.10])
          by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA08675
          for <freebsd-questions@FreeBSD.org>; Sat, 20 May 1995 13:57:39 -0700
Received: by easynet.com (Smail3.1.28.1 #7)
	id m0sCvaf-000rdMC; Sat, 20 May 95 13:57 WET DST
Message-Id: <m0sCvaf-000rdMC@easynet.com>
From: brian@mediacity.com (Brian Litzinger)
Subject: Re: linking kernel... *** signal 11
To: terry@cs.weber.edu (Terry Lambert)
Date: Sat, 20 May 1995 13:57:41 -0700 (PDT)
Cc: brian@mediacity.com, freebsd-questions@FreeBSD.org
In-Reply-To: <9505202020.AA06487@cs.weber.edu> from "Terry Lambert" at May 20, 95 02:20:27 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 507       
Sender: questions-owner@FreeBSD.org
Precedence: bulk


> > I'm building a kernel with a device driver from a third party company.

> Binary or source?

A little of both.  Mostly source and a little binary.

They, the author of the driver, have it running on a FreeBSD 2.0
(from the CDROM) system.  I'm running it under -current.

The previous release of their code ran under -current with an
mbuf leak.  This latest release has the mbuf leak fixed and
as other "improvements".  Regretably I get the signal 11 during
the link.

Brian Litzinger
brian@easynet.com