From owner-freebsd-advocacy@FreeBSD.ORG Tue Dec 28 13:17:08 2004 Return-Path: Delivered-To: freebsd-advocacy@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B341216A5D4 for ; Tue, 28 Dec 2004 13:17:07 +0000 (GMT) Received: from netmeister.org (netmeister.org [64.81.200.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3ACBA43D3F for ; Tue, 28 Dec 2004 13:17:07 +0000 (GMT) (envelope-from jschauma@netmeister.org) Received: by netmeister.org (Postfix, from userid 1000) id A8EDCE8067; Tue, 28 Dec 2004 08:19:16 -0500 (EST) Date: Tue, 28 Dec 2004 08:19:16 -0500 From: Jan Schaumann To: freebsd-advocacy@freebsd.org Message-ID: <20041228131916.GB10229@netmeister.org> Mail-Followup-To: freebsd-advocacy@freebsd.org References: <8cb27cbf04122708111005f3eb@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mxv5cy4qt+RJ9ypb" Content-Disposition: inline In-Reply-To: <8cb27cbf04122708111005f3eb@mail.gmail.com> User-Agent: Mutt/1.4.1i Subject: Re: How to deploy FreeBSD desktops ? X-BeenThere: freebsd-advocacy@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Evangelism List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 13:17:08 -0000 --mxv5cy4qt+RJ9ypb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Jon Drews wrote: =20 > Can anyone give me advice on how I should go about deploying and > maintaining FreeBSD desktops, in a company setting? I know how to do > it for my own FreeBSD desktop but how would I manage 30 to 50 > simultaneous installs? Shamelessly plugging myself :-), I'd like to point out that I presented a framework for just this at EuroBSDCon this year. Well, not FreeBSD desktops, but NetBSD, but the underlying principle is obviously the same. So you may find this paper helpful: http://www.netbsd.org/~jschauma/netbsd-desktop.pdf http://www.netbsd.org/~jschauma/netbsd-desktop-slides.pdf > Also what would be an effective way to track > ports so that I don't inadvertently portupgrade to an unstable=20 > version of software? Would I set aside one computer for tracking > ports? That is, suppose I have Gnome 2.6.2 in use but I want to > evaluate 2.8.0. How should I test it? Superficially, it would seem a > simple thing but how can I be sure that my use of 2.8.0 replicates > what be normal usage, throughout the company? I usually build binary versions of all my software. I install everything in a test-sandbox, and push the changes out to one machine if I need to test such an upgrade. If I have willing users, I push out the changes from the test-sandbox to them and let them evaluate the setup for a few days, before I update the production-sandbox and push out all clients. -Jan --=20 Free Speech Online - Stop Internet Censorship --- Electronic Frontier Foundation -- http://www.eff.org --- --mxv5cy4qt+RJ9ypb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (NetBSD) iD8DBQFB0V1UfFtkr68iakwRAk8oAJ0Ydvq2u4Mr9iQZRzpvT6mac+CxugCfRqBx nOs2wLDX4UvvZJdBmUG2PyQ= =pQG8 -----END PGP SIGNATURE----- --mxv5cy4qt+RJ9ypb--