From owner-freebsd-questions Tue Mar 20 15:28:39 2001 Delivered-To: freebsd-questions@freebsd.org Received: from c007.snv.cp.net (c007-h008.c007.snv.cp.net [209.228.33.214]) by hub.freebsd.org (Postfix) with SMTP id 0582937B728 for ; Tue, 20 Mar 2001 15:28:37 -0800 (PST) (envelope-from otterr@telocity.com) Received: (cpmta 1536 invoked from network); 20 Mar 2001 14:41:28 -0800 Received: from dsl-216-227-91-85.telocity.com (HELO zoso) (216.227.91.85) by smtp.telocity.com (209.228.33.214) with SMTP; 20 Mar 2001 14:41:28 -0800 X-Sent: 20 Mar 2001 22:41:28 GMT From: "Otter" To: "'Kris Kennaway'" , "'Ben'" Cc: Subject: RE: Automating CVSUP Date: Tue, 20 Mar 2001 17:33:04 -0500 Message-ID: <001501c0b18d$bb6aaf10$1401a8c0@zoso> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20010320122707.A24145@xor.obsecurity.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben, Kris has a good point, but if you're just trying to minimize *some* work, it's perfectly safe to cvsup your ports collection automatically. I do mine daily with no problems. The same warnings are why I don't automate my OS updates. If there's an error, I want to see it when I still have the opportunity to do something about it. -Otter > -----Original Message----- > From: owner-freebsd-questions@FreeBSD.ORG > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Kris Kennaway > Sent: Tuesday, March 20, 2001 3:27 PM > To: Ben > Cc: questions@FreeBSD.ORG > Subject: Re: Automating CVSUP > > > On Tue, Mar 20, 2001 at 08:23:45AM -0500, Ben wrote: > > > Will this work? Can someone tell me how I can accomplish this and > > also if I wanted to execute this myself how would I do it? > > A windows "batch file" is just a stunted implementation of a UNIX > "shell script" -- it's trivial to do what you want, but it's probably > a bad idea to go so far as to try and automate the entire > build/install process without even checking for errors. Best to do > these by hand at least until you're more experienced at FreeBSD, and > can recover from the first time there's a broken kernel/world, or an > extra step you need to do by hand, which may otherwise hose your > system. > > Kris > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message