linux-kernel - Re: Why is CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 30 Dec 2019 21:33:14 -0500
From:   "Theodore Y. Ts'o" <tytso@....edu>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     Rob Landley <rob@...dley.net>, linux-kernel@...r.kernel.org
Subject: Re: Why is CONFIG_VT forced on?

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