From owner-freebsd-questions Thu Jan 25 14:22: 2 2001 Delivered-To: freebsd-questions@freebsd.org Received: from relay3.inwind.it (relay3.inwind.it [212.141.53.74]) by hub.freebsd.org (Postfix) with ESMTP id D647237B400 for ; Thu, 25 Jan 2001 14:21:43 -0800 (PST) Received: from bartequi.ottodomain.org (62.98.170.127) by relay3.inwind.it (5.1.056) id 3A40BF860077C01C; Thu, 25 Jan 2001 23:21:30 +0100 From: Salvo Bartolotta Date: Thu, 25 Jan 2001 22:24:15 GMT Message-ID: <20010125.22241500@bartequi.ottodomain.org> Subject: Re: Advise Please To: Odhiambo Washington Cc: freebsd-questions@FreeBSD.ORG References: <20010125215637.C70366@poeza.iconnect.co.ke> X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 1/25/01, 7:56:37 PM, Odhiambo Washington wrote regarding Advise Please: > I only need a little advise on source synchronization. > Could someone kindly tell me what might have happened if you cvsup today > and your buildworld breaks, but you cvsup 2morrow and it goes OK? Is it > because we're all humans and are prone to err? Hello Odhiambo, Errare humanum, perseverare autem**... :-)) Seriously, though, the best piece of advice I have ever heard of is the following: 1) cvsup and update a test machine; 2) test... the test machine for a week or so. N.B. the updating process itself, in this connection, is a *minor* issue. Rather, it is important (even essential) that you should "squeeze" your test machine, in order to examine/check/scrutinize its actual stability/functionality/etc. before committing -- if I may say so -- the changes to your production machines. Best regards, Salvo **reference to [FreeBSD's] daemon(s) is to be considered as purely coincidental. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message