From owner-freebsd-questions Thu Nov 28 23:33:53 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA04116 for questions-outgoing; Thu, 28 Nov 1996 23:33:53 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA04110 for ; Thu, 28 Nov 1996 23:33:51 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.3/8.6.12) with SMTP id XAA06971; Thu, 28 Nov 1996 23:36:46 -0800 (PST) Date: Thu, 28 Nov 1996 23:36:46 -0800 (PST) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Costa Morris cc: questions@FreeBSD.org Subject: Re: upgrade to 2.2 In-Reply-To: <199611221018.KAA06623@inner.cortx.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 22 Nov 1996, Costa Morris wrote: > I am looking to upgrade from 2.1 to 2.2 so i can take adavantage of > netatalk. What are the steps involved to upgrade? >From dwhite@gdi.uoregon.edu Wed Aug 28 20:05:07 1996 Date: Tue, 27 Aug 1996 21:17:49 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: "Sean J. Schluntz" Cc: freebsd-questions@FreeBSD.org Subject: Re: Upgrading 2.1.0 to 2.1.5 question. On Tue, 27 Aug 1996, Sean J. Schluntz wrote: > I have three FBSD systems running on my network at this time. I would like > to get my Administrative system upgraded to v2.1.5 (The others are running > fine they will wait until v2). What is the best way to do this? I tried > the upgrade option from the boot disk and got a nice little warning message > that made me wonder if that was really the way. Put the distribution files in an accessible place and follow the instructions below. 1) BACKUP /ETC, BACKUP /ETC, BACKUP /ETC. IT __WILL__ BE HOSED!!! 2) Boot the new floppy. Select the 'update' option. Follow the prompts. Make sure you MOUNT your filesystems and not NEWFS them. Select the same distributions you did originally and any you wish to add. 3) Hit 'commit'. Take note of the modified files. 4) WHen you're dumped to a shell prompt: . Copy services back from your backup /etc. It's three lines long now :( . Edit sysconfig and re-config from scratch using your old one as a guide. It's changed a bunch this time around and it's too much pain to hack in the new changes. . Migrate any changes you made to rc.local. Note that httpd is no longer started from sysconfig. 5) Reboot, recompile & reinstall your kernel, reboot again, and enjoy. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major