From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] system.map file in /boot. How to manage?
Date: Thu, 1 Jul 2021 08:01:39 -0500 [thread overview]
Message-ID: <0772091e-1ff7-61b8-4c64-1a3efa348fff@gmail.com> (raw)
In-Reply-To: <20210701144102.25331a3a@ventiloplattform.tastytea.de>
tastytea wrote:
> On 2021-07-01 13:16+0200 Dr Rainer Woitok <rainer.woitok@gmail.com>
> wrote:
>
>> Dale,
>>
>> On Thursday, 2021-07-01 01:59:57 -0500, you wrote:
>>
>>> ...
>>> Should I version the
>>> system.map file the same as kernels?
>> Not sure about that. Mine ARE versioned. That's probably what
>> "grub- mkconfig" is doing by default.
> I compile kernels with `genkernel`, and it produces versioned files:
> System.map-5.4.97-gentoo-x86_64
> System.map-5.10.27-gentoo-x86_64
> initramfs-5.4.97-gentoo-x86_64.img
> initramfs-5.10.27-gentoo-x86_64.img
> vmlinuz-5.4.97-gentoo-x86_64
> vmlinuz-5.10.27-gentoo-x86_64
>
> Kind regards, tastytea
>
This info is helpful. I tend to do mine by hand, I may only upgrade my
kernel once, maybe twice, a year. I don't reboot very often so there is
no point in upgrading every time a new one comes out. After reading
this, I've copied over the proper system.map files and versioned them to
match the kernel names. I'll run grub-mkconfig just in case shortly.
I've always had *A* file there but never copied newer versions over
before. Honestly, I didn't know if it was needed or not. It has a lot
of info in it tho so I figured it wise to ask.
Thanks to all for the info. Now I have a better understanding of what I
need to do and how.
Dale
:-) :-)
P. S. Back to the woods. Putting out fertilizer for the trees.
Supposed to rain in the next day or so.
next prev parent reply other threads:[~2021-07-01 13:01 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 [this message]
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=0772091e-1ff7-61b8-4c64-1a3efa348fff@gmail.com \
--to=rdalek1967@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