From owner-freebsd-current Mon Apr 15 10:27:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA10900 for current-outgoing; Mon, 15 Apr 1996 10:27:21 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA10891 for ; Mon, 15 Apr 1996 10:27:17 -0700 (PDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.4/8.7.4) with SMTP id NAA11456; Mon, 15 Apr 1996 13:26:43 -0400 (EDT) Date: Mon, 15 Apr 1996 13:26:41 -0400 (EDT) From: "Marc G. Fournier" To: David Greenman cc: current@FreeBSD.ORG Subject: Re: Panic during boot In-Reply-To: <199604150332.UAA04584@Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 14 Apr 1996, David Greenman wrote: > >> Wait, what's wrong with -n?? Except for the other day, I always > >> use -gn when I reconfig the sources before compiling, so that I don't lose > >> my version #. > > > >It would have been nice if you mentioned this back when you were talking > >about other problems you were having. > > > >-n is _evil_. If any changes have been made to your kernel sources that > >you are not _intimately_ familiar with, (ie. you have resupped), then > >you _must_must_must_ not use -n. Dependencies aren't enough to protect > >you from losing like this. I suspect this _may_ be part of your problem. > > Indeed. Even the dependencies themselves don't always work as expected so > some things don't get rebuilt when they need to be. The whole reason why > Jordan made the change to config to blow away the compile directory was > because we kept getting weird bug reports that later turned out to be caused > by a stale .o's. > As I sent back to Jordan...*groan* I only wanted to keep my version numbers straight :( actually, when I think back on it, it wasn't until I started asking about the version numbers that someone mentioned the -n switch...can we get rid of it altogether? :) Recompiling my kernel now and I'll see if that fixes the problem :( Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org