From: tastytea <gentoo@tastytea.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] system.map file in /boot. How to manage?
Date: Thu, 1 Jul 2021 14:41:02 +0200 [thread overview]
Message-ID: <20210701144102.25331a3a@ventiloplattform.tastytea.de> (raw)
In-Reply-To: <24797.41997.225807.451604@tux.local>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
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
--
Get my PGP key with `gpg --locate-keys tastytea@tastytea.de` or at
<https://tastytea.de/tastytea.asc>.
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2021-07-01 12:41 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 [this message]
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=20210701144102.25331a3a@ventiloplattform.tastytea.de \
--to=gentoo@tastytea.de \
--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