Date: Mon, 22 Aug 2005 15:00:20 -0700 From: Colin Percival <cperciva@freebsd.org> To: John Baldwin <jhb@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/conf newvers.sh Message-ID: <430A4AF4.4070004@freebsd.org> In-Reply-To: <200508221742.39896.jhb@FreeBSD.org> References: <200508190356.j7J3uj5D095435@repoman.freebsd.org> <200508221615.37569.jhb@FreeBSD.org> <430A4223.6080009@freebsd.org> <200508221742.39896.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > On Monday 22 August 2005 05:22 pm, Colin Percival wrote: >>FreeBSD Update doesn't know how to add new files; fortunately, it doesn't >>need to. Security patches don't add new files (or remove them). > > Yet. :) I'm going to try hard to make sure it stays that way. :-) >>The problem of upgrading between versions is outside of the scope of >>FreeBSD Update; it exists _only_ for the purpose of of tracking the >>RELENG_x_y branches. > > Hmm, ok. Might be useful someday to let folks choose to update their 5.3 box > to 5.4, etc. I put some instructions online for doing this -- essentially it comes down to "work out which configuration files you've changed, extract everything else from the new release's ISO image, and then compare file lists to remove any junk which was left behind": http://www.daemonology.net/freebsd-upgrade-5.3-to-5.4/ I considered doing some work to replace "download the 5.4-RELEASE ISO image" with "download a few MB of binary diffs" and generally to make the process more user friendly, but I haven't seen much interest in this so I haven't bothered. That said, I think that bsdupdates.com is going to be doing something along those lines. Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?430A4AF4.4070004>