From owner-freebsd-isp Wed Apr 23 02:54:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA20237 for isp-outgoing; Wed, 23 Apr 1997 02:54:45 -0700 (PDT) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA20230 for ; Wed, 23 Apr 1997 02:54:34 -0700 (PDT) Received: (from bsdisp@localhost) by shadows.aeon.net (8.8.5/8.8.3) id MAA02640; Wed, 23 Apr 1997 12:45:59 +0300 (EET DST) From: mika ruohotie Message-Id: <199704230945.MAA02640@shadows.aeon.net> Subject: Re: Methods of keeping current with 2.2 In-Reply-To: <199704230749.JAA08506@zibbi.mikom.csir.co.za> from John Hay at "Apr 23, 97 09:49:52 am" To: jhay@zibbi.mikom.csir.co.za (John Hay) Date: Wed, 23 Apr 1997 12:45:59 +0300 (EET DST) Cc: ernie@spooky.eis.net.au, freebsd-isp@freebsd.org 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 > > and a somewhat trickier set up involving big Modula-3 libraries etc. > > > > My question is what is the most practical method I can use to automate > > monthly unattended updates of the 2.2 release? > I'd say use cvsup. If you don't want to hassle with the modula-3 libs, > use the one in ftp://hub.freebsd.org/pub/CVSup/cvsup-bin-14.1.1.tar.gz that that's right. the cvsup is still superrior for the task, far more better than sup ever could be... and hard to set up? either the said binary, or cd /usr/ports/net/cvsup make all install and there you go after a while. what comes to the cvsupfile, well, it can not be that hard. once you've been assimilated to cvsup you dont want to drop it. mickey