SlackwareThis Forum is for the discussion of Slackware Linux.
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.
A simple question with a non-simple answer, posed numerous times
is what do I do with System.map?
I am getting ready to compile the 2.6.13 kernel from source and
I want to be sure that I can get back to my old kernel 2.4.31 should
something go wrong. My present /boot (rearranged slightly for readability) is:
You'll notice that symlinks haven't been changed from the original kernel and
the newly compiled kernel (newlinux) has no associated 'System.map' or 'config'.
This doesn't pose a problem since klogd will search the following for System.map:
Any other programs that need System.map access will presumably do the same.
However, if I compile a new 2.6.13 kernel, I will either have to copy the System.map
to /boot or change the symlink /usr/src/linux to point to /usr/src/linux-2.6.13
instead of /usr/src/linux-2.4.31 in order for klogd (& any others) to find the
2.6.13 System.map. Either way, I wish to keep my ability to load either kernel
with the applicable System.maps.
What is the best way to insure this?
1. Copy all System.maps to boot with version nos? What about symlinks?
2. Put the 2.6.13 kernel and associated System.map in another directory?
3. Something else?
Anyone know what the 'map' file is?
Do I need an initrd if I compile everything I need into the new 2.6.13?
I assume this is only needed if you load a stock 2.6.13 kernel and say
have a Reiser fs.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.