I'm experimenting with generating some custom kernels using genkernel.
However, each iteration leaves a file in /boot called System.map-genkernel-<arch>-<version>.
Is it safe to rename and/or delete the System.map-* files?
Add a comment |
1 Answer
The System.map file is mainly used to debug kernel crashes. It's not actually necessary, but it's best to keep it around if you're going to use that kernel. If you've decided you don't need that kernel, then it's safe to delete the corresponding map file.
If you're really low on disk space, you could compress the map files. They aren't that big, so this won't save much space, but bzip2 will squeeze them down to about 25% of the original size. Then you can uncompress one if you discover that you need it.
- @cjm what if, after a certain time of continuous use (let's say, 2 weeks), I felt the kernel is stable and in no need of debugging. Is it safe to delete the
System.mapthen?pepoluan– pepoluan2011-03-24 08:33:14 +00:00Commented Mar 24, 2011 at 8:33 - Why do you want to delete it?J. Taylor– J. Taylor2011-03-24 08:42:45 +00:00Commented Mar 24, 2011 at 8:42
- 1Why not delete it at the same time as deleting the kernel?Mikel– Mikel2011-03-24 08:52:55 +00:00Commented Mar 24, 2011 at 8:52
- @jrtayloriv /boot is getting fullpepoluan– pepoluan2011-04-01 08:25:11 +00:00Commented Apr 1, 2011 at 8:25
- 2I'm not saying don't keep one or two known good kernels, in fact I would suggest you do. What I am suggesting is that when you delete a kernel, delete the map file for that kernel. The map files are only about 1.8 MB. Delete them if you have to, but if you've got more than two or three kernels, it might be time to delete a kernel and a System.map together.Mikel– Mikel2011-04-01 09:21:28 +00:00Commented Apr 1, 2011 at 9:21