From owner-freebsd-stable Wed Mar 14 7:50:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.communityconnect.com (mail.communityconnect.com [209.10.169.57]) by hub.freebsd.org (Postfix) with ESMTP id 0C43737B71D for ; Wed, 14 Mar 2001 07:50:22 -0800 (PST) (envelope-from marius@mail.communityconnect.com) Received: from amavis by mail.communityconnect.com with scanned-ok (Exim 3.20 #1) id 14dDXY-0000do-00 for freebsd-stable@freebsd.org; Wed, 14 Mar 2001 10:50:20 -0500 Received: from [206.28.215.90] (helo=dt-9-45.hq.communityconnect.com) by mail.communityconnect.com with esmtp (Exim 3.20 #1) id 14dDXU-0000ac-00; Wed, 14 Mar 2001 10:50:16 -0500 Date: Wed, 14 Mar 2001 10:50:19 -0500 (EST) From: Marius X-Sender: marius@utterlux.hq.communitconnect.com To: Steffen Vorrix Cc: freebsd-stable@freebsd.org Subject: Re: Major upgrade In-Reply-To: <000e01c0ac9d$abd50040$fd03a8c0@ws001> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've done the upgrade from 3.4 to 4.x stable a few times. I genrally go from 3.4->3.5-Stable and then 3.5-Stable -> 4.x-stable. Basically, if you follow the instructions in UPDATING, it should go well. If you take UPDATING seriously and actually reboot into single user when it tells you to, it will likely be painless. There are ways to get around going into single user, but if you have the luxury of a console, don't sweat it. -Marius On Wed, 14 Mar 2001, Steffen Vorrix wrote: > I have been tracking this list for about 3 or 4 weeks now, and I have lea= rned alot more about FreeBSD then I thought I might. I have successfully u= pgrade my two home FreeBSD machines from 4.2 REL to the current stable vers= ion, and everything went just fine. However, I now need to upgrade 2 produ= ction machines for my employer, and these have to go as painlessly as possi= ble. The problem is that these machines are 3.4 REL. I have looked throug= h the mail over the past weeks, and I have found people mention that 3.4 to= 4 can have some gotcha's associated with it, but I haven't seen anything s= pecifically mentioned. Are there things that I need to watch out for? The= reference that I am referring to was a thread regarding remotely updating = servers. While this was frowned upon by almost everyone in the list, one p= erson specifically mentioned that remote updating would be a problem from a= 3.x to a 4.x. I don't plan to do any remote updating, but I want to be su= re there aren't other things I need to watch out for. >=20 > Thanks a bunch. >=20 > Chris Schremser >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message