From patchwork Tue Sep 4 17:44:51 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: stephen hemminger X-Patchwork-Id: 181643 X-Patchwork-Delegate: davem@davemloft.net Return-Path: X-Original-To: patchwork-incoming@ozlabs.org Delivered-To: patchwork-incoming@ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 98AEB2C00A2 for ; Wed, 5 Sep 2012 03:45:50 +1000 (EST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932523Ab2IDRpV (ORCPT ); Tue, 4 Sep 2012 13:45:21 -0400 Received: from mail.vyatta.com ([76.74.103.46]:35694 "EHLO mail.vyatta.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932453Ab2IDRpU (ORCPT ); Tue, 4 Sep 2012 13:45:20 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.vyatta.com (Postfix) with ESMTP id 06B261480007; Tue, 4 Sep 2012 10:45:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at tahiti.vyatta.com Received: from mail.vyatta.com ([127.0.0.1]) by localhost (mail.vyatta.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YAMfYpkOUt5B; Tue, 4 Sep 2012 10:45:11 -0700 (PDT) Received: from nehalam.linuxnetplumber.net (static-50-53-80-93.bvtn.or.frontiernet.net [50.53.80.93]) by mail.vyatta.com (Postfix) with ESMTPSA id 8F7011480005; Tue, 4 Sep 2012 10:45:11 -0700 (PDT) Date: Tue, 4 Sep 2012 10:44:51 -0700 From: Stephen Hemminger To: Randy Dunlap Cc: Stephen Rothwell , linux-next@vger.kernel.org, LKML , netdev@vger.kernel.org Subject: [PATCH] net: don't allow INET to be not configured Message-ID: <20120904104451.29819808@nehalam.linuxnetplumber.net> In-Reply-To: <50463941.9070703@xenotime.net> References: <20120904171330.f6b0a922a754ba0f3acc123b@canb.auug.org.au> <50463941.9070703@xenotime.net> Organization: Vyatta X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org 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 --- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html --- 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 - . - - 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 - . - - Short answer: say Y. + def_bool y if INET source "net/ipv4/Kconfig"