From owner-freebsd-advocacy Tue Oct 5 21:54: 5 1999 Delivered-To: freebsd-advocacy@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 7DFAD1570C for ; Tue, 5 Oct 1999 21:53:26 -0700 (PDT) (envelope-from brooks@one-eyed-alien.net) Received: from localhost (brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with ESMTP id VAA29450; Tue, 5 Oct 1999 21:48:58 -0700 (PDT) X-Authentication-Warning: orion.ac.hmc.edu: brdavis owned process doing -bs Date: Tue, 5 Oct 1999 21:48:58 -0700 (PDT) From: Brooks Davis X-Sender: brdavis@orion.ac.hmc.edu To: J McKitrick Cc: Alfred Perlstein , freebsd-advocacy@FreeBSD.ORG Subject: Re: Linux convert... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 6 Oct 1999, J McKitrick wrote: > Will it be difficult to upgrade to 4.0? I just got 3.2, and i am leery of > updating to 3.3 and breaking my system (even though it has features i > could use) since i've seen some problems on the questions list. Won't 4.0 > be even more likely to do that? There will certaintly be issues, there always are. On the other hand I survived going to source upgrade route from 2.2.8 to 3.1 with minimal problems by reading the lists carefully before hand. That upgrade replaced the entire aout userland and kernel with an ELF userland and kernel and upgraded the bootloader, certaintly nothing to sneeze at. As to the move form 3.2 to 3.3, I wouldn't worry, I've been happily tracking stable on my router since 2.2.8 and on my laptop since 3.1 with no real problems. Heck, my laptop runs way better under FreeBSD then under windows. Once Warner Losh gets PCCard support working under newbus and current has a quiet moment, I plan run current and try my hand as some kernel hacking. As Alfred mentioned, it looks like 4.0 is going to kick some serious ass. -- Brooks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message