Date: Wed, 2 Jan 2008 13:10:53 +0100 From: "Andrew Hotlab" <andrew.hotlab@hotmail.com> To: "Jon Passki" <jon.passki@hursk.com> Cc: FreeBSD-Jail <freebsd-jail@freebsd.org> Subject: Re: How to better update a jail host system Message-ID: <BAY138-DS14AD6ECA4AD7D24BA4E11F6520@phx.gbl> In-Reply-To: <BAY102-W41E0DDC536BD8491761400F65C0@phx.gbl> <cc6847e40712242048mf26f6d3ve360d4bb5486f2b5@mail.gmail.com> References: <BAY102-W41E0DDC536BD8491761400F65C0@phx.gbl> <cc6847e40712242048mf26f6d3ve360d4bb5486f2b5@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-------------------------------------------------- From: "Jon Passki" <jon.passki@hursk.com> Sent: Tuesday, December 25, 2007 5:48 AM To: "Andrew Hotlab" <andrew.hotlab@hotmail.com> Cc: "FreeBSD-Jail" <freebsd-jail@freebsd.org> Subject: Re: How to better update a jail host system > You can re-create your binary jail setup easily from sysinstall: > > sysinstall _ftpPath=ftp://ftp.FreeBSD.org/pub/FreeBSD/ > nonInteractive=yes mediaSetFTP releaseName=6.2-RELEASE dists=base > distSetCustom installRoot=/path/to/jail installCommit > > Then, the only thing you have to manage is packages. With a patched > freebsd-update [2], you can even update from 6.2 to 6.3. If ezjail > supports a binary tarball update, it would be trivial to take the > output of the sysinstall and freebsd-update and roll one. > I had not ever considered using sysinstall(8) as an option to create jails: it sounds good, expecially to a sysadmin who had never had to compile nothing, like me! As you pointed out, until ezjail(5) doesn't support that procedure I won't likely use it in production, since the advantages that Dirk's framework brings in managing jails are more valuable to me than the "annoyance" of compiling from sources! :) Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BAY138-DS14AD6ECA4AD7D24BA4E11F6520>