Date: Wed, 5 Dec 2007 13:53:06 +0100 From: Max Laier <max@love2party.net> To: freebsd-stable@freebsd.org Cc: John Baldwin <jhb@freebsd.org>, Colin Percival <cperciva@freebsd.org> Subject: Re: missing .cshrc and pf.conf after upgrade to 7.0-beta3 Message-ID: <200712051353.13065.max@love2party.net> In-Reply-To: <4755C3EB.8010108@freebsd.org> References: <47436A80.30306@quip.cz> <200711291451.47268.jhb@freebsd.org> <4755C3EB.8010108@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart4640653.n20Dnh76uo Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 04 December 2007, Colin Percival wrote: > John Baldwin wrote: > > On Wednesday 28 November 2007 02:47:11 pm Colin Percival wrote: > >> Miroslav Lachman wrote: > >>> I am not 100% sure, maybe I overlook something in binary major > >>> version upgrade procedure, but after upgrade from 6.2 to 7.0-BETA3 > >>> my roots ~/.cshrc was "accidentally" replaced with dist version of > >>> .cshrc and /etc/pf.conf is missing. > >> > >> The fact that /etc/pf.conf disappeared is due to it being removed > >> from the release (it is now in /usr/share/examples/etc). The fact > >> that /.cshrc was upgraded in spite of having been locally modified > >> is probably a bad idea -- I'll change the default > >> freebsd-update.conf to deal with this. > > > > 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. :-( > > FreeBSD Update tries to guess what users want to have done -- in this > case, the heuristic is "if a configuration file is present in release X > but not in release Y, it's probably not relevant in release Y; so let's > delete it". The case of a default configuration file being moved from > /etc/ into /usr/share/examples/etc is one which I didn't consider; but > I think the general heuristic is a good one (consider the scenario > where a /etc/foo.conf is renamed to /etc/food.conf -- with the current > heuristic, at least the user gets a warning that the file is > disappearing rather than suddenly finding that the foo daemon isn't > starting up properly for no apparent reason). Yet they lose the configuration changes they might have applied to the=20 original foo.conf. I don't think you should delete files that have=20 changed. Maybe moving them somewhere for future reference would be the=20 best thing to do? =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart4640653.n20Dnh76uo Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHVp85XyyEoT62BG0RAsrJAJ9GQiE33eFRMsfqe2CmNb+X+X0CmwCfR018 tlByr08JeqXdTamyvRcfPU8= =YfeW -----END PGP SIGNATURE----- --nextPart4640653.n20Dnh76uo--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200712051353.13065.max>