From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1S0Up7-0000tD-1j for garchives@archives.gentoo.org; Thu, 23 Feb 2012 09:18:49 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7FFC6E0B9E; Thu, 23 Feb 2012 09:18:38 +0000 (UTC) Received: from mail.digimed.co.uk (82-69-83-178.dsl.in-addr.zen.co.uk [82.69.83.178]) by pigeon.gentoo.org (Postfix) with ESMTP id C17B5E0AF0 for ; Thu, 23 Feb 2012 09:17:39 +0000 (UTC) Received: from hactar.digimed.co.uk (hactar.digimed.co.uk [192.168.1.3]) by mail.digimed.co.uk (Postfix) with ESMTPSA id B621D8075F for ; Thu, 23 Feb 2012 09:17:38 +0000 (GMT) Date: Thu, 23 Feb 2012 09:17:34 +0000 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] gentoo-sources menuconfig feature/weirdness Message-ID: <20120223091734.2aa3d6d0@hactar.digimed.co.uk> In-Reply-To: <4F45FE1F.9070006@waagmeester.co.za> References: <4F45F490.2020504@waagmeester.co.za> <201202230826.00642.michaelkintzios@gmail.com> <4F45FE1F.9070006@waagmeester.co.za> Organization: Digital Media Production X-Mailer: Claws Mail 3.8.0cvs29 (GTK+ 2.24.10; x86_64-pc-linux-gnu) X-GPG-Fingerprint: 7260 0F33 97EC 2F1E 7667 FE37 BA6E 1A97 4375 1903 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/FJx6Yyl4OdUZFBqTL/B_Er6"; protocol="application/pgp-signature" X-Archives-Salt: dd3fb0fe-cbc8-4ab0-890d-742198053679 X-Archives-Hash: 186000217b234cd1c0e0123b2e7300b2 --Sig_/FJx6Yyl4OdUZFBqTL/B_Er6 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable 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. --=20 Neil Bothwick This is as bad as it can get; but don't bet on it. --Sig_/FJx6Yyl4OdUZFBqTL/B_Er6 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAk9GBDIACgkQum4al0N1GQOMAACgwM12FPToTAJhbC0aVxL0QOEV sF0An2Nu+MdFz8cjKNkQLsoHkEgxf+Kc =6mLb -----END PGP SIGNATURE----- --Sig_/FJx6Yyl4OdUZFBqTL/B_Er6--