Messages in this thread |  | | Date | Fri, 1 Sep 2000 14:10:16 +0200 | From | "Andi Kleen" <> | Subject | Re: [PATCH] 2.2: /proc/config.gz |
| |
On Fri, Sep 01, 2000 at 02:04:44PM +0200, almesber@lrc.di.epfl.ch wrote: > 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.
I'm not sure I understand the question. It would basically work like booting in BSD or most other Unixes: the bootloader knows ext2 and reads a filename that you pass as a command line option or a default from /. That file name would be available in the environment that is passed to init.
So nm $KERNELNAME should work usually to get the symbol table of the currently running kernel.
> Also, I' very sceptical about anything that requires non-trivial updates > to all boot loaders.
I guess a single bootloader that supports it optionally would be enough for Daniel-Phillips-who-cannot-remember-where-he-put-his-System-maps ;)
Of course bzImage would still be the standard way to boot.
-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/
|  |