From owner-freebsd-current Sun Jan 11 12:18:04 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA02370 for current-outgoing; Sun, 11 Jan 1998 12:18:04 -0800 (PST) (envelope-from owner-freebsd-current) Received: from bubble.didi.com (sjx-ca124-37.ix.netcom.com [207.223.162.165]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA02238 for ; Sun, 11 Jan 1998 12:16:54 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by bubble.didi.com (8.8.7/8.8.8) id MAA00716; Sun, 11 Jan 1998 12:04:53 -0800 (PST) (envelope-from asami) Date: Sun, 11 Jan 1998 12:04:53 -0800 (PST) Message-Id: <199801112004.MAA00716@bubble.didi.com> To: current@FreeBSD.ORG In-reply-to: (message from Simon Shapiro on Sat, 10 Jan 1998 20:07:39 -0800 (PST)) Subject: Re: Firewall in kernel? - Found it! From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Listen guys, we've been over this over and over before. Check the mailing list archives for all the wonderful arguments we had in the past. Really, it's quite simple. If you change a header file, do a complete buildworld. Otherwise, just recompile that program. The tree might still have a minor breakage from time to time, but we're talking -current hee. Satoshi