From owner-freebsd-current Tue Jul 28 13:05:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01970 for freebsd-current-outgoing; Tue, 28 Jul 1998 13:05:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01770 for ; Tue, 28 Jul 1998 13:04:27 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id NAA04275; Tue, 28 Jul 1998 13:03:35 -0700 (PDT) (envelope-from jdp) Message-Id: <199807282003.NAA04275@austin.polstra.com> To: lee@gwinnett.com Subject: Re: GENERIC Kernel Problem In-Reply-To: <35BDEF4D.41C67EA6@gwinnett.com> References: <35BDEF4D.41C67EA6@gwinnett.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Tue, 28 Jul 1998 13:03:35 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <35BDEF4D.41C67EA6@gwinnett.com>, Lee Reese wrote: > I just loaded the 7-25-98 SNAP release of -current and a couple of > uniprocessor machines. I can't seem to run a /usr/sbin/config on the > MYKERNEL file I made. > > The error is: > > cant open ../i386/config/devices.(null) > > Could someone tell me what is going on here? Thanks. If I had to guess without looking, I'd say you probably left out the line machine "i386" in your config file. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message