Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When I installed a new kernel, the documentation said that I should copy the System.map and vmlinuz to /boot directory. I know vmlinuz is the kernel file, but am curious to know what System.map file is.
I figured it was done by the suffix of the System.map file, If you boot a kernel thats not the default the link will not be used and it will use the one with the same version suffix..
but then theres the map.0301 and map.0341 files in the /boot folder of one of my systems which I don't know about, and on my laptop I have just one file called /boot/map without the suffix.
as far as i understand it, the System.map file contains the locations of all the functions active in the compiled kernel. the file can be named using versions - like System.map-2.4.5 or whatever version you happen to have.
i think it's there because on a modular kernel like linux, there needs to be a file to keep track of the locations of each kernel module, and where it's located or where it's inserted. i think .
Distribution: Slackware 10, Fedora Core 3, Mac OS X
Posts: 617
Rep:
things don;t break if you just use the one System.map for different versions of the kernel.
I always use the System.map that is created with my most recent kernel recompile and the old, backup kernel (2.2.14) works fine (except it complains because my startup scripts that load modules can't find them since they havn't been compiled in).
I just set up a new system. I upgraded it to the 2.4.9-12 kernel
It removed the /boot/boot.b file somehow.
I began by converting to ext3 fs when I saw the kernel did not support it(2.2-2)
lilo complained about it being gone. I removed it from the lilo.conf file and running lilo still it complained about it. So I copied the boot.b file from another system. Then lilo complained about the linear line in lilo.conf which I changed to lba32 and now everything is ok.
Though I managed to get it working I am still a bit confused.
Thanks folks for your replies,
but I think I am going nowhere as far as System.map file is concerned. The only reason why I have an issue with this file is because when I build a new kernel, I have two kernel files (one new and one old), two system.map files. I know where and how to use kernel files, but am confused about the usage of system.map.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.