From: ny6p01@gmail.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gentoo-sources menuconfig feature/weirdness
Date: Fri, 24 Feb 2012 14:08:19 -0800 [thread overview]
Message-ID: <20120224220818.GA27406@badass.gateway.2wire.net> (raw)
In-Reply-To: <20120223091734.2aa3d6d0@hactar.digimed.co.uk>
On Thu, Feb 23, 2012 at 09:17:34AM +0000, Neil Bothwick wrote:
> On Thu, 23 Feb 2012 10:51:43 +0200, Coert Waagmeester wrote:
>
> > The only thing I can currently think of is maybe the kernel config
> > files in /boot?
>
> I'd say it's more likely to be getting it from /proc/config.gz.
>
> But why start with a clean config each time? That means you have plenty
> of opportunities to produce a broken kernel on every update.
>
>
> --
> Neil Bothwick
>
> This is as bad as it can get; but don't bet on it.
yea, I was thinking along those line, too. If I had to start from scratch
each update, what a chore that would be!
Terry
next prev parent reply other threads:[~2012-02-24 22:09 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
2012-02-25 11:38 ` Dale
2012-02-24 22:08 ` ny6p01 [this message]
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=20120224220818.GA27406@badass.gateway.2wire.net \
--to=ny6p01@gmail.com \
--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