From owner-freebsd-questions@FreeBSD.ORG Wed Nov 24 04:52:56 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CD8916A4CE for ; Wed, 24 Nov 2004 04:52:56 +0000 (GMT) Received: from web53907.mail.yahoo.com (web53907.mail.yahoo.com [206.190.36.217]) by mx1.FreeBSD.org (Postfix) with SMTP id 029F243D31 for ; Wed, 24 Nov 2004 04:52:56 +0000 (GMT) (envelope-from stheg_olloydson@yahoo.com) Received: (qmail 45094 invoked by uid 60001); 24 Nov 2004 04:52:55 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=3V1ikK1DqJ1e5b1UcahnRiupOTr7pSy4n6SoN+gkI8KEENmzs2ZYJte8nFRoWDIbseYaIEugjc0kt9TQs1zbeKxI8b/nQdhgIPU2ZtSL2yaqB8AICnE6AvHmnTCbXzm/fk1aePrfp62tm0aUju/BOP8t7zH3fhZuSnV6Zyfptp0= ; Message-ID: <20041124045255.45089.qmail@web53907.mail.yahoo.com> Received: from [68.210.43.125] by web53907.mail.yahoo.com via HTTP; Tue, 23 Nov 2004 20:52:55 PST Date: Tue, 23 Nov 2004 20:52:55 -0800 (PST) From: stheg olloydson To: jayobrien@att.net MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: questions@freebsd.org Subject: Re: CVSup questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 04:52:56 -0000 it was said: >I have a system that right now I'm using to learn FreeBSD. I want to go >through the update process that I assume I'll have to follow regularly >once the computer is up and running as a web and mail server. Right >now I'm not concerned about backups; that's my next project. > >I'm attempting to follow "Using CVSup" and learn how CVSup works. See: >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html > >Questions about CVSup: > >1. Where should I place supfile? Obviously I could put it anywhere >and make it work, but is there a usual place for it? I can't find >where the manual makes a suggestion. Do I have a need for more than >one supfile? See http://www.cvsup.org/faq.html > >2. I am running 5.3 RELEASE. It appears that if I specify "*default >tag=." that I will be getting updates from "current". Is this what I >should do, given that I want to stay current on security and bug >fixes, but I don't (at this time) intend to get involved with beta >testing? Or should I specify *default tag=RELENG_5_3? And, if I do >that, will the ports be updated, including adding new ports? The current "current" is 6.0, not 5.3, so when updating src use tag=RELENG_5_3. *See #11 on the FAQ above for an important exception to this. > >3. The tutorial at http://www.us-webmasters.com/FreeBSD/Install/ >after item 68 describes CVSup. It suggests using the supfile >/usr/share/examples/cvsup/ports-supfile which gets the "ports-all" >collection. However, the Using CVSup manual says to get "src-all", >that includes ports-all. Is there some reason to use ports-all, not >src-all as suggested by the handbook? You can use one or two sup files. If you use one for both, you need two different tag= declarations, one for src (tag=RELENG_5_3) and one for everything else (tag=.). Ports, docs, etc. don't have RELENG versions, so if you try to use tag=RELENG_5_3, you will wipe out your ports, doc, etc., trees. > >4. The tutorial (see 3 above) item 97 concludes, after running cvsup, >"FreeBSD is installed, CONGRATULATIONS!" Isn't this a bit premature? >It seems to me that at that point I need to rebuild world per >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/book.html#MAKEWORLD >to apply the new files and bring the system up to date. Am I missing >something? I don't think "premature" is the right word. Clearly, FBSD is installed _already_. You are updating it. But, at this point, you aren't finished. You need to do the world/kernel/portupgrade stuff. Then it's CONGRATULATIONS!, assuming something doesn't blow up during any of the various procedures. As an extra word of advice, you may want to run the "script" command at each step to record the vast amount of messages that fly by. If anything goes wrong, you'll have a complete log; and if nothing goes wrong, you can grep thru them to see the many config options you didn't know about and the wonderful, worrisome warning messages that you won't be sure you can safely ignore or not! HTH Stheg __________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com