Re: [PATCH] 2.2: /proc/config.gz

• Previous message: almesber@lrc.di.epfl.ch: "Re: [PATCH] 2.2: /proc/config.gz"
• In reply to: almesber@lrc.di.epfl.ch: "Re: [PATCH] 2.2: /proc/config.gz"
• Next in thread: Alan Cox: "Re: [PATCH] 2.2: /proc/config.gz"
• Next in thread: CaT: "Re: [PATCH] 2.2: /proc/config.gz"
• Reply: Alan Cox: "Re: [PATCH] 2.2: /proc/config.gz"
• Reply: Werner Almesberger: "Re: [PATCH] 2.2: /proc/config.gz"
• Reply: Philipp Rumpf: "Re: [PATCH] 2.2: /proc/config.gz"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Fri, Sep 01, 2000 at 02:23:57PM +0200, almesber@lrc.di.epfl.ch wrote:
> I don't see the advantage over Alan's proposal of simply adding the
> config data to the bzImage or whatever is the most common format on
> the respective platform. You still have the same fundamental problem
> to solve (i.e. accessing the file), plus you may need to extend the
> boot loader(s) to support a new format ...

I just don't see much advantage in a bzImage anymore, given the disk sizes
of modern computers. For kernel debugging I prefer to have an unpacked
vmlinux with symbol table. Would it be that hard to make lilo support unpacked,
unmangled ELF kernels ?

-Andi
-
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 message: Alan Cox: "Re: [PATCH] 2.2: /proc/config.gz"
• Previous message: almesber@lrc.di.epfl.ch: "Re: [PATCH] 2.2: /proc/config.gz"
• In reply to: almesber@lrc.di.epfl.ch: "Re: [PATCH] 2.2: /proc/config.gz"
• Next in thread: Alan Cox: "Re: [PATCH] 2.2: /proc/config.gz"
• Next in thread: CaT: "Re: [PATCH] 2.2: /proc/config.gz"
• Reply: Alan Cox: "Re: [PATCH] 2.2: /proc/config.gz"
• Reply: Werner Almesberger: "Re: [PATCH] 2.2: /proc/config.gz"
• Reply: Philipp Rumpf: "Re: [PATCH] 2.2: /proc/config.gz"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Sep 01 2000 - 08:29:21 EDT