From owner-freebsd-questions Thu Mar 27 11:44:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA14392 for questions-outgoing; Thu, 27 Mar 1997 11:44:23 -0800 (PST) Received: from gdi.uoregon.edu (cisco-ts16-line13.uoregon.edu [128.223.150.213]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA14376 for ; Thu, 27 Mar 1997 11:44:16 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id LAA00436; Thu, 27 Mar 1997 11:43:59 -0800 (PST) Date: Thu, 27 Mar 1997 11:43:59 -0800 (PST) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Pat McPartland cc: FBSD questions Subject: Re: Install new version FreeBSD In-Reply-To: <199703202055.PAA24111@fireball.blast.net> 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 Thu, 20 Mar 1997, Pat McPartland wrote: > Hello, > How do I upgrade an existing FreeBSD server to the current version? How > long should it take? What preparations should I make in case install > fails, etc... FreeBSD Upgrade Checklist for 2.2: 1) 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 (including the kernel source, src/ssys!) and any you wish to add. **WARNING!** Do **NOT** upgrade XFree86 at this time. The binary distributed with 2.2 is built for 3.0-CURRENT, which has longer usernames. It will corrupt your utmp file, which will cause w, who, and associated utils to give odd output. If you have dire need to upgrade, you will want to rebuild xdm and xterm, and probably the whole package, before using it. 2) Hit 'commit' to start the upgrade. 3) When you're dumped to a shell prompt: . Your /etc directory is preserved as it was for 2.1.x. You will want to look in /etc/upgrade, which contains new & updated files for this release. . Using your old sysconfig as a guide, create a new sysconfig using the one in /etc/upgrade as a template. . Copy over the rc* files from upgrade/, so new features in sysconfig are used. Merge in any local changes, if necessary. If you are getting unusual messages from ipx, you forgot to do this. . Migrate other files as necessary. 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