From owner-freebsd-questions Thu Jan 16 16:52:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA27876 for questions-outgoing; Thu, 16 Jan 1997 16:52:21 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA27869 for ; Thu, 16 Jan 1997 16:52:19 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.2/8.6.12) with SMTP id QAA03748; Thu, 16 Jan 1997 16:52:05 -0800 (PST) Date: Thu, 16 Jan 1997 16:52:05 -0800 (PST) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Stan Brown cc: Free BSD Questions list Subject: Re: Can I / Should I upgrade just the kernel from 2.1.5 to 2.2 ? In-Reply-To: <199701162257.RAA26122@netcom4.netcom.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 Thu, 16 Jan 1997, Stan Brown wrote: > So now the question, I started down the road of upgrading. I booted the > floppy, and eventually I was presented with a bewildering set of > choices on what packages I wanted to upgrade. I have a slow net > connection *28.8( and I would like to wait for the CD to come out to do > as much as possible. So just what do I need to upgrade to work corectly? Skip the packages. You can't install them without the CD. Just use 'pkg_add' like you always have. Upgrade instructions follow: FreeBSD Upgrade Checklist: 1) BACKUP /ETC, BACKUP /ETC, BACKUP /ETC. IT __WILL__ BE MODIFIED!!! 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. . Migrate any changes you made to rc.local and other files noted during the upgrade process. 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