Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I then copied System.map from /usr/src/linux (linked to linux-2.4.21-0.25mdk) to /boot and renamed it to System.map-2.4.21-0.25mdkcustom. I deleted the old System.map symbolic link and replaced it with a System.map linked to the 0.25 map. When I reboot, the new system.map is gone and the System.map link is pointing to the 0.13 map. I am doing all of this from within Kde.
What is going on? How do I use the 0.25 System.map?
'man lilo-conf' says this about the map param:
Specifies the location of the map file. If `map' is omitted, the
file /boot/map is used.
On machines with a pre-1998 BIOS, the EDD bios extensions which
are required to support "lba32" disk sector addressing may not
be present. In this case, the boot-loader will fall back auto-
matically to "geometric" addressing; this fall back situation,
or the specific use of "geometric" or "linear" addressing, will
require the map file to be located within the first 1024 cylin-
ders of the disk drive. This BIOS limitation is not present on
post-1998 systems, most of which support the newer EDD disk BIOS
There is a /boot/map which has a timestamp the same as the last time I ran lilo.
'man lilo' says this about the '-q' parameter:
-q List the currently mapped files. lilo maintains a file, by
default /boot/map, containing the name and location of the ker-
nel(s) to boot. This option will list the names therein. Use
with -v for more detailed information about the installed boot
So, from the above it looks like changing the map parameter may make my system unbootable (?). Any other suggestions?
It is not as if I am having problems (eg. no odd behaviour or mysterious crashes, yet..). It is just that I think I am supposed to have System.map pointing to the correct file for the kernel.
"So, from the above it looks like changing the map parameter may make my system unbootable (?). "
Every time I compile a kernel I run for a while with two kernels and two map files and I don't use symbolic links. Currently I am running with a single kernel and:
I have never had any problems with changing the lilo.conf from one map to the other so I do not think that your system will crash. However there is obviously something wrong with your system and I cannot guarentee that it will not crash if you play around with the map names.
You could safely experiment by creating boot floppies that reference the map directly without using a symbolic link.
I think your right, there is something wrong. I deleted the System.map link file and copied my custom System.map file to /boot/System.map-blah-blah and rebooted. I went to /boot and System.map-blah-blah was not there. Also, a new link file was not created. Anyway, I will try it with a boot floppy (should make one anyway).