"Jeff V. Merkey" wrote:
> We need a format that allow multiple executable segments to be combined
> in a single executable and the loader have enough smarts to grab the
> right one based on architecture. two options:
>
> 1. extend gcc to support this or rearragne linux into segments based on
> code type
> 2. Use PE.
The kernel isn't going non-ELF. Too painful, for dubious advantages,
namely:
The current gcc toolchain already supports what you suggest.
I understand that some people have even put some thought into a
bootloader that dynamically links your kernel on bootup, so this idea
isn't new. It's a good idea though.
Jeff
--
Jeff Garzik | "When I do this, my computer freezes."
Building 1024 | -user
MandrakeSoft | "Don't do that."
| -level 1
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
- Re: Installing kernel 2.4 David Lang
- Re: Installing kernel 2.4 Jeff V. Merkey
- Re: Installing kernel 2.4 Sven Koch
- Re: Installing kernel 2.4 Jeff Garzik
- Re: Installing kernel 2.4 David Relson
- Re: Installing kernel 2.4 Jeff V. Merkey
- Re: Installing kernel 2.4 Jeff Garzik
- Re: Installing kernel 2.4 Jeff V. Merkey
- Re: Installing kernel 2.4 Jeff Garzik
- Re: Installing kernel 2.4 Jeff V. Merkey
- Re: Installing kernel 2.4 Jeff Garzik
- Re: Installing kernel 2.4 Jeff V. Merkey
- Re: Installing kernel 2.4 Mark W. McClelland
- Re: Installing kernel 2.4 Alan Cox
- Re: Installing kernel 2.4 H. Peter Anvin
- Re: Installing kernel 2.4 Jeff V. Merkey
- Re: Installing kernel 2.4 Alan Cox
- Re: Installing kernel 2.4 Matthew Kirkwood
- Re: Installing kernel 2.4 Alan Cox
- Re: Installing kernel 2.4 Jeff V. Merkey
- Re: Installing kernel 2.4 Alan Cox

