Awhile ago I asked a question about a mismatch between my newly compiled kernel, and the system.map. One of the Suse experts said that the system.map was inconsequential. OK, and I've been going along fine until today I tried to run lsof and I'm getting errors saying "kernel and system.map are mismatched" So how do I make my system.map current? - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
-----BEGIN PGP SIGNED MESSAGE----- On 08-Jan-99 zentara wrote about the following [SuSE Linux] System.map revisited. : || || Awhile ago I asked a question about a mismatch || between my newly compiled kernel, and the system.map. || || One of the Suse experts said that the system.map was || inconsequential. || OK, and I've been going along fine until today || || I tried to run lsof and I'm getting errors saying || "kernel and system.map are mismatched" || || So how do I make my system.map current? I have seen that problem come up from time to time... Simply, you pull the file, /usr/src/linux/System.map and place that in /boot and name is something like /boot/System.map.2.1.132 (or some other logical convention that works for you. This is assuming that you are somewhat like me, and have multiple boot kernels. If not, then copy System.map as /boot/map, run lilo and you should be good to go. As a standard practice, the current boot kernel's system map is automatically put into /boot after you finish with the compilation. If you are running multiple boot kernels, then there is a simple way of handling that. Like I mentioned above, name your System.map file into something logical and place it in /boot. Add to your lilo.conf a map option for each kernel that you are supporting, ie: image = /boot/vmlinuz root = /dev/sda1 label = linux map = /boot/System.map-2.1.132 # image = /boot/vmlinuz.old root = /dev/sda1 label = linux-stable map = /boot/System.map-2.0.35 # image = /boot/vmlinuz-2.0.36 root = /dev/sda1 label = linux-2.0.36 map = /boot/System.map-2.0.36 Run lilo and you will be good to go! Hope this answered your question... - --- Kim C. Callis -- kcc@ziplink.net ********************************* * When it absolutely, * * Positively has to be * * Destroyed over night! * * * * (800) MARINES * ********************************* -----BEGIN PGP SIGNATURE----- Version: PGP for Personal Privacy 5.0 Charset: noconv iQCVAwUBNpbFMiaI5lr1ZTHJAQFYKgP/eq4Mps5v+w8bPqoBvzh7T/LzDFmIn8TO dVAdQ3WNTkGtCXDOK+06quoXRmjBDNOKMHC+HphT5x7d6T4uwlgYmIEkxpXCGEWO 98tox6o4vuxrcN3YCR90mp2TTQn+sc1kIwmuwka76509k6Y5KEikP+l8TlRuK2P3 RhCiAkvQzYg= =UlHd -----END PGP SIGNATURE----- - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Kim C. Callis wrote:
Add to your lilo.conf a map option for each kernel that you are supporting, ie:
image = /boot/vmlinuz root = /dev/sda1 label = linux map = /boot/System.map-2.1.132 #
Well, you learn something new every day. (Regarding the other topics on the list about rtfm and stuff) I didn't know that there's a "map" option in lilo. Just curious why you put your stuff in /boot. Is this "standard" for 2.2.*, personal prefference or adapted from redhat? Juergen -- ========================================== __ _ Juergen Braukmann mail: brauki@cityweb.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu| /\\ /__/ / _ \/ // /\ \/ / ==========================================_\_v __/_/_//_/\_,_/ /_/\_\ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Kim C. Callis wrote:
|| || Just curious why you put your stuff in /boot. Is this "standard" for || 2.2.*, personal prefference or adapted from redhat?
Ok, I admit it! I stole the idea to place my stuff in /boot from RedHat... I am slightly anal about the / directry being clean of everything except directories. Hence, I jumped on RedHat's layout of keeping kernel et. al. in /boot.
Today, i thought of doing the same. I am experimenting with my not yet working zip drive (see my other thread) and all these "just in case" saved kernels and map files spoil my root dir. /boot seems to be a good carpet to brush this stuff under. :) Juergen -- ========================================== __ _ Juergen Braukmann mail: brauki@cityweb.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu| /\\ /__/ / _ \/ // /\ \/ / ==========================================_\_v __/_/_//_/\_,_/ /_/\_\ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
participants (3)
-
brauki@cityweb.de
-
kcc@ziplink.net
-
zentara@netfrog.net