From: Keith Owens <kaos@ocs.com.au>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: linux-kernel@vger.kernel.org, "Matt D. Robinson" <yakker@alacritech.com>
Subject: Re: LKCD from SGI
Date: Sat, 25 Nov 2000 12:58:37 +1100 [thread overview]
Message-ID: <5009.975117517@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "24 Nov 2000 16:40:50 PDT." <m1ofz5vszh.fsf@frodo.biederman.org>
On 24 Nov 2000 16:40:50 -0700,
ebiederm@xmission.com (Eric W. Biederman) wrote:
>Peter Samuelson <peter@cadcamlab.org> writes:
>
>> [Matt D. Robinson]
>> > Any way we can standardize 'make install' in the kernel? It's
>> > disturbing to have different install mechanisms per platform ...
>> > I can make the changes for a few platforms.
>>
>> 2.5 material, already on the todo list.
>
>What is the thought on this. There is an issue with different
>boot loaders needing rather dramatically different formats...
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.
The install phases are many and varied, depending on whether you are
installing on this machine, on another machine, does your boot loader
understand ELF, do you have to do the [b]zImage fiddling first, are you
doing a network boot from ROM, a network boot over tftp etc.
In current kernels the install phases are mixed in with the compile
phase which makes it difficult to handle different install targets.
2.5 will have a default make target which does the compile phase but
does nothing that is install related, i.e. default is no [b]zImage, no
modules_install etc. There will be separate install targets for any
combination that is required and for which people can be bothered
writing the make scripts.
[1] ftp://ftp.<country>.kernel.org/pub/linux/kernel/projects/kbuild/makefile-wishlist-2.5-...
-
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 2:29 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 [this message]
2000-11-25 13:18 ` J . A . Magallon
2000-11-25 13:23 ` Keith Owens
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=5009.975117517@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yakker@alacritech.com \
/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