From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 13AA0138330 for ; Thu, 1 Sep 2016 21:56:45 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C0B6E21C222; Thu, 1 Sep 2016 21:56:34 +0000 (UTC) Received: from smarthost03b.mail.zen.net.uk (smarthost03b.mail.zen.net.uk [212.23.1.21]) by pigeon.gentoo.org (Postfix) with ESMTP id 7E76921C0A5 for ; Thu, 1 Sep 2016 21:56:33 +0000 (UTC) Received: from [81.108.251.46] (helo=mail.digimed.co.uk) by smarthost03b.mail.zen.net.uk with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1bfZyK-0007zT-C0 for gentoo-user@lists.gentoo.org; Thu, 01 Sep 2016 21:56:32 +0000 Received: from phoucgh.digimed.co.uk (phoucgh.digimed.co.uk [192.168.1.9]) by mail.digimed.co.uk (Postfix) with ESMTPSA id E00BC53877D for ; Thu, 1 Sep 2016 22:56:31 +0100 (BST) Date: Thu, 1 Sep 2016 22:56:31 +0100 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: What's happened to gentoo-sources? Message-ID: <20160901225631.20714da4@phoucgh.digimed.co.uk> In-Reply-To: <20160901220819.7a1183df@jupiter.sol.kaishome.de> References: <3719941.fjHdSEpZyq@peak> <3696924.CMMy0m93A0@peak> <20160830083455.739cc9a1@jupiter.sol.kaishome.de> <20160830084722.009963a1@digimed.co.uk> <20160901220819.7a1183df@jupiter.sol.kaishome.de> Organization: Digital Media Production X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.30; 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_/vaPtWpnQSju9NiL=yM8Yc+3"; protocol="application/pgp-signature" X-Originating-smarthost03b-IP: [81.108.251.46] Feedback-ID: 81.108.251.46 X-Archives-Salt: 3e845f7e-1d66-46b5-b5b9-7489847ac5ee X-Archives-Hash: a668ed1f7bf58d8e69c1cab8d53aacf7 --Sig_/vaPtWpnQSju9NiL=yM8Yc+3 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Thu, 1 Sep 2016 22:08:19 +0200, Kai Krakow wrote: > > No one forced you to do anything. You 4.6 kernel was still in boot, > > your 4.6 sources were still installed. The ebuild was only removed > > fro the portage tree, nothing was uninstalled from your system unless > > you did it. Even the ebuild was still on your computer > > in /var/db/pkg. =20 >=20 > Of course nobody forced me. I just can't follow how the 4.7 ebuild > kind-of replaced the 4.6 (and others) ebuild in face of this pretty > mature oom-killer problem. >=20 > Removal of a 4.6 series ebuild also means there would follow no updates Are there any updates to the 4.6 series or was is 4.7 considered its successor by the kernels devs? If the former, I can understand your point. If the latter, there would be no updates so there is no point. > - so my next upgrade would "force" me into deciding going way down > (probably a bad idea) or up into unknown territory (and this showed: > can also be a problem). Or I can stay with 4.6 until depclean removed > it for good (which will, by the way, remove the files from /usr/src). Depclean won't remove it if you add it to world. Or you can add this to /etc/portage/sets.conf to prevent depclean removing any kernels [kernels] class =3D portage.sets.dbapi.OwnerSet world-candidate =3D False files =3D /usr/src Running old or out of date kernels is not an issue with Gentoo. I had a machine running the same kernel for at least a year, long after it was removed from the tree, because I had some hardware for which the driver wouldn't compile with newer kernels. --=20 Neil Bothwick [unwieldy legal disclaimer would go here - feel free to type your own] --Sig_/vaPtWpnQSju9NiL=yM8Yc+3 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlfIpA8ACgkQum4al0N1GQP4GwCglxN1PC7LlcJ6/LliNRo1Qwfu 1IYAoNo0NkNYVXIV9KT+shXsZuFhPFXD =Z2ul -----END PGP SIGNATURE----- --Sig_/vaPtWpnQSju9NiL=yM8Yc+3--