From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 7E5F81381F3 for ; Sun, 28 Apr 2013 17:52:11 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 99C0CE09D4; Sun, 28 Apr 2013 17:52:00 +0000 (UTC) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by pigeon.gentoo.org (Postfix) with ESMTP id 64483E09A5 for ; Sun, 28 Apr 2013 17:51:59 +0000 (UTC) Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r3SHpv2C005362 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 28 Apr 2013 13:51:58 -0400 Received: from [10.10.55.30] (vpn-55-30.rdu2.redhat.com [10.10.55.30]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r3SHpunN008549 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Sun, 28 Apr 2013 13:51:57 -0400 Message-ID: <1367171516.2194.197.camel@localhost> Subject: Re: [gentoo-user] why my system is keeping old kernel around? From: Randy Barlow To: gentoo-user@lists.gentoo.org Date: Sun, 28 Apr 2013 13:51:56 -0400 In-Reply-To: <517D5291.4020407@gmail.com> References: <20130428011949.GA14514@syscon7.inet> <20130428092917.7e5e882c@digimed.co.uk> <1367165208.2194.186.camel@localhost> <517D5291.4020407@gmail.com> Content-Type: text/plain; charset="UTF-8" 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-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.25 X-Archives-Salt: 62a544ba-648e-4d77-a664-10e49daa1824 X-Archives-Hash: 9cf60d58df4cd6021fa92342a0e7442a On Sun, 2013-04-28 at 18:47 +0200, Alan McKinnon wrote: > By far the most likely cause is you type > > emerge =gentoo-sources- > > and forget to use the -1 option. It's the same thing that results in > packages called *lib* in world Yeah, I knew that doing this would cause what I was talking about, but I don't recall ever having using a specific version in a kernel emerge command. I guess it's possible I just don't remember doing it, but it happens often enough that I don't think this is why. I'll try to pay attention to the contents of world and see if I can pinpoint an action that is doing this. Thanks! -- Randy Barlow