From owner-freebsd-isp Sun May 11 16:44:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA18469 for isp-outgoing; Sun, 11 May 1997 16:44:20 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA18464 for ; Sun, 11 May 1997 16:44:18 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id QAA00575; Sun, 11 May 1997 16:44:26 -0700 (PDT) To: Blaine Minazzi cc: isp@FreeBSD.ORG Subject: Re: Upgrade 2.1.5 --> 2.2.1 ? In-reply-to: Your message of "Sun, 11 May 1997 13:08:54 MDT." <33761946.42EFBF3B@denverweb.net> Date: Sun, 11 May 1997 16:44:25 -0700 Message-ID: <571.863394265@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Is this a straigtforward upgrade, or a complete re install and > reconfigure? Any tips as to what I can expect BEFORE i jump in feet > first would be appreciated. Yes. ;-) I actually recommend a reinstall right now as the sysinstall in 2.2.1 didn't do a chflags -R noschg over the root and usr filesystems before upgrading, and that was a mistake. Some things don't get upgraded properly and you end up with things like bogus ld.so files which can cause genuine dysfunction. This is fixed now in 2.2/3.0 but for 2.1.x -> 2.2.1 upgrades, I recommend a backup of the important bits and then a clean install. Clean installs are always preferable anyway since it's sort of the UNIX equivalent of an enema - you get rid of all the old header files and libs and such that can only get in your way later. > Another note. Is the adaptec driver that is included on the april 97 > cdrom from walnut creek the one that is buggy under a high load? No, it was updated before release. > Also, what are the advantages of the 2.2.1 over the 2.1.5? > I am wondering if it is worth waiting another 6 months or so before > doing an upgrade to whatever is likleyt to be the release this next > fall. ( I don't like to upgrade for minimal reasons. ) Is your 2.1.5 box working well for you? I'd wait. :-) Seriously, from the very beginning we've told folks that the "dot zero" releases (and the .1 release in this case really == .0 since there was only a week between the two :) should be avoided by ISPs with no clear reason to switch. Give the release branch another point release to stabilize itself before jumping on, if you can. Jordan