From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 14 13:12:23 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 039EE106564A for ; Fri, 14 Jan 2011 13:12:23 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (m209-73.dsl.rawbw.com [198.144.209.73]) by mx1.freebsd.org (Postfix) with ESMTP id 94C208FC16 for ; Fri, 14 Jan 2011 13:12:22 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.4/8.14.4) with ESMTP id p0EChHd8040717; Fri, 14 Jan 2011 04:43:17 -0800 (PST) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.4/8.14.4/Submit) id p0EChHKf040716; Fri, 14 Jan 2011 04:43:17 -0800 (PST) (envelope-from david) Date: Fri, 14 Jan 2011 04:43:17 -0800 From: David Wolfskill To: Aryeh Friedman Message-ID: <20110114124317.GN1817@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Aryeh Friedman , freebsd-hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="E4UgsyMmvHjpIg3x" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-hackers@freebsd.org Subject: Re: best way to run -RELEASE and -CURRENT on the same machine X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2011 13:12:23 -0000 --E4UgsyMmvHjpIg3x Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I won't claim that the approach I use is "best" for anyone (even me), but it generally works adequately for my purposes. I use a dual- (actually, quad-)boot approach, and set up the file systems in such a way that /usr/local is a symlink from each bootable environment to the same place. On my home "build machine," I maintain private FreeBSD repo mirrors; I mirror those onto my laptop. I use the above-sketched approach on both the build machine & my laptop, and (at present) track stable/8 & head on those machines on a daily basis. I update the ports (on each machine) while running stable/8. Naturally, if the goal were to be to test port-building or the function & stability of a port under head, this appraoch will not be suitable. To make this a bit more complete, I periodically (at present, each Sunday) install the latest built snapshot of stable/8 on my "production" machines here at home. Note that I am actually using "development" branches for this; that may or may not make sense for a given situation. (I had managed to get started on the multi-boot appraoch before jails existed -- it's a minor variation of an approach I used to use on IBM mainframes back in the 80s. It's plausible that some form of virtualization or the use of jails would do the job for me, but I'm fairly comfortable using what I'm familiar with.) Peace, david --=20 David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --E4UgsyMmvHjpIg3x Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAk0wROQACgkQmprOCmdXAD2q5gCfWIoUsE2JMAQ58Yb3aXnMJRl3 /iIAnikSusQn2TgKO8VHfcmca3zycBK2 =grGi -----END PGP SIGNATURE----- --E4UgsyMmvHjpIg3x--