Re: PROBLEM: Default initial config options all N

[Mikael Pettersson <mikpe@csd.uu.se>]

Ross Boylan writes:
 > Please cc me on replies.
 > 
 > [1.] One line summary of the problem:  
 > Defaults for oldconfig options not set correctly in recent 2.4 kernels

Define "correctly". Hint: it's user-dependent.

 > [2.] Full description of the problem/report:
 > Built 2.4.21 kernel, starting with config file from 2.4.20 and running
 > oldconfig.  *All* new config options had default values of N.  The
 > help text for the following options suggested "if unsure, pick Y":
 > PF_KEY
 > CONFIG_INET_AH
 > CONFIG_INET_ESP
 > CONFIG_INET_IPCOMP
 > CONFIG_IP_NF_TFTP
 > CONFIG_XFRM_USER

Not a bug.

 > Sample from the config dialog:
 > 
 > PF_KEY sockets (CONFIG_NET_KEY) [N/y/m/?] (NEW) ?
 > 
 > CONFIG_NET_KEY:
 > 
 >   PF_KEYv2 socket family, compatible to KAME ones.
 >   They are required if you are going to use IPsec tools ported
 >   from KAME.
 > 
 >   Say Y unless you know what you are doing.
 > PF_KEY sockets (CONFIG_NET_KEY) [N/y/m/?] (NEW) y

Still not a bug. oldconfig stopped and asked you what to do,
you checked the help text and chose Y.

Option authors tend to want people to enable them (enable this
cool feature!) but in real life, most are Ok to disable.

If oldconfig were to choose Y for new options, then _that_
would be a bug.