From owner-freebsd-stable Thu Dec 17 16:17:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11818 for freebsd-stable-outgoing; Thu, 17 Dec 1998 16:17:58 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from enterprise.cs.unm.edu (enterprise.cs.unm.edu [198.59.151.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA11812 for ; Thu, 17 Dec 1998 16:17:55 -0800 (PST) (envelope-from colinj@cs.unm.edu) Received: from viper.cs.unm.edu [198.59.151.25] by enterprise.cs.unm.edu with smtp (Exim 1.80 #2) id 0zqnc3-00055S-00; Thu, 17 Dec 1998 17:17:47 -0700 Date: Thu, 17 Dec 1998 17:18:58 -0700 (MST) From: Colin Eric Johnson To: "Chris D. Faehl" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: going from 2.2.8 to 3.0, when? In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually I was planning on doing a fresh install of 3.0. I wasn't going to try and cvsup the 3.0 source. I can just as easily do the clean reinstall. On Thu, 17 Dec 1998, Chris D. Faehl wrote: > > So here I am inbetween semesters and I'm think that this is an excellent > > time to do an upgrade. So now my question is, what's the planned date for > > the -STABLE branch to working on the 3.x code? Should I run with it now? > > > > Don't do it, don't do it, don't try suicide... > > Sorry, my latent 70's Queen fetish got the best of me for a moment. > > I took a 2.2.8 box to 3.0 recently. My experience: fraught with pit traps, > only for the very cautious and FreeBSD-aware, and still some strange > problems. For now, I'd say best to reinstall from floppies. I'll > elaborate on some of my problems for the Good Of All. I'd love correction > and elucidation. > > a) cvsup/make buildworld/make installworld worked okay. > b) rebuilding a kernel (with appropriate references to new CAM devices) > worked okay. > c) updated /etc okay, merged my changes with dist changes okay. > d) made the new devices for the da? devices okay. > e) rebooting couldn't quite get it's act together after that make installworld. > "Bad System Call". Okay, I figured something like that might happen. > Cold booted, and 3.0-current fsck'd just fine, booted into multi-user > without issue. > f) some ports broke. In particular, acroread didn't work (probs with a.out > libraries and the linux emulator is my best guess). > g) After a 'make aout-to-elf', I couldn't login on the console any longer - > always "Login incorrect". But I could get in fine via ssh (I had > built as a port before I took to elf). > h) At that point, Jon wanted his box back ;). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message