From owner-freebsd-current Mon Jul 13 12:24:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19485 for freebsd-current-outgoing; Mon, 13 Jul 1998 12:24:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.falcon.com (bppp1.sysnet.net [206.142.16.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19472 for ; Mon, 13 Jul 1998 12:24:28 -0700 (PDT) (envelope-from patton@sysnet.net) Received: from [192.168.1.10] ([192.168.1.10]) by gatekeeper.falcon.com (8.8.8/8.8.5) with ESMTP id PAA21606 for ; Mon, 13 Jul 1998 15:14:57 -0400 (EDT) X-Sender: patton@mail.sysnet.net Message-Id: In-Reply-To: <199807101013.DAA22643@mailgate.cadence.com> References: <199807100843.SAA27370@cimlogic.com.au> from Matthew Patton at "Jul 8, 98 08:02:49 pm" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 12 Jul 1998 03:45:37 -0400 To: freebsd-current@FreeBSD.ORG From: Matthew Patton Subject: Re: SOLUTION! 2.2.6-Release to -current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG well I will concede that probably the vast majority of people out there do not seem to have problems doing a buildworld. But what I find interesting is that NOBODY seems to have done an FTP install which is what I do and did. Not that it should make any difference. Seems the "-m" directive doesn't help 100% of the time either. It ought to, I agree. I've also run into the problems with vinode.c being garbage or 0 bytes and having to restart the kernel build. This is a bit strange. To those out there having trouble (like libc failing) make sure you cvsup again (just in case) and give my steps a whirl. YMMV. -------- "If I were called upon to identify briefly the principal trait of the 20th Century, here too I would be unable to find anything more precise and pithy than to repeat once again: Men have forgotten God." - Aleksander Solzhenitsyn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message