Re: having System.map reflect the running kernel
Todd Fries (tfries@umr.edu)
Thu, 31 Aug 1995 00:47:50 +0000 (GMT)
> Then, after booting and fsck'ing root, the kernel needs to know where it came
> from...then some script after bootup could make a copy of a running kernel
> into a constant, known file (uncompressing and stripping off the boot
> sequence in compressed images...).
>
> This strategy can also work with lilo/vmlinuz kernels (i.e. images of
> kernels can be copied to a know location or linked. So all tools which want to
> read the kernel symbols will know where to go (instead of specifying an
> image name if the default isn't used).
>
>
> I'd rather forget about the system.map stuff and just get kernel symbols
> in a normal way (in the image).../proc/image doesn't need to have the symbol
> table...
This is all fine and dandy, but what happens if someone like me ftp's a kernel
image and loadlin.exe onto a novell drive on a hd'less pc, and loads the kernel,
and uses a floppy drive as root? I seriously doubt that the kernel would be
found anywhere after this.
--
Todd Fries...tfries@umr.edu
http://www.cs.umr.edu/~tfries