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 3B65A138AE9 for ; Thu, 28 Dec 2017 20:05:14 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 552BFE0DA6; Thu, 28 Dec 2017 20:05:07 +0000 (UTC) Received: from mail-qt0-f194.google.com (mail-qt0-f194.google.com [209.85.216.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E8C05E0C9A for ; Thu, 28 Dec 2017 20:05:06 +0000 (UTC) Received: by mail-qt0-f194.google.com with SMTP id a16so52284214qtj.3 for ; Thu, 28 Dec 2017 12:05:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:references:in-reply-to :message-id:mime-version:content-disposition :content-transfer-encoding; bh=JiAZ6TEXnB+6wd1jOwYrY9prwuegPhRLDUZeiWF5BKE=; b=jlD94LrMcM+ZeafMMACEsQWvyehWbNPKx4gA81O/AlYXCoYLnXWb3WxjFw275zL60N VwlAPxDten3dosqNVyecXrABoiGAZdvrcEiDl6alyP4Oi2KUQNQ46KmkqhG/CNNSs9xW XtPkEaVOYem2ayAlmn/yPpxhfIY/44qKtKoOPNnfmS2DT8LrKslW4ncaoPD9Jj8+cYWJ oY4n+TS21XmwgPJBjgOVdWMfum2n9PoOPAU+E0Dd6IKcXhaRVffYPldp+eIpjXJ+Q20t 5sRM1XcNmzJHK+FKGduO3Y4SwaRIuPM2sVY63vVeqe15GRLKo79qs7DKDdRRxHP13+/3 EQgA== X-Gm-Message-State: AKGB3mJEiOdcRpC9FuGeK20Ocnklx6SfKXehEuZbqoExONjYcg1+yjjE CPm2xssIPzvsN4HFIZcMlbKJl4QH X-Google-Smtp-Source: ACJfBot7eTrtnW2bcC56jO7YE9HN1Mzp9qS+gTsVpVllkZjnySxH8lHogGvyukWsUrhlzIgTqE9EMQ== X-Received: by 10.237.55.74 with SMTP id i68mr9853452qtb.237.1514491506005; Thu, 28 Dec 2017 12:05:06 -0800 (PST) Received: from ffortso4 (c-76-23-130-96.hsd1.ct.comcast.net. [76.23.130.96]) by smtp.gmail.com with ESMTPSA id k34sm22903584qtk.5.2017.12.28.12.05.05 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 28 Dec 2017 12:05:05 -0800 (PST) Date: Thu, 28 Dec 2017 15:05:04 -0500 From: Jack Subject: Re: [gentoo-user] Using an old kernel .config as the basis for a new .config To: gentoo-user@lists.gentoo.org References: <20171228195236.GA17094@ACM> In-Reply-To: <20171228195236.GA17094@ACM> (from acm@muc.de on Thu Dec 28 14:52:36 2017) X-Mailer: Balsa 2.5.3a-272-ge7382b30 Message-Id: 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: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Archives-Salt: c9432bf8-2d5d-4ce3-b442-daea7b24dbaf X-Archives-Hash: 8213a3e209f7026f238a5bd669305f20 On 2017.12.28 14:52, Alan Mackenzie wrote: > Hello, Gentoo. >=20 > Having just built linux-4.14.7-gentoo, suddenly a new version of the =20 > kernel, linux-4.14.8-gentoo-r1 has become stable. Configuring a =20 > kernel from scratch is a repetitive drudge. >=20 > There is some way of initialising a new kernel .config from an =20 > existing one, I am sure, but I can't find it. I've looked at the =20 > Gentoo wiki, I've looked at (some of) the kernel's own =20 > documentation. The nearest I can find is make oldconfig, which =20 > supposedly does what I want, but it just seems to start off with a =20 > default .config and go through the hundreds of questions one at a =20 > time. >=20 > So, would some kind soul please tell me how to get my old .config =20 > into a new one properly. Thanks! You need to copy your old .config into the new kernel source =20 directory. "make oldconfig" then uses those values, and only asks you =20 about new items. It sounds like it was asking about everything because =20 it didn't have the old file as a starting point - so was starting from =20 scratch. Jack=