public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] system.map file in /boot. How to manage?
Date: Thu, 1 Jul 2021 15:22:27 +0800	[thread overview]
Message-ID: <cfb79bd4-727c-8efc-c87e-1e93b4e0de6b@iinet.net.au> (raw)
In-Reply-To: <e6e3d981-66a4-989e-2c34-3807287e9ea1@gmail.com>

There is a lot online - basically its optional and needed just in case
(!) and should be versioned like its matching kernel and initrd.

BillK

one of many refs:
https://stackoverflow.com/questions/28936630/what-is-the-need-of-having-both-system-map-file-and-proc-kallsyms


On 1/7/21 2: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
>
> :-)  :-) 
>


  reply	other threads:[~2021-07-01  7:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-01  6:59 [gentoo-user] system.map file in /boot. How to manage? Dale
2021-07-01  7:22 ` William Kenworthy [this message]
2021-07-01 11:16 ` Dr Rainer Woitok
2021-07-01 12:41   ` tastytea
2021-07-01 13:01     ` Dale
2021-07-01 14:28   ` Neil Bothwick
2021-07-01 14:41     ` Dale
2021-07-01 15:04       ` Neil Bothwick
2021-07-01 15:14         ` [gentoo-user] " Grant Edwards
2021-07-01 15:47           ` Hayley
2021-07-01 15:13       ` [gentoo-user] " antlists
2021-07-01 15:13     ` Dr Rainer Woitok
2021-07-02 23:07 ` Daniel Frey
2021-07-02 23:54   ` Dale
2021-07-03  9:11     ` J. Roeleveld

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cfb79bd4-727c-8efc-c87e-1e93b4e0de6b@iinet.net.au \
    --to=billk@iinet.net.au \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox