From owner-freebsd-current Tue Dec 9 19:43:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA09015 for current-outgoing; Tue, 9 Dec 1997 19:43:23 -0800 (PST) (envelope-from owner-freebsd-current) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA08990 for ; Tue, 9 Dec 1997 19:43:06 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id OAA01369; Wed, 10 Dec 1997 14:06:54 +1030 (CST) Message-Id: <199712100336.OAA01369@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Charlie Roots cc: Joerg Wunsch , freebsd-current@freebsd.org Subject: Re: files.i386, npx mandatory, config problem? In-reply-to: Your message of "Tue, 09 Dec 1997 18:25:15 -0800." <19971210022515.15414.rocketmail@send1a.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Dec 1997 14:06:53 +1030 From: Mike Smith Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > This problem is evidently causing much trouble for many people who use > cvsup to be current, so its current afterall. No, it's the people *using* current. Note that none of the "regulars" are complaining. Does this tell you something> > That's why I suggested > to Dough White in the past few days that the config kernel should have > a technique to check for discrapencies between the version of config > and the system being rebuilt, and gives a stub message telling the > user to make world first, this also includes rebuilding new config, > before attempting to compile a new kernel, but he just LAUGHED in my > face for that suggestion, Probably because it was implemented ages ago. If your config(8) doesn't bitch about being out of sync with your kernel sources, then it's either up to date or too old. I'll send you a copy of 'Staying -current with FreeBSD' off the list. Anyone else wants a copy, please ask. mike