From owner-freebsd-current  Tue Dec  9 16:07:11 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA20559
          for current-outgoing; Tue, 9 Dec 1997 16:07:11 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id QAA20553
          for <freebsd-current@freebsd.org>; Tue, 9 Dec 1997 16:06:59 -0800 (PST)
          (envelope-from tom@uniserve.com)
Received: from shell.uniserve.com [204.244.210.252] 
	by pop.uniserve.com with smtp (Exim 1.73 #1)
	id 0xfZfa-0002jM-00; Tue, 9 Dec 1997 16:06:30 -0800
Date: Tue, 9 Dec 1997 16:06:27 -0800 (PST)
From: Tom <tom@uniserve.com>
To: Nathan Dorfman <nathan@SENATE.ORG>
cc: freebsd-current@freebsd.org
Subject: Re: files.i386, npx mandatory, config problem?
In-Reply-To: <199712092246.RAA24863@limbo.rtfm.net>
Message-ID: <Pine.BSF.3.96.971209160515.11657C-100000@shell.uniserve.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Tue, 9 Dec 1997, Nathan Dorfman wrote:

...
> worked fine. I haven't made world, it was the cvsup alone that
> started these problems. Obi-Wan cvsuped at the same time and got
> no problems; it isn't my configuration since config on GENERIC returns
> the same error.

  Probably "config" has changed, and you missed it because you haven't
done a "make world" for some time.  Probably a new "config" will
understand the config file.

> Any ideas?

Tom