From owner-freebsd-security@FreeBSD.ORG Fri Feb 6 12:16:29 2004 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FEAC16A4CE for ; Fri, 6 Feb 2004 12:16:29 -0800 (PST) Received: from gigatrex.com (saraswati.gigatrex.com [64.5.48.159]) by mx1.FreeBSD.org (Postfix) with SMTP id 827F443D46 for ; Fri, 6 Feb 2004 12:16:27 -0800 (PST) (envelope-from piechota@argolis.org) Received: (qmail 17834 invoked from network); 6 Feb 2004 20:16:17 -0000 Received: from unknown (HELO cithaeron.argolis.org) (141.156.46.123) by saraswati.gigatrex.com with SMTP; 6 Feb 2004 20:16:17 -0000 Received: from cithaeron.argolis.org (localhost [127.0.0.1]) i16KGOHa001005; Fri, 6 Feb 2004 15:16:24 -0500 (EST) (envelope-from piechota@argolis.org) Received: from localhost (piechota@localhost)i16KG5NC001001; Fri, 6 Feb 2004 15:16:05 -0500 (EST) X-Authentication-Warning: cithaeron.argolis.org: piechota owned process doing -bs Date: Fri, 6 Feb 2004 15:16:05 -0500 (EST) From: Matt Piechota To: Brett Glass In-Reply-To: <6.0.0.22.2.20040206104336.0587c5a0@localhost> Message-ID: <20040206151109.S921@cithaeron.argolis.org> References: <0FDD52D38220D611B7CC0004763B3744F80821@HNTS-04> <6.0.0.22.2.20040206104336.0587c5a0@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "'freebsd-security@freebsd.org'" cc: "Gogh, Ruben van" Subject: Re: IPFIREWALL_DEFAULT_TO_ACCEPT becomes default to deny X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2004 20:16:29 -0000 On Fri, 6 Feb 2004, Brett Glass wrote: > I've noticed that, in 4.9-RELEASE (and probably in -STABLE too), making > even minor changes to your kernel configuration often requires > > make clean; make depend; make; make install > > to work. If you leave out the "make clean" or "make depend", > modifications to your configuration sometimes don't take effect, > depending upon what you changed. Aren't supposed to run 'config' on your kernel conf when you modify it? That's what the handbook says, after all. :) -- Matt Piechota