From owner-freebsd-stable Wed Mar 14 7:44:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vorrix.com (ns1.vorrix.com [205.214.90.212]) by hub.freebsd.org (Postfix) with ESMTP id 6E44A37B71A for ; Wed, 14 Mar 2001 07:44:35 -0800 (PST) (envelope-from steffen@vorrix.com) Received: from ws001 [208.60.70.195] by vorrix.com [192.168.0.1] with SMTP (MDaemon.v3.5.3.R) for ; Wed, 14 Mar 2001 10:46:08 -0500 Message-ID: <000e01c0ac9d$abd50040$fd03a8c0@ws001> From: "Steffen Vorrix" To: Subject: Major upgrade Date: Wed, 14 Mar 2001 10:44:34 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C0AC73.C2523D80" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-MDRemoteIP: 208.60.70.195 X-Return-Path: steffen@vorrix.com X-MDaemon-Deliver-To: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000B_01C0AC73.C2523D80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have been tracking this list for about 3 or 4 weeks now, and I have = learned alot more about FreeBSD then I thought I might. I have = successfully upgrade my two home FreeBSD machines from 4.2 REL to the = current stable version, and everything went just fine. However, I now = need to upgrade 2 production machines for my employer, and these have to = go as painlessly as possible. The problem is that these machines are = 3.4 REL. I have looked through 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 specifically 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 person 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 sure there = aren't other things I need to watch out for. Thanks a bunch. Chris Schremser ------=_NextPart_000_000B_01C0AC73.C2523D80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I have been tracking this list for = about 3 or 4=20 weeks now, and I have learned alot more about FreeBSD then I thought I=20 might.  I have successfully upgrade my two home FreeBSD machines = from 4.2=20 REL to the current stable version, and everything went just fine.  = However,=20 I now need to upgrade 2 production machines for my employer, and these = have to=20 go as painlessly as possible.  The problem is that these machines = are 3.4=20 REL.  I have looked through the mail over the past weeks, and I = have found=20 people mention that 3.4 to 4 can have some gotcha's associated with it, = but I=20 haven't seen anything specifically mentioned.  Are there things = that I need=20 to watch out for?  The reference that I am referring to was a = thread=20 regarding remotely updating servers.  While this was frowned upon = by almost=20 everyone in the list, one person specifically mentioned that remote = updating=20 would be a problem from a 3.x to a 4.x.  I don't plan to do any = remote=20 updating, but I want to be sure there aren't other things I need to = watch out=20 for.
 
Thanks a bunch.
 
Chris = Schremser
------=_NextPart_000_000B_01C0AC73.C2523D80-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message