Messages in this thread | | | Date | Thu, 17 Jun 1999 17:16:59 +0100 | From | Raiden <> | Subject | RE: System.map |
| |
At 17.14 16/6/99 +0200, Ward Vandewege wrote: >At 10:56 16/06/99 -0400, you wrote: >>I still think a better solution would be to store System.map in the >>/lib/modules/KVER heirarchy. It would be a much easier way to boot various >>kernels and be assured the correct map file > >This _is_ already possible. Just do the following: > >Rename your System.map file to System.map-2.2.10 >Rename your bzImage or whatever to vmlinuz-2.2.10 > >Adjust lilo.conf. No more need for a System.map file: when booting, the >kernel will understand System.map-2.2.10 is the companion of vmlinuz-2.2.10 >and use it. >This way you can use any number of kernel versions with the correct map file. > > >Hope this helps, >Ward.
Yeah :) but that dont fix problem on tree structure on distributions.
> > >- >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in >the body of a message to majordomo@vger.rutgers.edu >Please read the FAQ at http://www.tux.org/lkml/ >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |