public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Testing new kernels - saving dumps / strip down kernel options
Date: Fri, 11 Jan 2013 06:28:21 +0000	[thread overview]
Message-ID: <91D93B9A-E018-4FCD-8FD4-279827D6FBAF@stellar.eclipse.co.uk> (raw)
In-Reply-To: <50EC0D98.6070104@xunil.at>


On 8 January 2013, at 12:14, Stefan G. Weichinger wrote:
> …
> * I remember a thread here where this was discussed already:
> 
> How do you guys get to your .config for a recent kernel? "make
> oldconfig" doesn't always work out best, I recall?
> 
> My kernel config is maintained along for years now and has survived
> several hardware changes. I don't have any obvious problems but I wonder
> if I have something in there that is deprecated and might be better
> thrown out.
> 
> Does it make sense to take the .config from the gentoo install dvd for
> example and remove all the stuff I don't have?

I most always take the .config from a recent systemrescuecd and it has always worked well for me.

I change "processor type and features" and disable the initrd. 

There may be some stuff on a LiveCD based distro which is optimised for running off an optical disk, so I guess a RedHat or Ubuntu default .config might be better.

These should provide everything you need to boot, and most everything else as modules, which will be automatically loaded. IMO this is pretty much optimal.

The engineers at RedHat and Ubuntu know a heck of a lot more about kernels than I do. One might be able to make one's kernel milliseconds more efficient by tuning it by hand, but it will surely take hours of tinkering to attain that.

I do not believe you can properly understand the consequences of any given kernel option merely by reading the one- or two-line description in makeconfig's help. To *properly* customise a kernel for oneself will take more research than that, I reckon.

Stroller.

  parent reply	other threads:[~2013-01-11  6:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 12:14 [gentoo-user] Testing new kernels - saving dumps / strip down kernel options Stefan G. Weichinger
2013-01-10  9:38 ` [gentoo-user] " Nuno J. Silva
2013-01-11  6:56   ` Stefan G. Weichinger
2013-01-11  6:28 ` Stroller [this message]
2013-01-11  6:59   ` [gentoo-user] " Stefan G. Weichinger

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=91D93B9A-E018-4FCD-8FD4-279827D6FBAF@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --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