Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261783AbUKUS4I (ORCPT ); Sun, 21 Nov 2004 13:56:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261787AbUKUS4H (ORCPT ); Sun, 21 Nov 2004 13:56:07 -0500 Received: from pfepb.post.tele.dk ([195.41.46.236]:6496 "EHLO pfepb.post.tele.dk") by vger.kernel.org with ESMTP id S261783AbUKUS4G (ORCPT ); Sun, 21 Nov 2004 13:56:06 -0500 Date: Sun, 21 Nov 2004 19:56:46 +0100 From: Sam Ravnborg To: Jesper Juhl Cc: Andreas Steinmetz , Sam Ravnborg , Blaisorblade , LKML Subject: Re: Why INSTALL_PATH is not /boot by default? Message-ID: <20041121185646.GA7811@mars.ravnborg.org> Mail-Followup-To: Jesper Juhl , Andreas Steinmetz , Sam Ravnborg , Blaisorblade , LKML References: <200411160127.15471.blaisorblade_spam@yahoo.it> <20041121094308.GA7911@mars.ravnborg.org> <41A06FF0.7090808@domdv.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 865 Lines: 21 On Sun, Nov 21, 2004 at 02:03:24PM +0100, Jesper Juhl wrote: > Please note that there are cases where you build a kernel for machine x on > > machine y. Which means: don't unconditionally uncomment this line. > > > Huh, in that case wouldn't you just copy the kernel image from the source > dir on machine y to whereever it needs to liveon machine x by hand? At > least that's what I do, the Makefile and its INSTALL_PATH never comes into > play then. In scripting it's much easier to have: make INSTALL_MOD_PATH=/nfs/frodo/ modules_install make INSTALL_PATH=/nfs/frodo/ install And everything 'just works'. Sam - 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/