From owner-freebsd-isp  Tue Apr 22 17:31:52 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id RAA20142
          for isp-outgoing; Tue, 22 Apr 1997 17:31:52 -0700 (PDT)
Received: from spooky.eis.net.au (ernie@spooky.eis.net.au [203.12.171.2])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA20136
          for <freebsd-isp@freebsd.org>; Tue, 22 Apr 1997 17:31:42 -0700 (PDT)
Received: (from ernie@localhost)
	by spooky.eis.net.au (8.8.5/8.8.5) id KAA25315
	for freebsd-isp@freebsd.org; Wed, 23 Apr 1997 10:31:18 +1000 (EST)
From: Ernie Elu <ernie@spooky.eis.net.au>
Message-Id: <199704230031.KAA25315@spooky.eis.net.au>
Subject: Methods of keeping current with 2.2
To: freebsd-isp@freebsd.org
Date: Wed, 23 Apr 1997 10:31:17 +1000 (EST)
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As this and freebsd-announce are the only FreeBSD mail lists I subcribe to I
may have missed articles on how to keep up with patches to the 2.2-RELEASE.

I run a ISP with many FreeBSD 2.2.1-RELEASE servers doing various things, and
a bunch of customer sites also running 2.2.1-RELEASE. 

In the past I used 2.1.5, and once a month cron would fire up SUP to download 
source code updates to the -stable tree, and run a make world on each machine.

Now I beleive SUP is no longer really supported, being replaced with cvsup
and a somewhat trickier set up involving big Modula-3 libraries etc. 
I read Jordan's announcement this morning about the daily snaps of 2.2 with 
interest which prompted me to write this e-mail.

My question is what is the most practical method I can use to automate
monthly unattended updates of the 2.2 release?

- Ernie.