From owner-freebsd-stable@FreeBSD.ORG Wed Dec 5 16:28:01 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9665116A468; Wed, 5 Dec 2007 16:28:01 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [82.208.36.70]) by mx1.freebsd.org (Postfix) with ESMTP id DABCC13C45D; Wed, 5 Dec 2007 16:28:00 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 4B7AD19E019; Wed, 5 Dec 2007 17:27:59 +0100 (CET) Received: from [192.168.1.2] (r3a200.net.upc.cz [213.220.192.200]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTP id BDE5719E02D; Wed, 5 Dec 2007 17:27:54 +0100 (CET) Message-ID: <4756D19F.3050003@quip.cz> Date: Wed, 05 Dec 2007 17:28:15 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cz, cs, en, en-us MIME-Version: 1.0 To: Colin Percival References: <47436A80.30306@quip.cz> <200711291451.47268.jhb@freebsd.org> <4755C3EB.8010108@freebsd.org> <200712051353.13065.max@love2party.net> <4756C70B.2050400@freebsd.org> In-Reply-To: <4756C70B.2050400@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Max Laier , freebsd-stable@freebsd.org, John Baldwin Subject: Re: missing .cshrc and pf.conf after upgrade to 7.0-beta3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Dec 2007 16:28:01 -0000 Colin Percival wrote: > Max Laier wrote: > >>On Tuesday 04 December 2007, Colin Percival wrote: >> >>>John Baldwin wrote: >>> >>>>Considering that /etc/pf.conf is a file that users edit to configure >>>>pf(4), removing it out from under them is probably a very bad idea. >>> >>>The heuristics didn't work this time. :-( >> >>Yet they lose the configuration changes they might have applied to the >>original foo.conf. I don't think you should delete files that have >>changed. Maybe moving them somewhere for future reference would be the >>best thing to do? > > > That is, in effect, what FreeBSD Update does -- the upgrade can always > be rolled back (and /etc/pf.conf recovered) by "freebsd-update rollback". Is there any way how one can recover just pf.conf and not whole upgrade? Is there any place, where warning about this issue (removing pf.conf) should go? Because many users are using PF and if anybody from them will try your freebsd-update.sh upgrade from FreeBSD 6.2 to newer release will lose pf.conf and end up with unfirewalled machine after reboot without knowing it. (just like me) Miroslav Lachman