From: Hayley <spam@foxes.systems>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: system.map file in /boot. How to manage?
Date: Fri, 02 Jul 2021 01:47:22 +1000 [thread overview]
Message-ID: <d51b7cf38b56300d9d2cf42ee9fb2c6d727a20b2.camel@foxes.systems> (raw)
In-Reply-To: <sbkm3q$1lj$1@ciao.gmane.io>
On Thu, 2021-07-01 at 15:14 +0000, Grant Edwards wrote:
> On 2021-07-01, Neil Bothwick <neil@digimed.co.uk> wrote:
>
> > make install names the files in a way that dracut and grub-mkconfig
> > recognise. Just run make install after make modules install. You've
> > let
> > the makefile copy all the other files, you may as well let it handle
> > the
> > final two :)
>
> IIRC, "make install" requiers /sbin/installkernel -- an executable
> that's provided by one of installkernel-gentoo-3, debianutils, or
> installkernel-systemd-boot. Back in the day, a base installation
> didn't have /sbin/installkernel, and you needed to install it
> manually. Has that changed?
>
> --
> Grant
>
>
The handbook says that sys-kernel/installkernel-gentoo should be
installed by default. [1]
Just throw in my 2 cents, I use genkernel to manage compiling and
installing the kernel. With a little configuring you can get it to
compile, install and run grub-mkconfig for you. That way I can't forget
to run grub-mkconfig or something.
Hayley
[1]
https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel#Installing_correct_installkernel
next prev parent reply other threads:[~2021-07-01 15:47 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 [this message]
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=d51b7cf38b56300d9d2cf42ee9fb2c6d727a20b2.camel@foxes.systems \
--to=spam@foxes.systems \
--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