From owner-freebsd-security Thu Jul 26 4:26:49 2001 Delivered-To: freebsd-security@freebsd.org Received: from vindaloo.allsolutions.com.au (vindaloo.allsolutions.com.au [203.111.24.54]) by hub.freebsd.org (Postfix) with ESMTP id 4A2C137B403 for ; Thu, 26 Jul 2001 04:26:46 -0700 (PDT) (envelope-from David_May@allsolutions.com.au) Received: from roganjosh.allsolutions.com.au (roganjosh.allsolutions.com.au [192.9.200.253]) by vindaloo.allsolutions.com.au (8.9.3/8.9.3) with ESMTP id TAA02121 for ; Thu, 26 Jul 2001 19:26:38 +0800 (WST) (envelope-from David_May@allsolutions.com.au) From: David_May@allsolutions.com.au Subject: [Q] distribution of patched binaries for security fixes. To: Date: Thu, 26 Jul 2001 18:47:21 +0800 Message-ID: X-MIMETrack: Serialize by Router on Perth/All Solutions(Release 5.0.7 |March 21, 2001) at 07/26/2001 07:26:39 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, I am setting up a FreeBSD machine to track the STABLE branch and to rebuild the system from time-to-time. The main reason being to keep track of security related fixes and enhancents.The documentation covers that quite well. But I was wondering what is a good procedure to distribute updated binaries to other machines. I several have production machines that I would like to keep up-to-date but do not want to compile source on every machine. Being able to create something like a Windows NT service pack would be nice :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message