From owner-freebsd-questions Thu Nov 6 07:26:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA22194 for questions-outgoing; Thu, 6 Nov 1997 07:26:05 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from milehigh.denver.net (milehigh.denver.net [204.144.180.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA22187 for ; Thu, 6 Nov 1997 07:26:02 -0800 (PST) (envelope-from jdc@milehigh.denver.net) Received: (from jdc@localhost) by milehigh.denver.net (8.8.7/8.8.5) id IAA02436; Thu, 6 Nov 1997 08:26:16 -0700 (MST) Message-ID: <19971106082616.43888@denver.net> Date: Thu, 6 Nov 1997 08:26:16 -0700 From: John-David Childs To: Francisco Reyes Cc: freebsd-questions@freebsd.org Subject: Re: Can I use CVSup to go from 2.2.2 to 2.2.5? References: <199711060747.CAA24291@federation.addy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79 In-Reply-To: <199711060747.CAA24291@federation.addy.com>; from Francisco Reyes on Thu, Nov 06, 1997 at 02:51:12AM -0400 Organization: Enterprise Internet Solutions Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thursday November 6, 1997, Francisco Reyes had this to say about "Can I use CVSup to go from 2.2.2 to 2.2.5?": > I am new to using CVSup so forgive me if the questions are FAQ. > > By looking at the documentation it seems I could go from 2.2.2 to 2.2.5 > with CVSup. True...but be sure to back up EVERYTHING first (and do the upgrade on a spare machine first if you've never done a CVSup/make world before). > So far what I think I need: tag=RELENG_2_2 That tag will get you 2.2-STABLE, which has progressed beyond 2.2.5-RELEASE. If you want the latter, the tag should be RELENG_2_2_5_RELEASE A sample CVSupfile to use to get 2.2-STABLE is at: ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/examples /cvsup/stable-supfile (the above should be on one line of course) If you don't already have cvsup-15.2, get the binaries from hub.freebsd.org:/pub/CVSup or the package/port. I recommend the static-linked binary from hub.freebsd.org if you don't use/want modula-3 libraries laying around on your system. > I am still not clear which file collection I need. src-sys only? You will want src-all if you're doing a full upgrade. You may also want to uncomment the "secure" sources at the bottom of the file if you live in the U.S./Canada and need/want that code (Kerberos, DES, etc.) > > Going from 2.2.2 to 2.2.5 are there any file changes like there was > with sysconf becoming rc.conf? You will want to do a "make buildworld" first (once you CVSup the new/changed sources, that is). This will compile everything into /usr/obj >From there you can do "make installworld" and "make reinstall" if you NFS mount /usr/src and /usr/obj to other FreeBSD machines in your network. BE SURE TO READ /usr/src/Makefile to see what it does, and also BACKUP/COMPARE all the rc* files in your /etc directory with the new ones in /usr/src/etc (mostly minor changes imho, but the order of loading some network services was changed). As a matter of fact, you should definately keep /usr/src/etc/* (and /usr/src/sys/*) around if you decide to purge the sources once you've upgraded. Everyone once in a while I stumble across the need to replace/change/add a file from /usr/src/etc (/usr/src/etc/mtree/BSD.x11.dist is the latest example) -- John-David Childs (JC612) Enterprise Internet Solutions System Administrator @denver.net/Internet-Coach/@ronan.net & Network Engineer 1031 S. Parker Rd. #I-8 Denver, CO 80231 As of this^H^H^H^H next week, passwords will be entered in Morse code.