From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gentoo-sources menuconfig feature/weirdness
Date: Sat, 25 Feb 2012 09:50:41 +0700 [thread overview]
Message-ID: <CAA2qdGVUtMpFtwYWuPkxZdXCX_vmq=F=UGXCVvw9OfcXfNgk2A@mail.gmail.com> (raw)
In-Reply-To: <4F48431F.10903@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
On Feb 25, 2012 9:16 AM, "Dale" <rdalek1967@gmail.com> wrote:
>
---->8snip
>
>
> That is true BUT the docs are for 100% certainty. Well, 99% at least.
> They almost always have the safest way to do anything but not
> necessarily the most used way. There are lots of things I do
> differently from the docs and my system generally works fine, except for
> the little roaches that scurry about from time to time.
>
> If you want a drop dead, almost as sure as the Sun comes up in the East
> approach, go by the docs. If you want to save some time for most
> general usage, do it the way us goofy geeks do it. Some of us know some
> neat shortcuts.
>
> Dale
>
I tend to do an 'eyeball dryrun' first: start tmux, create 2 'windows', do
make menuconfig of the older kernel in the first window, and start make
menuconfig in the second. I quickly compare the menu structure of both to
see where the implicit oldconfig might choke, do some research if
necessary, and make notes.
Then, I exit the newer menuconfig and cp the older .config to the newer src
directory, and start make menuconfig again. I keep comparing what I'm doing
against what I've done in window #1.
Never had a kernel upgrade failure this way -- touch wood!
Rgds,
[-- Attachment #2: Type: text/html, Size: 1508 bytes --]
next prev parent reply other threads:[~2012-02-25 2:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 8:10 [gentoo-user] gentoo-sources menuconfig feature/weirdness Coert Waagmeester
2012-02-23 8:25 ` Mick
2012-02-23 8:51 ` Coert Waagmeester
2012-02-23 9:17 ` Neil Bothwick
2012-02-23 10:48 ` Coert Waagmeester
2012-02-23 11:08 ` Alan McKinnon
2012-02-23 11:16 ` [gentoo-user] SOLVED " Coert Waagmeester
2012-02-23 11:25 ` Alan McKinnon
2012-02-23 12:24 ` J. Roeleveld
2012-02-23 14:04 ` Mark Knecht
2012-02-24 22:11 ` [gentoo-user] " ny6p01
2012-02-24 23:02 ` Neil Bothwick
2012-02-24 23:44 ` David W Noon
2012-02-24 23:49 ` Dale
2012-02-25 1:52 ` ny6p01
2012-02-25 2:10 ` Dale
2012-02-25 2:50 ` Pandu Poluan [this message]
2012-02-25 11:38 ` Dale
2012-02-24 22:08 ` ny6p01
2012-02-23 9:25 ` William Kenworthy
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='CAA2qdGVUtMpFtwYWuPkxZdXCX_vmq=F=UGXCVvw9OfcXfNgk2A@mail.gmail.com' \
--to=pandu@poluan.info \
--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