From: Roy Bamford <neddyseagoon@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Vanilla sources
Date: Sun, 05 Jan 2020 10:34:26 +0000 [thread overview]
Message-ID: <UWZTRNE3.LXOCD7EE.JP5K2YVH@DSPI4F34.J4V2S4WE.FVS7GMAR> (raw)
In-Reply-To: <6eeea4ce-f117-9c9f-8505-7a22f5649342@gentoo.org> (from whissi@gentoo.org on Sat Jan 4 13:43:04 2020)
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
On 2020.01.04 13:43, Thomas Deutschmann wrote:
> On 2020-01-04 14:08, Roy Bamford wrote:
> > emerge -1 vanilla-sources
> > eselect kernel ...
> > genkernel all
> > ...
>
> Please tell user to do
>
> genkernel --kernel-config=/proc/config.gz all
>
> by default which will give them a better experience because new kernel
> will be build based on kernel configuration from current running
> kernel.
> Without providing a kernel config, user will probably fall back to
> generic configuration which isn't intended for daily usage.
>
>
> --
> Regards,
> Thomas Deutschmann / Gentoo Linux Developer
> C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
>
>
Thomas,
Ten years ago the user did
genkernel all
and used the default .config provided with genkernel.
Today, genkernel --kernel-config=/proc/config.gz all does not improve
that config.
genkernel --kernel-config=/proc/config.gz all
perpetuates the existing .config which is only useful if its not an
earlier generic configuration.
--
Regards,
Roy Bamford
(Neddyseagoon) a member of
elections
gentoo-ops
forum-mods
arm64
[-- Attachment #2: Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-01-05 10:35 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-28 7:09 [gentoo-dev] Keywordreqs and slacking arch teams Michał Górny
2019-12-28 9:27 ` Kent Fredric
2019-12-28 9:35 ` Fabian Groffen
2019-12-28 11:05 ` Kent Fredric
2019-12-28 11:14 ` Michael 'veremitz' Everitt
2019-12-28 11:27 ` Kent Fredric
2019-12-28 11:40 ` James Le Cuirot
2019-12-28 11:44 ` Kent Fredric
2019-12-28 11:32 ` Kent Fredric
2019-12-28 11:35 ` Michael 'veremitz' Everitt
2019-12-28 11:42 ` Kent Fredric
2019-12-28 18:05 ` Alec Warner
2019-12-29 2:19 ` Aaron Bauman
2019-12-29 5:09 ` Kent Fredric
2019-12-30 1:45 ` A Schenck
2020-01-02 20:32 ` Rolf Eike Beer
2020-01-02 23:25 ` Mike Pagano
2020-01-02 23:35 ` Rolf Eike Beer
2020-01-03 0:19 ` Michael 'veremitz' Everitt
2020-01-03 2:40 ` Aaron Bauman
2020-01-03 10:00 ` Rolf Eike Beer
2020-01-04 11:09 ` Rolf Eike Beer
2020-01-04 11:25 ` Michael 'veremitz' Everitt
2020-01-04 13:35 ` Rolf Eike Beer
2020-01-03 14:37 ` [gentoo-dev] Vanilla sources Michael Orlitzky
2020-01-03 14:40 ` Toralf Förster
2020-01-03 14:41 ` Michael Orlitzky
2020-01-03 14:46 ` Rich Freeman
2020-01-03 14:48 ` Toralf Förster
2020-01-03 22:32 ` Michael 'veremitz' Everitt
2020-01-04 7:38 ` Hanno Böck
2020-01-04 18:39 ` William Hubbs
2020-01-04 18:41 ` Michał Górny
2020-01-07 8:52 ` Hanno Böck
2020-01-03 14:52 ` Michael Orlitzky
2020-01-03 14:55 ` Michael Orlitzky
2020-01-03 16:28 ` Aaron Bauman
2020-01-04 11:01 ` Rich Freeman
2020-01-04 11:42 ` Roy Bamford
2020-01-04 12:54 ` Rich Freeman
2020-01-04 13:08 ` Roy Bamford
2020-01-04 13:43 ` Thomas Deutschmann
2020-01-05 10:34 ` Roy Bamford [this message]
2020-01-04 20:13 ` Christopher Head
2020-01-04 20:39 ` Rich Freeman
2020-01-04 13:47 ` Thomas Deutschmann
2020-01-04 18:41 ` William Hubbs
2020-01-04 18:42 ` Michał Górny
2020-01-04 19:13 ` Rolf Eike Beer
2020-01-05 16:41 ` Michael Orlitzky
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=UWZTRNE3.LXOCD7EE.JP5K2YVH@DSPI4F34.J4V2S4WE.FVS7GMAR \
--to=neddyseagoon@gentoo.org \
--cc=gentoo-dev@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