If memory serves me right, Pete French wrote: > I appear to have a machine which will not run RELENG_6_2, though it runs > the released code quite happily. Is there a CVS tag I can use to revert the > sources back to the way they were on RELEASE? I want to be able to > verify that this is and track down what changed! I don't think it should > ever be the case that something which runs X.Y-RELEASE will not run RELENG_X_Y > should it ?
According to my records of commits, there were only three post-release commits to RELENG_6_2, and they were all fixes for security advisories or errata notices. They were: FreeBSD-SA-07:02.bind (9 Feb 2007) FreeBSD-EN-07:02.net and FreeBSD-EN-07:03.rc.d_jail (28 Feb 2007) FreeBSD-EN-07:05.freebsd-update (15 Mar 2007) All of these were vetted pretty closely by secteam@ and domain experts (and usually re@ as well). The only one of these that touched the kernel was FreeBSD-EN-07:02.net, which backed out an IPv6-related regression that was introduced late in the 6.2 release cycle. I'm personally pretty skeptical that this could cause a problem, although I'm admittedly a little biased, plus there weren't a lot of details in your email as to what the problem is. To answer your last question: If your machine runs 6.2-RELEASE, then RELENG_6_2 should run on it. Bruce.
signature.asc
Description: OpenPGP digital signature
