From owner-freebsd-hackers  Fri Jul 30 13: 7:34 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP
	id CBEE1152FA; Fri, 30 Jul 1999 13:07:31 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA08608;
	Fri, 30 Jul 1999 13:06:13 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
To: "Brian F. Feldman" <green@FreeBSD.org>
Cc: hackers@FreeBSD.org
Subject: Re: So, back on the topic of enabling bpf in GENERIC... 
In-reply-to: Your message of "Fri, 30 Jul 1999 16:04:47 EDT."
             <Pine.BSF.4.10.9907301603050.6951-100000@janus.syracuse.net> 
Date: Fri, 30 Jul 1999 13:06:13 -0700
Message-ID: <8605.933365173@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> There's no good reason to not have bpf in at least the boot disk kernel.

It already is.  That's not the question under discussion here - we're
talking about how to make things work in the post-installation boot
scenario.

- Jordan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message