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
Subject: Re: 2.6.11-bk10 build problems
Date: Mon, 14 Mar 2005 11:57:39 -0800 [thread overview]
Message-ID: <1110830259.19340.17.camel@localhost> (raw)
In-Reply-To: <20050314194930.GB17373@mars.ravnborg.org>
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
next prev parent reply other threads:[~2005-03-14 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 19:39 2.6.11-bk10 build problems Dave Hansen
2005-03-14 19:49 ` Sam Ravnborg
2005-03-14 19:57 ` Dave Hansen [this message]
2005-03-14 20:34 ` Martin J. Bligh
2005-03-14 21:22 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2005-03-14 21:31 Martin J. Bligh
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=1110830259.19340.17.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=kai@germaschewski.name \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox