From owner-freebsd-virtualization@FreeBSD.ORG Fri Aug 21 17:59:11 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4068B106568B; Fri, 21 Aug 2009 17:59:11 +0000 (UTC) (envelope-from andrew.hotlab@hotmail.com) Received: from col0-omc2-s3.col0.hotmail.com (col0-omc2-s3.col0.hotmail.com [65.55.34.77]) by mx1.freebsd.org (Postfix) with ESMTP id 1D62E8FC18; Fri, 21 Aug 2009 17:59:10 +0000 (UTC) Received: from COL113-W3 ([65.55.34.71]) by col0-omc2-s3.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 21 Aug 2009 10:47:10 -0700 Message-ID: X-Originating-IP: [81.174.54.98] From: Andrew Hotlab To: , , , Date: Fri, 21 Aug 2009 17:47:10 +0000 Importance: Normal In-Reply-To: References: <20090820121309.122740@gmx.net> <9C042ACE-8677-4104-BBB5-5F80C7EAFD3C@gmail.com> Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 21 Aug 2009 17:47:10.0411 (UTC) FILETIME=[689699B0:01CA2287] X-Mailman-Approved-At: Fri, 21 Aug 2009 21:03:55 +0000 Cc: Subject: RE: Best practice to update jails X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Aug 2009 17:59:11 -0000 > 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=