From owner-freebsd-questions Tue Jun 5 16:19:41 2001 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 7B81937B407 for ; Tue, 5 Jun 2001 16:19:38 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 88796 invoked by uid 100); 5 Jun 2001 23:19:37 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15133.26889.919193.686189@guru.mired.org> Date: Tue, 5 Jun 2001 18:19:37 -0500 To: Joel Dinel Cc: questions@freebsd.org Subject: Re: From -RELEASE to -STABLE In-Reply-To: <76672245@toto.iv> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Joel Dinel types: > I'd like to know : > > * What to add/modify to my cvsup file to track -STABLE > * How 'make world' works, and how *not* to bomb my system > * What to expect (broken stuff perhaps ?) > * How to keep my system (/usr/src) up to date afterwards All the answers are in the handbook: Personally, I recommend not fooling with the sup files at all. You can just tweak /etc/make.conf a bit, setting: SUP_UPDATE= yes SUPHOST= cvsupFIXME.FreeBSD.org SUP= /usr/local/bin/cvsup SUPFILE= /usr/share/examples/cvsup/stable-supfile PORTSSUPFILE= /usr/share/examples/cvsup/ports-supfile DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile then do "make update" in /usr/src to update everything. You can update /usr/doc and /usr/ports individually with the same command in those directories. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message