Date: Tue, 20 Mar 2001 17:33:04 -0500 From: "Otter" <otterr@telocity.com> To: "'Kris Kennaway'" <kris@obsecurity.org>, "'Ben'" <ben@cahostnet.com> Cc: <questions@FreeBSD.ORG> Subject: RE: Automating CVSUP Message-ID: <001501c0b18d$bb6aaf10$1401a8c0@zoso> In-Reply-To: <20010320122707.A24145@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001501c0b18d$bb6aaf10$1401a8c0>