From owner-freebsd-questions Wed Jul 19 20:35:39 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 3808D37BA2B for ; Wed, 19 Jul 2000 20:35:31 -0700 (PDT) (envelope-from djab@enteract.com) Received: from olivia (dschrock.cpe.dsl.enteract.com [216.80.53.93] (may be forged)) by mail.enteract.com (8.9.3/8.9.3) with SMTP id WAA04597; Wed, 19 Jul 2000 22:35:29 -0500 (CDT) (envelope-from djab@enteract.com) Message-ID: <007301bff1fb$d1745290$0271a8c0@anonymousdaemon.org> Reply-To: "Daniel Schrock" From: "Daniel Schrock" To: "\"R. D. Davis\"" Cc: "freebsd-questions" References: <8l5lml$6lt$1@FreeBSD.csie.NCTU.edu.tw> Subject: Re: 2.2.x to 4.0 Date: Wed, 19 Jul 2000 22:37:23 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 19 Jul 2000, Dan O'Connor wrote: > > I've heard one way is to upgrade to 3.5-STABLE, then upgrade again to > > 4.0-STABLE (soon to be 4.1). Rumour has it 2.2.x to 4.0 direct isn't > > feasible. > > That's what I'm discovering... a bit too late, alas for my crashed > system. It would have been helpful if a note about this had been > included with the 4.0 distribution, suah as in a README file, or at > least on the CD package or in the ordering info. I've read numerous articles and posts regarding this issue. The warnings are out there but they are kind of hard to find- I researched for a month or so before switching to 4.0. I started at 3.3-Release, upgraded to 3.4, clean installed 4.0-Release and cvsuped to 4.0-Stable. The rule of thumb I follow is that small steps can be cvsup'd (ie 3.3 -> 3.4) but major leaps are easiest as clean installs (3.4 ->4.0 or 2.2.x to 4.0 in your case). > I hate to say this, but this experience has made me think that perhaps > I should stock up on more old Sun 4 hardware and rely more on an old > version of Solaris for safeguarding my data. Hopefully someone from > this list, or someone developing FreeBSD can help change my mind about > this. Don't give up on FreeBSD. Cvsuping just hosed my webserver (which I attribute to changed/possibly broken nfs code but haven't found any posts regarding it- see the posts entitled- "I cvsup'd and now nfs filesystems won't mount" if they are still available). Its not that it wasn't usable at all, it just was not usable in the capacity which I needed. Even with days of pulling my hair out and fighting with my webserver, I still feel that FreeBSD is one of the greatest OS's of all time. My network is now changed as a result of the broken box, but the separate webserver was a bit of overkill for my needs. It was a learning experience and I'm glad I tried it (it was an experiment using port forwarding, nfs and nis) but now I have a box free for other experiments (it is now running Storm Linux- based on Debian- for a side by side comparison with FreeBSD- so far FreeBSD is still better, IMO). Anyway, good luck. Hope everything works out for you. daniel schrock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message