Andi Kleen wrote: > What you need is a bootloader than can read uncompressed vmlinux directly, > and use that for booting. Then you can always directly extract the System.map > out of the vmlinux using nm or gdb. And then pass this information to the soon to be running system via e.g. an initrd ? I'm not sure this is a lot more efficient, and you've just created yet another set of dependencies. Also, I' very sceptical about anything that requires non-trivial updates to all boot loaders. - Werner -- _________________________________________________________________________ / Werner Almesberger, ICA, EPFL, CH [EMAIL PROTECTED] / /_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/ - 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: [PATCH] 2.2: /proc/config.gz Alan Cox
- Re: [PATCH] 2.2: /proc/config.gz almesber
- Re: [PATCH] 2.2: /proc/config.gz almesber
- Re: [PATCH] 2.2: /proc/config.gz Alan Cox
- Re: [PATCH] 2.2: /proc/config.gz Nathan Paul Simons
- Re: [PATCH] 2.2: /proc/config.gz Michael Rothwell
- Re: [PATCH] 2.2: /proc/config.gz Daniel Phillips
- Re: [PATCH] 2.2: /proc/config.gz Timur Tabi
- Re: [PATCH] 2.2: /proc/config.gz Andi Kleen
- Re: [PATCH] 2.2: /proc/config.gz Jan-Benedict Glaw
- Re: [PATCH] 2.2: /proc/config.gz almesber
- Re: [PATCH] 2.2: /proc/config.gz Andi Kleen
- Re: [PATCH] 2.2: /proc/config.gz almesber
- Re: [PATCH] 2.2: /proc/config.gz Andi Kleen
- Re: [PATCH] 2.2: /proc/config.gz Alan Cox
- Re: [PATCH] 2.2: /proc/config.gz Werner Almesberger
- Re: [PATCH] 2.2: /proc/config.gz Philipp Rumpf
- Re: [PATCH] 2.2: /proc/config.gz Werner Almesberger
- Re: [PATCH] 2.2: /proc/config.gz Philipp Rumpf
- Re: [PATCH] 2.2: /proc/config.gz Philipp Rumpf
- Re: [PATCH] 2.2: /proc/config.gz Werner Almesberger