All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Steinmetz <ast@domdv.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Blaisorblade <blaisorblade_spam@yahoo.it>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Why INSTALL_PATH is not /boot by default?
Date: Sun, 21 Nov 2004 11:37:36 +0100	[thread overview]
Message-ID: <41A06FF0.7090808@domdv.de> (raw)
In-Reply-To: <20041121094308.GA7911@mars.ravnborg.org>

Sam Ravnborg wrote:
> On Tue, Nov 16, 2004 at 01:27:15AM +0100, Blaisorblade wrote:
> 
>>This line, in the main Makefile, is commented:
>>
>>export  INSTALL_PATH=/boot
>>
>>Why? It seems pointless, since almost everything has been for ages requiring 
>>this settings, and distros' versions of installkernel have been taking an 
>>empty INSTALL_PATH as meaning /boot for ages (for instance Mandrake). It's 
>>maybe even mandated by the FHS (dunno).
>>
>>Is there any reason I'm missing?
> 
> 
> Changing this may have impact on default behaviour of some versions of
> installkernel.
> If /boot is ok for other than just i386 we can give it a try.
> 

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.

-- 
Andreas Steinmetz                       SPAMmers use robotrap@domdv.de

  parent reply	other threads:[~2004-11-21 10:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16  0:27 Why INSTALL_PATH is not /boot by default? Blaisorblade
2004-11-21  9:43 ` Sam Ravnborg
2004-11-21 10:19   ` Jan Engelhardt
2004-11-21 10:37   ` Andreas Steinmetz [this message]
2004-11-21 13:03     ` Jesper Juhl
2004-11-21 13:07       ` Andreas Steinmetz
2004-11-21 20:23         ` Jesper Juhl
2004-11-21 18:56       ` Sam Ravnborg
2004-12-03 19:57   ` Blaisorblade

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41A06FF0.7090808@domdv.de \
    --to=ast@domdv.de \
    --cc=blaisorblade_spam@yahoo.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.