From: Daniel Frey <djqfrey@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] system.map file in /boot. How to manage?
Date: Fri, 2 Jul 2021 16:07:09 -0700 [thread overview]
Message-ID: <337d6a33-4e6a-ea1a-b26f-8a675313423e@gmail.com> (raw)
In-Reply-To: <e6e3d981-66a4-989e-2c34-3807287e9ea1@gmail.com>
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
next prev parent reply other threads:[~2021-07-02 23:07 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
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 [this message]
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=337d6a33-4e6a-ea1a-b26f-8a675313423e@gmail.com \
--to=djqfrey@gmail.com \
--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