Re: [gentoo-user] system.map file in /boot. How to manage?

["J. Roeleveld" <joost@antarean.org>]

On Saturday, July 3, 2021 1:54:13 AM CEST Dale wrote:
> Daniel Frey wrote:
> > On 6/30/21 11:59 PM, Dale wrote:
> >> Howdy,
> >> 
> >> The subject line pretty much describes this.  How does one manage the
> >> system.map file in /boot?  Is it needed?  Should it be updated with each
> >> kernel?  I tend to keep 2 to 3 kernels installed.  I tend to keep 2 that
> >> I know are stable and one testing.  After a while, I may remove the
> >> oldest one and only have two, just in case.  Should I version the
> >> system.map file the same as kernels?  Does just one with no version get
> >> the job done?  Update the file with each kernel upgrade or install one
> >> and done?
> >> 
> >> While at it, what does it even do?  If it needs it, it doesn't matter
> >> but just curious.
> >> 
> >> Thanks for any tips on this.
> >> 
> >> Dale
> >> 
> >> :-)  :-)
> > 
> > I never copy it over unless I have some kernel panic (so not for well
> > over a decade.) So there's nothing for me to manage (I only copy the
> > kernel and kernel config to /boot.)
> > 
> > Dan
> 
> So if it isn't there or something, it isn't going to break anything. 
> That's good to know too. 

I only copy the kernel image (and initrd if required)
I haven't done anything with the System.map or config (apart from keeping it 
updated for compiling the kernel) in over a decade.

My boot-partition isn't even mounted unless I update the kernel, so a file 
there wouldn't even be visible to the system.

--
Joost