From owner-freebsd-current Tue Mar 7 22:19:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E425937B59E; Tue, 7 Mar 2000 22:19:36 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA61856; Tue, 7 Mar 2000 23:19:35 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA99365; Tue, 7 Mar 2000 23:19:20 -0700 (MST) Message-Id: <200003080619.XAA99365@harmony.village.org> To: Kris Kennaway Subject: Re: 3.4 -> 4.0 upgrade problems Cc: Ruslan Ermilov , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 07 Mar 2000 18:19:05 PST." References: Date: Tue, 07 Mar 2000 23:19:20 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kris Kennaway writes: : On Tue, 7 Mar 2000, Warner Losh wrote: : > A better work around is cd lib/libc and do a make install. : : I'm pretty sure I tried that - I can't remember if it screwed me up : (signal 12 errors) or just didn't work. Odd. I actually tried it myself not to long ago and it worked great. : Sounds like a bug. However, IMO people should be building GENERIC as their : first 4.0 kernel, because all the config file changes mean they won't be : able to just use their old one, and chances are they might screw up and : miss out something important and then blame it on 4.0 instead of their own : ignorance. If we get them booting with GENERIC and prove they can (which : is what the buildkernel target does by default), then it's more obviously : user error when the next kernel they build doesn't work (plus, they : have a working 4.0 kernel to fall back on, namely kernel.old :-) Hmmm, I'll have to think about this... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message