From: Keith Owens <kaos@ocs.com.au>
To: jamagallon@able.es
Cc: linux-kernel@vger.kernel.org
Subject: Re: LKCD from SGI
Date: Sun, 26 Nov 2000 00:23:57 +1100 [thread overview]
Message-ID: <7235.975158637@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 25 Nov 2000 14:18:30 BST." <20001125141830.C2877@werewolf.able.es>
On Sat, 25 Nov 2000 14:18:30 +0100,
"J . A . Magallon" <jamagallon@able.es> wrote:
>On Sat, 25 Nov 2000 02:58:37 Keith Owens wrote:
>> 2.5 kernel build wish list[1] has a couple of entries for standardising
>> the install targets. My thinking (and I know that some people disagree
>> with this) is that the standard targets of a linux compile are only
>>
>> * vmlinux
>> * System.map
>> * modules in the kernel tree (not installed yet)
>> * any other bits and pieces that are required to compile external
>> modules against this config.
>
>Could the default target install names int the std kernel be changed to
>System.map -> System.map-$(KERNELRELEASE)
>vmlinuz -> vmlinuz-$(KERNELRELEASE)
>and then symlink to that ?
We could do a lot of things in the install targets. But none of them
are going to be done before kernel 2.5. We are in code freeze (is this
freeze number 4 or 5?). Changing the install method just before a new
kernel branch is released will not be popular with the distributors.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-25 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 15:20 LKCD from SGI 64738
2000-11-22 18:14 ` Matt D. Robinson
2000-11-23 1:41 ` Peter Samuelson
2000-11-24 23:40 ` Eric W. Biederman
2000-11-25 1:58 ` Keith Owens
2000-11-25 13:18 ` J . A . Magallon
2000-11-25 13:23 ` Keith Owens [this message]
2000-11-25 13:49 ` J . A . Magallon
2000-11-25 13:44 ` Matthew Kirkwood
-- strict thread matches above, loose matches on Subject: below --
2000-11-25 15:17 64738
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=7235.975158637@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.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