[Solved] i removed my System.map files out of /boot

Sade · Last edited by Sade on Mon Apr 11, 2005 8:06 am; edited 1 time in total

[help] i removed my System.map files out of /boot
Stupid, stupid, stupid, but a fact. i erased them, (accept the symlinks)

How can i get them back?
the system won't boot anymore. I'm chrooted in atm.
_________________
| 1.6Ghz atom N270 | adopt an unanswerd post | a nice way to post a config file |

tomvollerthun · Guru Joined: 19 Mar 2005 Posts: 316

I have never heard of anyone getting problems because of removing System.map.
Perhaps it still is in your kernel's source dir, i.e. /usr/src/linux/System.map .

Could you post the error message you received, even if your system comes to life again? Just out of curiosity ;)
_________________
Computer science is no more about computers than astronomy is about telescopes.
Dijsktra
---------------
Don't believe my "Guru" status!

Frodg · l33t Joined: 11 Feb 2004 Posts: 761

true,
but just copy it back. I fear you may have deleted more than the system.map if it won't boot......
_________________
Aerosolo ergo sum - I spray therefore I am

Gentoo - Registered Linux User # 361400

Sade · Posted: Mon Apr 11, 2005 8:06 am Post subject:

well i removed System.map* so i removed some more.
But i did a kernell recompile, and no all is normal again.

the grub error was (out of memory sorry).
error [15]
files are missing.
_________________
| 1.6Ghz atom N270 | adopt an unanswerd post | a nice way to post a config file |

tomvollerthun · Guru Joined: 19 Mar 2005 Posts: 316

So perhaps it was more something like the initrd or the kernel you've deleted (perhaps a space between the System.map and the * ?)
Good to hear it works again.
_________________
Computer science is no more about computers than astronomy is about telescopes.
Dijsktra
---------------
Don't believe my "Guru" status!

Pink · Veteran Joined: 24 Jul 2003 Posts: 1062

I can safely say it is nothing to do with the System.map being removed.

You only need to put the bzImage/vmlinux into the /boot partition. Putting the SYstem.map file there makes no difference to anything whatsoever.

Anyway, glad you got it sorted, here is a link to a thread about the System.map (and it's complete redundency of putting it into /boot): see here

The links in the thread give some good info, but the main point is that there is no need and certainly no point in putting the System.map in /boot.

I'm not trying to start a particular discussion about it (that could be done in the link I have posted) but just to let you know that whatever you did had absolutely nothing to do with the System.map

Just ensure the 'linux' symlink points to the working kernel.