Date: Fri, 21 Aug 2009 17:47:10 +0000 From: Andrew Hotlab <andrew.hotlab@hotmail.com> To: <reddvinylene@gmail.com>, <jose.amengual@gmail.com>, <freebsd-jail@freebsd.org>, <freebsd-virtualization@freebsd.org> Subject: RE: Best practice to update jails Message-ID: <COL113-W33354CFB88F3644BB5689F6FC0@phx.gbl> In-Reply-To: <f1019d520908201428l534ea79fyd560441a97ecb72e@mail.gmail.com> References: <20090820121309.122740@gmx.net> <9C042ACE-8677-4104-BBB5-5F80C7EAFD3C@gmail.com> <f1019d520908201310t6e117e25wf46c59fa4624fdb2@mail.gmail.com> <AAD2F6B2-7567-445A-A404-803184D753EF@gmail.com> <f1019d520908201428l534ea79fyd560441a97ecb72e@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Thu=2C 20 Aug 2009 23:28:39 +0200 > From: reddvinylene@gmail.com > To: jose.amengual@gmail.com=3B freebsd-jail@freebsd.org=3B freebsd-virtua= lization@freebsd.org > CC: > Subject: Re: Best practice to update jails > > On Thu=2C Aug 20=2C 2009 at 10:57 PM=2C Jose Amengual wrote: > >> any reason of why you do not use freebsd-update ? >> >> Thanks. > > > I think most people prefer to build from source. I do=2C at least. > We manage some jail host system both for production and development (since = 6.2-RELEASE)=2C and we found the best support in the "build-from-source" up= grade method. Here the main steps we follow for a release-step upgrade (since we have a f= ew hosts to manage=2C we are using a dedicated build server=2C but the firs= t three steps might be executed on the host machine itself): 1. sync sources from a local cvsup-mirror to the build host=3B 2. make binaries on the build host (once per architecture we are supportin= g)=3B 3. mount /usr/src and /usr/obj via NFS on all systems to be upgraded=3B 4. run mergemaster in pre-buildworld mode (once for the host and once for = each jail with the -D flag)=3B 5. install the new kernel on the host we are upgrading=3B 6. reboot the host with the new kernel in single user mode=3B 7. install the new userland for the host and for the basejail (we are usin= g the ezjail framework)=3B 8. run mergemaster on the host to align its configuration files to the new= release=3B 9. boot into multi user mode=3B 10. run mergemaster with the -D flag to update each jail=92s configuration = files=3B 11. run "make delete-old" and "make delete-old-libs" on both host and jail = systems (using the DESTDIR variable). In our environment=2C this type of upgrade process has proved to be the mos= t effective and reliable=2C both for tracking the errata branch and for upg= rading between minor and major releases. Obviously it needs you quite knowl= edgeable about the build(7) process=2C but IMO time spent studying is alway= s time spent well! :) Andrew _________________________________________________________________ With Windows Live=2C you can organize=2C edit=2C and share your photos. http://www.microsoft.com/middleeast/windows/windowslive/products/photo-gall= ery-edit.aspx=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?COL113-W33354CFB88F3644BB5689F6FC0>