Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp14836650ybl; Mon, 30 Dec 2019 18:34:31 -0800 (PST) X-Google-Smtp-Source: APXvYqwh+91gWPBeZHf+ewrdkIUdJeEfXgvg0lFJKYGBCMF1QEfFxf1gJS3GeCCZUPtGYnKpFikm X-Received: by 2002:a9d:7f12:: with SMTP id j18mr80853229otq.17.1577759671816; Mon, 30 Dec 2019 18:34:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1577759671; cv=none; d=google.com; s=arc-20160816; b=r0umK9wv3FDOxhee25tDpstnLh6ZlAtvLGGzyj4PymVwUNPloG8NA82Yz3RVpw0ZxB Up+fSa7EesODkcosqJlgC2GbEVejlxxXivcfEbuvcj6i9g9xKpf+2JxhIwGI530OMP+5 kJchvPMr/46c0iiCpUpXWuBrZUvJQhu+cdr7DtnbPFNyeebZEih3zUn/WZEZWWTuDaCm +s/TA0g4TnyZfgTj6AB3MYkPl1oMUeFPrJmQ6dPCj75KG7kWeWiJYWPChE0DcONDNk/k 9AG7Enxos2zny4mAoPefdro4N8Gqu4Rtn9P9Mn9x1FSPlsaNj/fwHVpkCAA2/xK4hYqt 8xTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=aTBwODG71y2JP56EG2YM5hgjko3ah049/AFhK+DDt24=; b=fEwmBP5j4QhltiAFypAAWOmCIXnKzdf+fg+jHgJYVdgh6gHw4RmljnOpyx8DXqjBym U8fHFSYwDe+t6JieuXxT+CAzclCYm/Qj9VmogyD5WLWYOHVCQ8lpGx7DAlCXFycMAZb6 ng6aGgTON5wsQxNp17dkMvof/SSxIkP4D/rr6mAjJm1rlJI7ceamM487e3vlyDoZkhss 6NICL/SNfHZEfVya5cgrS2kzrcXK91m3JjgLZZauWEfoJCnGwBjeHUF9QALzA50rjvcH vRzGhYWtKu9sSaeti+4es9DpAU0z4Qo53B81ywqtTstrl8Btb2cJ28LoBMUznyikBeVY loRA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s18si3779674otr.172.2019.12.30.18.34.18; Mon, 30 Dec 2019 18:34:31 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726538AbfLaCd1 (ORCPT + 99 others); Mon, 30 Dec 2019 21:33:27 -0500 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:58291 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725536AbfLaCd1 (ORCPT ); Mon, 30 Dec 2019 21:33:27 -0500 Received: from callcc.thunk.org (96-72-102-169-static.hfc.comcastbusiness.net [96.72.102.169] (may be forged)) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id xBV2XE93024338 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 30 Dec 2019 21:33:15 -0500 Received: by callcc.thunk.org (Postfix, from userid 15806) id 5BEAF420485; Mon, 30 Dec 2019 21:33:14 -0500 (EST) Date: Mon, 30 Dec 2019 21:33:14 -0500 From: "Theodore Y. Ts'o" To: Randy Dunlap Cc: Rob Landley , linux-kernel@vger.kernel.org Subject: Re: Why is CONFIG_VT forced on? Message-ID: <20191231023314.GC3669@mit.edu> References: <9b79fb95-f20c-f299-f568-0ffb60305f04@landley.net> <018540ef-0327-78dc-ea5c-a43318f1f640@landley.net> <774dfe49-61a0-0144-42b7-c2cbac150687@landley.net> <8059d1c4-759d-9911-73c7-211f8576e7f2@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8059d1c4-759d-9911-73c7-211f8576e7f2@infradead.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 30, 2019 at 06:03:26PM -0800, Randy Dunlap wrote: > > > > So if I disable CONFIG_EXPERT, using miniconfig I then need to manually switch on: > > > > ./init/Kconfig: bool "Namespaces support" if EXPERT > > > > So nobody noticed you have a structural "this config option actually switches > > this thing _off_" implemented via magic symbol then? Perhaps because the right thing happens if you enable CONFIG_EXPERT using "make menuconfig"? It also looks like the right thing happens if you edit the .config and then run "make oldconfig". Personally, I never use miniconfig, so it's not anything *I* ever noticed in all of my years of kernel development. Usually, the way that I manage configs is "make menuconfig", or editing the .config directly, or "make savedefconfig" / "make olddefconfig". Cheers, - Ted