From: Andrew Lowe <agl@wht.com.au>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Fwd: Creating a custom kernel from a -bin kernel
Date: Sun, 6 Oct 2024 22:16:46 +0800 [thread overview]
Message-ID: <bceac387-0b94-0723-d72e-dcc12781bf1a@wht.com.au> (raw)
In-Reply-To: <379cf455-3ff3-47ad-4d0e-7d4a38920e37@wht.com.au>
For some reason this didn't go through yesterday so, once again......
-------- Forwarded Message --------
Subject: Creating a custom kernel from a -bin kernel
Date: Sat, 5 Oct 2024 18:55:50 +0800
From: Andrew Lowe <agl@wht.com.au>
Reply-To: agl@wht.com.au
Organization: Wombat High Tech
To: gentoo-user@lists.gentoo.org
Dear all,
I'm in the process of building a new machine. To get things up and
running I've decided to go with the gentoo-sources-bin kernel initially,
then once I get things basically working as I want I will go back to
building my kernels manually.
I've now reached that point, "hand rolling" the kernel, but it is a
pain, the first time round, getting things right.
I have a recollection of reading somewhere online mention of a script
that will take the .config file from the "-bin" kernel and then
modprobe, I think, each listed module in turn to see if it is actually
being used and subsequently writing a new .config file that now only
contains the modules/options that the specific machine needs.
Is this a mythical script that I have dreamt up after a long day and
too much chocolate or does it actually exist and does anyone have a link.
Thanks for any thoughts,
Andrew
next parent reply other threads:[~2024-10-09 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <379cf455-3ff3-47ad-4d0e-7d4a38920e37@wht.com.au>
2024-10-06 14:16 ` Andrew Lowe [this message]
2024-10-09 22:08 ` [gentoo-user] Fwd: Creating a custom kernel from a -bin kernel Michael
2024-10-09 22:23 ` [gentoo-user] " Peter Böhm
2024-10-10 0:44 ` [gentoo-user] Fwd: " Eli Schwartz
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=bceac387-0b94-0723-d72e-dcc12781bf1a@wht.com.au \
--to=agl@wht.com.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