Subject: Re: 2.6.11-bk10 build problems
From: Dave Hansen <haveblue@us.ibm.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       kai@germaschewski.name
In-Reply-To: <20050314194930.GB17373@mars.ravnborg.org>
References: <1110829177.19340.8.camel@localhost>
	 <20050314194930.GB17373@mars.ravnborg.org>
Content-Type: text/plain
Date: Mon, 14 Mar 2005 11:57:39 -0800
Message-Id: <1110830259.19340.17.camel@localhost>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1109
Lines: 25

On Mon, 2005-03-14 at 20:49 +0100, Sam Ravnborg wrote:
> On popular request 'make install' no longer try to update vmlinux.
> This is to avoid errornous recompilation when installing the kernel
> as root especially when fetching kernel via nfs where path may have
> changed.

That makes sense, but it's still quite a surprise, and a serious change
in behavior from as long as I've been compiling kernels.

How about a new "make install-norebuild" or something that doesn't
change current, relied-upon behavior?  Seems like the weirdos^Wusers
doing kernel fetches over nfs are probably the minority, and their small
numbers can be much more easily educated than the masses who expect
'make menuconfig; make install' to do what it's always done.  

If that's too invasive, how about restoring the old behavior with a
warning to stderr for a release or two?

-- Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/