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
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
