All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org
Subject: [PATCH] net: don't allow INET to be not configured
Date: Tue, 4 Sep 2012 10:44:51 -0700	[thread overview]
Message-ID: <20120904104451.29819808@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <50463941.9070703@xenotime.net>

There is no reason to expose turning off TCP/IP networking.
If networking is enabled force TCP/IP to enabled. This also
eliminates the time chasing down errors with bogus configurations
generated by 'make randconfig'

For testing, it is still possible to edit Kconfig

Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>


--- a/net/Kconfig	2012-08-15 08:59:22.910704705 -0700
+++ b/net/Kconfig	2012-09-04 10:39:53.654585718 -0700
@@ -51,26 +51,7 @@ source "net/xfrm/Kconfig"
 source "net/iucv/Kconfig"
 
 config INET
-	bool "TCP/IP networking"
-	---help---
-	  These are the protocols used on the Internet and on most local
-	  Ethernets. It is highly recommended to say Y here (this will enlarge
-	  your kernel by about 400 KB), since some programs (e.g. the X window
-	  system) use TCP/IP even if your machine is not connected to any
-	  other computer. You will get the so-called loopback device which
-	  allows you to ping yourself (great fun, that!).
-
-	  For an excellent introduction to Linux networking, please read the
-	  Linux Networking HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  If you say Y here and also to "/proc file system support" and
-	  "Sysctl support" below, you can change various aspects of the
-	  behavior of the TCP/IP code by writing to the (virtual) files in
-	  /proc/sys/net/ipv4/*; the options are explained in the file
-	  <file:Documentation/networking/ip-sysctl.txt>.
-
-	  Short answer: say Y.
+	def_bool y
 
 if INET
 source "net/ipv4/Kconfig"

  reply	other threads:[~2012-09-04 17:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04  7:13 linux-next: Tree for Sept 4 Stephen Rothwell
2012-09-04 17:03 ` linux-next: Tree for Sept 4 (uml + execve) Randy Dunlap
2012-09-04 17:24 ` linux-next: Tree for Sept 4 (netdev) Randy Dunlap
2012-09-04 17:44   ` Stephen Hemminger [this message]
2012-09-04 18:07     ` [PATCH] net: don't allow INET to be not configured David Miller
2012-09-04 17:29 ` linux-next: Tree for Sept 4 (cma) Randy Dunlap
2012-09-04 17:29   ` Randy Dunlap
2012-09-04 23:48 ` linux-next: Tree for Sept 4 (drivers/net/phy/mdio-mux-mmioreg.c) Randy Dunlap
2012-09-07 19:37   ` Timur Tabi
2012-09-07 19:37     ` Timur Tabi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120904104451.29819808@nehalam.linuxnetplumber.net \
    --to=shemminger@vyatta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.