Re: [PATCH] network configs: disconnect network options from drivers

2005-04-05 Thread Sam Ravnborg 
On Tue, Apr 05, 2005 at 10:42:25AM -0700, Sridhar Samudrala wrote:
> On Mon, 4 Apr 2005, Sam Ravnborg wrote:
> 
> >
> >Only bit that I am worried about is the statement in SCTP:
> > depends on IPV6 || IPV6=n
> >
> >That looked like a noop to me. It had the sideeffect that SCTP
> >menu entries where idented an extra level which was not desireable
> >with currect layout.
> >
> 
> No. This is not a noop. This is required to restrict SCTP configured as
> static when IPV6 is configured as module.

I see now - thanks.

Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] network configs: disconnect network options from drivers

2005-04-05 Thread Randy.Dunlap 
Sam Ravnborg wrote:
On Mon, Apr 04, 2005 at 04:11:33PM -0700, Randy.Dunlap wrote:
- in Networking support, move Network testing and Netpoll
support to the end of the menu (basically put the devel.
tools toward the bottom of the menu)
Done

- I would rather not "hide" Amateur Radio, IrDA, and
Bluetooth in the Networking protocols area, but have them
near 802.1x and ATM in the top-level Networking support
menu.  How does that sound to you?
Done
I've made them with separate menu's that you have to enter to enable
them.
Also pushed out xfrm stuff to net/xfrm/Kconfig
Several other small adjustments.
In the Networking menu the submenu's are grouped in beginning and in the
end now.
I thought of creating a Kconfig.netfilter for the common netfilter
stuff. But in the end did not do it - felt there was plenty of new small
files being created already.
It would make sense to isolate the netfilter options, but that can
be done later.
But you are right about "plenty of new small files."
I would move Frame Diverter (NET_DIVERT) from the end of the
net/core/Kconfig file to the top of the same file
and then ship it.  :)

Comments welcome.
Thanks for doing this.
--
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] network configs: disconnect network options from drivers

2005-04-05 Thread Sridhar Samudrala 
On Mon, 4 Apr 2005, Sam Ravnborg wrote:
Only bit that I am worried about is the statement in SCTP:
depends on IPV6 || IPV6=n
That looked like a noop to me. It had the sideeffect that SCTP
menu entries where idented an extra level which was not desireable
with currect layout.
No. This is not a noop. This is required to restrict SCTP configured as
static when IPV6 is configured as module.
Thanks
Sridhar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] network configs: disconnect network options from drivers

2005-04-05 Thread Sam Ravnborg 
On Mon, Apr 04, 2005 at 04:11:33PM -0700, Randy.Dunlap wrote:
> 
> - in Networking support, move Network testing and Netpoll
> support to the end of the menu (basically put the devel.
> tools toward the bottom of the menu)
Done

> - I would rather not "hide" Amateur Radio, IrDA, and
> Bluetooth in the Networking protocols area, but have them
> near 802.1x and ATM in the top-level Networking support
> menu.  How does that sound to you?
Done

I've made them with separate menu's that you have to enter to enable
them.
Also pushed out xfrm stuff to net/xfrm/Kconfig
Several other small adjustments.
In the Networking menu the submenu's are grouped in beginning and in the
end now.

I thought of creating a Kconfig.netfilter for the common netfilter
stuff. But in the end did not do it - felt there was plenty of new small
files being created already.

Comments welcome.

Sam


 drivers/Kconfig  |4 
 drivers/net/Kconfig  |5 
 net/Kconfig  |  541 ++-
 net/ax25/Kconfig |5 
 net/bluetooth/Kconfig|6 
 net/bridge/netfilter/Kconfig |1 
 net/decnet/Kconfig   |   24 +
 net/ipv4/netfilter/Kconfig   |5 
 net/ipv6/Kconfig |   20 +
 net/ipx/Kconfig  |   33 ++
 net/irda/Kconfig |5 
 net/sched/Kconfig|   40 +++
 net/sctp/Kconfig |5 
 net/xfrm/Kconfig |   14 +
 v2.6/net/8021q/Kconfig   |   21 +
 v2.6/net/appletalk/Kconfig   |   33 ++
 v2.6/net/atm/Kconfig |   79 ++
 v2.6/net/bridge/Kconfig  |   32 ++
 v2.6/net/core/Kconfig|   67 +
 v2.6/net/econet/Kconfig  |   34 ++
 v2.6/net/lapb/Kconfig|   24 +
 v2.6/net/packet/Kconfig  |   26 ++
 v2.6/net/unix/Kconfig|   22 +
 v2.6/net/wanrouter/Kconfig   |   31 ++
 v2.6/net/x25/Kconfig |   35 ++
 25 files changed, 590 insertions(+), 522 deletions(-)

 
= drivers/Kconfig 1.7 vs edited =
--- 1.7/drivers/Kconfig 2004-12-28 07:01:46 +01:00
+++ edited/drivers/Kconfig  2005-04-04 23:49:50 +02:00
@@ -1,5 +1,7 @@
 # drivers/Kconfig
 
+source "net/Kconfig"
+
 menu "Device Drivers"
 
 source "drivers/base/Kconfig"
@@ -28,7 +30,7 @@
 
 source "drivers/macintosh/Kconfig"
 
-source "net/Kconfig"
+source "drivers/net/Kconfig"
 
 source "drivers/isdn/Kconfig"
 
= drivers/net/Kconfig 1.113 vs edited =
--- 1.113/drivers/net/Kconfig   2005-03-29 22:48:24 +02:00
+++ edited/drivers/net/Kconfig  2005-04-04 22:06:34 +02:00
@@ -1,8 +1,9 @@
-
 #
 # Network device configuration
 #
 
+menu "Network device support"
+
 config NETDEVICES
depends on NET
bool "Network device support"
@@ -2535,4 +2536,6 @@
---help---
If you want to log kernel messages over the network, enable this.
See  for details.
+
+endmenu
 
= net/Kconfig 1.43 vs edited =
--- 1.43/net/Kconfig2005-03-23 04:20:04 +01:00
+++ edited/net/Kconfig  2005-04-05 17:03:51 +02:00
@@ -2,7 +2,7 @@
 # Network configuration
 #
 
-menu "Networking support"
+menu "Networking"
 
 config NET
bool "Networking support"
@@ -10,7 +10,9 @@
  Unless you really know what you are doing, you should say Y here.
  The reason is that some programs need kernel networking support even
  when running on a stand-alone machine that isn't connected to any
- other computer. If you are upgrading from an older kernel, you
+ other computer.
+
+ If you are upgrading from an older kernel, you
  should consider updating your networking tools too because changes
  in the kernel and the tools often go hand in hand. The tools are
  contained in the package net-tools, the location and version number
@@ -20,57 +22,9 @@
  recommended to read the NET-HOWTO, available from
  .
 
-menu "Networking options"
-   depends on NET
-
-config PACKET
-   tristate "Packet socket"
-   ---help---
- The Packet protocol is used by applications which communicate
- directly with network devices without an intermediate network
- protocol implemented in the kernel, e.g. tcpdump.  If you want them
- to work, choose Y.
-
- To compile this driver as a module, choose M here: the module will
- be called af_packet.
-
- If unsure, say Y.
-
-config PACKET_MMAP
-   bool "Packet socket: mmapped IO"
-   depends on PACKET
-   help
- If you say Y here, the Packet protocol driver will use an IO
- mechanism that results in faster communication.
-
- If unsure, say N.
-
-config UNIX
-   tristate "Unix domain sockets"
-   ---help---
- If you say Y here, you will include support for Unix domain sockets;
- sockets are the standard Unix mechanism for establishing and
- accessing network connections.  Many commonly used programs suc

Re: [PATCH] network configs: disconnect network options from drivers

2005-04-04 Thread Randy.Dunlap 
Sam Ravnborg wrote:

- Move submenu to the top
- Rename top menu to "Networking" and located it just before
"File systems"
I still prefer Networking to come before Device Drivers FWIW.
Just makes some kind of hierarchical sense to me.
Moved up as suggested.

I propose that the new file net/atm/Kconfig be sourced somewhere.
Thanks, I have missed that one - added just before wanrouter.
 

I'll look at it more to see if I have any other comments.
OK. I will await and post an updated patch if you do not beat me.
Sam,
Here are a few more suggestions for you to consider.
- in Networking support, move Network testing and Netpoll
support to the end of the menu (basically put the devel.
tools toward the bottom of the menu)
- I would rather not "hide" Amateur Radio, IrDA, and
Bluetooth in the Networking protocols area, but have them
near 802.1x and ATM in the top-level Networking support
menu.  How does that sound to you?
Thanks.
--
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] network configs: disconnect network options from drivers

2005-04-04 Thread Sam Ravnborg 
 
> >- Move submenu to the top
> >- Rename top menu to "Networking" and located it just before
> > "File systems"
> 
> I still prefer Networking to come before Device Drivers FWIW.
> Just makes some kind of hierarchical sense to me.
Moved up as suggested.

> I propose that the new file net/atm/Kconfig be sourced somewhere.
Thanks, I have missed that one - added just before wanrouter.
 
> I'll look at it more to see if I have any other comments.
OK. I will await and post an updated patch if you do not beat me.

Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] network configs: disconnect network options from drivers

2005-04-04 Thread Randy.Dunlap 
Hi Sam-
Sam Ravnborg wrote:
On Sun, Apr 03, 2005 at 08:30:13PM -0700, Randy.Dunlap wrote:
Any comments on this new version?
The new Networking menu looks unstructured.
And the net/Kconfig file contains a lot of config snippets that does not
belong there.
So I took a stamp on it with focus on:
- Move config bits to appropriate places, creating several new Kconfig
  files
Very Good.
- Made uses of menus more consistent at least on first and second level
Very Good again.
- Move submenu to the top
- Rename top menu to "Networking" and located it just before
 "File systems"
I still prefer Networking to come before Device Drivers FWIW.
Just makes some kind of hierarchical sense to me.
The patch became much larger. The win is that the top-level
net/Kconfig contains much less cruft.
Many of the 56 lines added are due to the additional files.
I did not (on purpose) change any functionality.
Only bit that I am worried about is the statement in SCTP:
depends on IPV6 || IPV6=n
That looked like a noop to me. It had the sideeffect that SCTP
menu entries where idented an extra level which was not desireable
with currect layout.
Yeah, I was having several identation problems.
Comments appreciated.
Nice job overall.  Especially nice to move ATM, bridge, DECNET,
ECONET, etc., to their own Kconfig files so that they are more
manageable.
I propose that the new file net/atm/Kconfig be sourced somewhere.
I'll look at it more to see if I have any other comments.
Patch on top of rc2.
Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]>
---
	Sam
	
 drivers/Kconfig   |5 
 drivers/net/Kconfig   |5 
 drivers/net/appletalk/Kconfig |   28 ++
 net/8021q/Kconfig |   21 +
 net/Kconfig   |  541 +++---
 net/atm/Kconfig   |   77 +
 net/bridge/Kconfig|   32 ++
 net/bridge/netfilter/Kconfig  |1 
 net/core/Kconfig  |   67 +
 net/decnet/Kconfig|   24 +
 net/econet/Kconfig|   34 ++
 net/ipv4/netfilter/Kconfig|5 
 net/ipv6/Kconfig  |   20 +
 net/ipx/Kconfig   |   33 ++
 net/lapb/Kconfig  |   24 +
 net/packet/Kconfig|   26 ++
 net/sched/Kconfig |   40 +++
 net/sctp/Kconfig  |5 
 net/unix/Kconfig  |   22 +
 net/wanrouter/Kconfig |   31 ++
 net/x25/Kconfig   |   35 ++
 21 files changed, 567 insertions(+), 509 deletions(-)
Thanks!
--
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] network configs: disconnect network options from drivers

2005-04-04 Thread Sam Ravnborg 
On Sun, Apr 03, 2005 at 08:30:13PM -0700, Randy.Dunlap wrote:
> Any comments on this new version?
The new Networking menu looks unstructured.
And the net/Kconfig file contains a lot of config snippets that does not
belong there.
So I took a stamp on it with focus on:
- Move config bits to appropriate places, creating several new Kconfig
  files
- Made uses of menus more consistent at least on first and second level
- Move submenu to the top
- Rename top menu to "Networking" and located it just before
 "File systems"


The patch became much larger. The win is that the top-level
net/Kconfig contains much less cruft.

Many of the 56 lines added are due to the additional files.
I did not (on purpose) change any functionality.

Only bit that I am worried about is the statement in SCTP:
depends on IPV6 || IPV6=n

That looked like a noop to me. It had the sideeffect that SCTP
menu entries where idented an extra level which was not desireable
with currect layout.

Comments appreciated.

Patch on top of rc2.

Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]>
---


Sam

 drivers/Kconfig   |5 
 drivers/net/Kconfig   |5 
 drivers/net/appletalk/Kconfig |   28 ++
 net/8021q/Kconfig |   21 +
 net/Kconfig   |  541 +++---
 net/atm/Kconfig   |   77 +
 net/bridge/Kconfig|   32 ++
 net/bridge/netfilter/Kconfig  |1 
 net/core/Kconfig  |   67 +
 net/decnet/Kconfig|   24 +
 net/econet/Kconfig|   34 ++
 net/ipv4/netfilter/Kconfig|5 
 net/ipv6/Kconfig  |   20 +
 net/ipx/Kconfig   |   33 ++
 net/lapb/Kconfig  |   24 +
 net/packet/Kconfig|   26 ++
 net/sched/Kconfig |   40 +++
 net/sctp/Kconfig  |5 
 net/unix/Kconfig  |   22 +
 net/wanrouter/Kconfig |   31 ++
 net/x25/Kconfig   |   35 ++
 21 files changed, 567 insertions(+), 509 deletions(-)

 
diff -Nru a/drivers/Kconfig b/drivers/Kconfig
--- a/drivers/Kconfig   2005-04-04 21:41:57 +02:00
+++ b/drivers/Kconfig   2005-04-04 21:41:57 +02:00
@@ -28,7 +28,7 @@
 
 source "drivers/macintosh/Kconfig"
 
-source "net/Kconfig"
+source "drivers/net/Kconfig"
 
 source "drivers/isdn/Kconfig"
 
@@ -59,3 +59,6 @@
 source "drivers/infiniband/Kconfig"
 
 endmenu
+
+source "net/Kconfig"
+
diff -Nru a/drivers/net/Kconfig b/drivers/net/Kconfig
--- a/drivers/net/Kconfig   2005-04-04 21:41:57 +02:00
+++ b/drivers/net/Kconfig   2005-04-04 21:41:57 +02:00
@@ -1,8 +1,9 @@
-
 #
 # Network device configuration
 #
 
+menu "Network device support"
+
 config NETDEVICES
depends on NET
bool "Network device support"
@@ -2535,4 +2536,6 @@
---help---
If you want to log kernel messages over the network, enable this.
See  for details.
+
+endmenu
 
diff -Nru a/drivers/net/appletalk/Kconfig b/drivers/net/appletalk/Kconfig
--- a/drivers/net/appletalk/Kconfig 2005-04-04 21:41:57 +02:00
+++ b/drivers/net/appletalk/Kconfig 2005-04-04 21:41:57 +02:00
@@ -1,6 +1,34 @@
 #
 # Appletalk driver configuration
 #
+config ATALK
+   tristate "Appletalk protocol support"
+   depends on NET
+   select LLC
+   ---help---
+ AppleTalk is the protocol that Apple computers can use to communicate
+ on a network.  If your Linux box is connected to such a network and 
you
+ wish to connect to it, say Y.  You will need to use the netatalk 
package
+ so that your Linux box can act as a print and file server for Macs as
+ well as access AppleTalk printers.  Check out
+  on the WWW for details.
+ EtherTalk is the name used for AppleTalk over Ethernet and the
+ cheaper and slower LocalTalk is AppleTalk over a proprietary Apple
+ network using serial links.  EtherTalk and LocalTalk are fully
+ supported by Linux.
+
+ General information about how to connect Linux, Windows machines and
+ Macs is on the WWW at .  The
+ NET-3-HOWTO, available from
+ , contains valuable
+ information as well.
+
+ To compile this driver as a module, choose M here: the module will be
+ called appletalk. You almost certainly want to compile it as a
+ module so you can restart your AppleTalk stack without rebooting
+ your machine. I hear that the GNU boycott of Apple is over, so
+ even politically correct people are allowed to say Y here.
+
 config DEV_APPLETALK
bool "Appletalk interfaces support"
depends on ATALK
diff -Nru a/net/8021q/Kconfig b/net/8021q/Kconfig
--- /dev/null   Wed Dec 31 16:00:00 196900
+++ b/net/8021q/Kconfig 2005-04-04 21:41:57 +02:00
@@ -0,0 +1,21 @@
+#
+# Configuration for 802.1Q VLAN support
+#
+
+co

[PATCH] network configs: disconnect network options from drivers

2005-04-03 Thread Randy.Dunlap 
Sam Ravnborg wrote:
On Thu, Mar 31, 2005 at 12:02:13PM -0800, Randy.Dunlap wrote:
Other than "sounds good," are there some comments on:
a.  leaving IrDA and Bluetooth subsystem (with drivers) where they
   are, which is under "Network options and protocols"
(I really don't want to split their drivers away from their
subsystem, just to put them under Network driver support.)

Agreed. All IrDA / Bluetooth stuff belongs together.
Leave them where they are for now.

b.  leaving SLIP, PPP, and PLIP where they are under Network driver
   support, even though they say that they are "protocols" ?
SLIP and PLIP is no that common. PPP is more common for cable-modem/ADSL
I suppose. But still it would make sense to create an Misc protocols
menu, like we have a misc filesystems menu.
While looking into this suggestion, I see that SLIP, PLIP,
and PPP depend on NETDEVICES, and they use some netdev
interfaces, so they appear to be more like net devices
than protocols even though they are called
protocols in Kconfig text, so I am leaving them alone
for now.  Don't hesitate to correct me
Any comments on this new version?
Thanks,
--
~Randy

A few people dislike that the Networking Options menu is inside
the Device Drivers/Networking menu.  This patch moves the
Networking Options menu to immediately before the Device Drivers
menu, renames it to "Networking options and protocols", & moves
most protocols to more logical places.

Notes:
- IrDA & Bluetooth subsystems include protocols & drivers, yet
  they are displayed under Networking protocols.  I don't see
  much good reason to split them up.  (See, this is an example
  of why the Networking Options and Network Drivers were close
  together)
- SLIP, PLIP, and PPP option names say that they are protocols,
  but they are sort of a hybrid device and protocol, and they
  use network device interfaces, so they remain listed under
  Network devices.

 drivers/Kconfig  |4
 drivers/net/Kconfig  |5
 net/Kconfig  |  450 ++-
 net/bridge/netfilter/Kconfig |1
 4 files changed, 241 insertions(+), 219 deletions(-)

Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>

diff -Naurp -X /home/rddunlap/doc/dontdiff-osdl linux-2612-rc1-bk5-pv/drivers/Kconfig linux-2612-rc1-bk5-netconfigs/drivers/Kconfig
--- linux-2612-rc1-bk5-pv/drivers/Kconfig	2005-03-01 23:38:26.0 -0800
+++ linux-2612-rc1-bk5-netconfigs/drivers/Kconfig	2005-04-03 19:45:18.330102257 -0700
@@ -1,5 +1,7 @@
 # drivers/Kconfig
 
+source "net/Kconfig"
+
 menu "Device Drivers"
 
 source "drivers/base/Kconfig"
@@ -28,7 +30,7 @@ source "drivers/message/i2o/Kconfig"
 
 source "drivers/macintosh/Kconfig"
 
-source "net/Kconfig"
+source "drivers/net/Kconfig"
 
 source "drivers/isdn/Kconfig"
 
diff -Naurp -X /home/rddunlap/doc/dontdiff-osdl linux-2612-rc1-bk5-pv/drivers/net/Kconfig linux-2612-rc1-bk5-netconfigs/drivers/net/Kconfig
--- linux-2612-rc1-bk5-pv/drivers/net/Kconfig	2005-04-03 19:42:32.0 -0700
+++ linux-2612-rc1-bk5-netconfigs/drivers/net/Kconfig	2005-04-03 19:45:18.335101815 -0700
@@ -1,8 +1,9 @@
-
 #
 # Network device configuration
 #
 
+menu "Network device support"
+
 config NETDEVICES
 	depends on NET
 	bool "Network device support"
@@ -2536,3 +2537,5 @@ config NETCONSOLE
 	If you want to log kernel messages over the network, enable this.
 	See  for details.
 
+endmenu
+
diff -Naurp -X /home/rddunlap/doc/dontdiff-osdl linux-2612-rc1-bk5-pv/net/bridge/netfilter/Kconfig linux-2612-rc1-bk5-netconfigs/net/bridge/netfilter/Kconfig
--- linux-2612-rc1-bk5-pv/net/bridge/netfilter/Kconfig	2005-03-01 23:37:50.0 -0800
+++ linux-2612-rc1-bk5-netconfigs/net/bridge/netfilter/Kconfig	2005-04-03 19:45:18.0 -0700
@@ -139,6 +139,7 @@ config BRIDGE_EBT_VLAN
 config BRIDGE_EBT_ARPREPLY
 	tristate "ebt: arp reply target support"
 	depends on BRIDGE_NF_EBTABLES
+	depends on INET
 	help
 	  This option adds the arp reply target, which allows
 	  automatically sending arp replies to arp requests.
diff -Naurp -X /home/rddunlap/doc/dontdiff-osdl linux-2612-rc1-bk5-pv/net/Kconfig linux-2612-rc1-bk5-netconfigs/net/Kconfig
--- linux-2612-rc1-bk5-pv/net/Kconfig	2005-04-03 19:42:35.0 -0700
+++ linux-2612-rc1-bk5-netconfigs/net/Kconfig	2005-04-03 19:45:18.0 -0700
@@ -2,7 +2,7 @@
 # Network configuration
 #
 
-menu "Networking support"
+menu "Networking options and protocols"
 
 config NET
 	bool "Networking support"
@@ -10,7 +10,9 @@ config NET
 	  Unless you really know what you are doing, you should say Y here.
 	  The reason is that some programs need kernel networking support even
 	  when running on a stand-alone machine that isn't connected to any
-	  other computer. If you are upgrading from an older kernel, you
+	  other computer.
+
+	  If you are upgrading from an older kernel, you
 	  should consider updating your networking tools too because changes
 	  in the kernel and the tools often go hand

Re: [RFC/PATCH] network configs: disconnect network options from drivers

2005-03-31 Thread Sam Ravnborg 
On Thu, Mar 31, 2005 at 12:02:13PM -0800, Randy.Dunlap wrote:
> 
> Other than "sounds good," are there some comments on:
> 
> a.  leaving IrDA and Bluetooth subsystem (with drivers) where they
> are, which is under "Network options and protocols"
>   (I really don't want to split their drivers away from their
>   subsystem, just to put them under Network driver support.)

Agreed. All IrDA / Bluetooth stuff belongs together.
Leave them where they are for now.

> 
> b.  leaving SLIP, PPP, and PLIP where they are under Network driver
> support, even though they say that they are "protocols" ?
SLIP and PLIP is no that common. PPP is more common for cable-modem/ADSL
I suppose. But still it would make sense to create an Misc protocols
menu, like we have a misc filesystems menu.

Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [RFC/PATCH] network configs: disconnect network options from drivers

2005-03-31 Thread Randy.Dunlap 
Sam Ravnborg wrote:
On Wed, Mar 30, 2005 at 11:47:09PM -0800, Randy.Dunlap wrote:
- some Networking options need to be qualified with CONFIG_NET
You can something along the lines os:
menu "Networking options and protocols"
  
config NET
	bool "Networking support"
	default y

if NET
...
menu "Network device support"
...
endmenu
...
endif
endmenu
Then everything wrapped in between if NET/endif is dependent on NET
without stating this explicitly.
You will alos have the menu nice indented.
Yes, sounds good, thanks.
And I'll look into Thomas's suggestions.
Other than "sounds good," are there some comments on:
a.  leaving IrDA and Bluetooth subsystem (with drivers) where they
are, which is under "Network options and protocols"
(I really don't want to split their drivers away from their
subsystem, just to put them under Network driver support.)
b.  leaving SLIP, PPP, and PLIP where they are under Network driver
support, even though they say that they are "protocols" ?
Any others?
Thanks,
--
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [RFC/PATCH] network configs: disconnect network options from drivers

2005-03-31 Thread Sam Ravnborg 
On Wed, Mar 30, 2005 at 11:47:09PM -0800, Randy.Dunlap wrote:
> 
> - some Networking options need to be qualified with CONFIG_NET
You can something along the lines os:

menu "Networking options and protocols"
  
config NET
bool "Networking support"
default y

if NET

...

menu "Network device support"
...
endmenu

...

endif
endmenu

Then everything wrapped in between if NET/endif is dependent on NET
without stating this explicitly.
You will alos have the menu nice indented.

Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [RFC/PATCH] network configs: disconnect network options from drivers

2005-03-31 Thread David S. Miller 
On Thu, 31 Mar 2005 10:46:45 -0600
Chris Friesen <[EMAIL PROTECTED]> wrote:

> > Any comments?
> 
> Makes sense to me...

Me too.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [RFC/PATCH] network configs: disconnect network options from drivers

2005-03-31 Thread Thomas Graf 
* Randy.Dunlap <[EMAIL PROTECTED]> 2005-03-30 23:47
> 
> RFC:  This is a work-in-progress (WIP), not yet completed.
> 
> A few people dislike that the Networking Options menu is inside
> the Device Drivers/Networking menu.  This patch moves the
> Networking Options menu to immediately before the Device Drivers menu,
> renames it to "Networking options and protocols", & moves most
> protocols to more logical places (IMHOOC).

Definitely a good idea.

> The reasons that it is still WIP are:
> - I'd like to see all of the sub-menus done in the same style;

Further suggestions:

 - Introduce sub menus on separate pages for TCP/IP, DECNet,
   ATM, ... i.e. like it is done for SCTP.

 - Separate things into top categories
 Socket Families (maybe separate page)
   - PF_PACKET
   - PF_UNIX
   - PF_KEY
 Protocols (separate page)
   - TCP/IP networking (separate page)
  - IPv6 (affecting choices below)
 - Privary extensions
  - multicasting
  - routing
 - advanced router
- policy routing
   - use nfmark with chaching support
- multipath routing
   - cached
  - rrd
  - random
  - ...
 - multicast routing
- pim v1
- pim v2
 - verbose route monitoring
  - auto configuration
 - dhcp
 - boop
 - rarp
  - tunneling
 - IPv4
- IPIP
- GRE
   - broadcast
 - IPv6
- IPv6oIPv6
  - transformations
 - IPv4
- AH
- ESP
- IPComp
 - IPv6
- AH
- ESP
- IPComp
  - ARP daemon
  - TCP
 - Diagnostics
 - Syn Cookies
   - SCTP
   - ATM
   - 802.1d
   - 802.1q
   - DECnet
   - 802.2 LLC
   - IPX
   - Appletalk
   - X.25
   - LAPB
   - Econet
 <>
   - Netfilter
   - IPsec
   - LVS
   - Frame Diverter
   - QoS & Fair Queueing
   - Network testing
   - WAN Router

Thoughts?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [RFC/PATCH] network configs: disconnect network options from drivers

2005-03-31 Thread Chris Friesen 
Randy.Dunlap wrote:
A few people dislike that the Networking Options menu is inside
the Device Drivers/Networking menu.  This patch moves the
Networking Options menu to immediately before the Device Drivers menu,
renames it to "Networking options and protocols", & moves most
protocols to more logical places (IMHOOC).

Any comments?
Makes sense to me...
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [RFC/PATCH] network configs: disconnect network options from drivers

2005-03-31 Thread jamal 
On Thu, 2005-03-31 at 02:47, Randy.Dunlap wrote:
> RFC:  This is a work-in-progress (WIP), not yet completed.
> 
> A few people dislike that the Networking Options menu is inside
> the Device Drivers/Networking menu.  This patch moves the
> Networking Options menu to immediately before the Device Drivers menu,
> renames it to "Networking options and protocols", & moves most
> protocols to more logical places (IMHOOC).
> 

About time someone brave did this.

cheers,
jamal


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[RFC/PATCH] network configs: disconnect network options from drivers

2005-03-31 Thread Randy.Dunlap 

RFC:  This is a work-in-progress (WIP), not yet completed.

A few people dislike that the Networking Options menu is inside
the Device Drivers/Networking menu.  This patch moves the
Networking Options menu to immediately before the Device Drivers menu,
renames it to "Networking options and protocols", & moves most
protocols to more logical places (IMHOOC).

The reasons that it is still WIP are:
- I'd like to see all of the sub-menus done in the same style;
- IrDA & Bluetooth subsystems include protocols & drivers, yet
  they are displayed under Networking protocols.  I don't see
  much good reason to split them up.  (See, this is an example
  of why the Networking Options and Network Drivers were close
  together)
- some Networking options need to be qualified with CONFIG_NET

Any comments?


Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>

 drivers/Kconfig |4
 drivers/net/Kconfig |5
 net/Kconfig |  396 ++--
 3 files changed, 208 insertions(+), 197 deletions(-)


diff -Naurp -X /home/rddunlap/doc/dontdiff-osdl 
linux-2612-rc1-pv/drivers/Kconfig linux-2612-rc1-netconfig/drivers/Kconfig
--- linux-2612-rc1-pv/drivers/Kconfig   2005-03-01 23:38:26.0 -0800
+++ linux-2612-rc1-netconfig/drivers/Kconfig2005-03-30 22:19:48.231418331 
-0800
@@ -1,5 +1,7 @@
 # drivers/Kconfig
 
+source "net/Kconfig"
+
 menu "Device Drivers"
 
 source "drivers/base/Kconfig"
@@ -28,7 +30,7 @@ source "drivers/message/i2o/Kconfig"
 
 source "drivers/macintosh/Kconfig"
 
-source "net/Kconfig"
+source "drivers/net/Kconfig"
 
 source "drivers/isdn/Kconfig"
 
diff -Naurp -X /home/rddunlap/doc/dontdiff-osdl 
linux-2612-rc1-pv/drivers/net/Kconfig 
linux-2612-rc1-netconfig/drivers/net/Kconfig
--- linux-2612-rc1-pv/drivers/net/Kconfig   2005-03-30 22:03:48.861547540 
-0800
+++ linux-2612-rc1-netconfig/drivers/net/Kconfig2005-03-30 
22:59:00.441523697 -0800
@@ -1,8 +1,9 @@
-
 #
 # Network device configuration
 #
 
+menu "Network device support"
+
 config NETDEVICES
depends on NET
bool "Network device support"
@@ -2556,3 +2557,5 @@ config NETCONSOLE
If you want to log kernel messages over the network, enable this.
See  for details.
 
+endmenu
+
diff -Naurp -X /home/rddunlap/doc/dontdiff-osdl linux-2612-rc1-pv/net/Kconfig 
linux-2612-rc1-netconfig/net/Kconfig
--- linux-2612-rc1-pv/net/Kconfig   2005-03-30 22:03:57.503790207 -0800
+++ linux-2612-rc1-netconfig/net/Kconfig2005-03-30 23:09:11.686664598 
-0800
@@ -2,15 +2,18 @@
 # Network configuration
 #
 
-menu "Networking support"
+menu "Networking options and protocols"
 
 config NET
bool "Networking support"
+   default y
---help---
  Unless you really know what you are doing, you should say Y here.
  The reason is that some programs need kernel networking support even
  when running on a stand-alone machine that isn't connected to any
- other computer. If you are upgrading from an older kernel, you
+ other computer.
+
+ If you are upgrading from an older kernel, you
  should consider updating your networking tools too because changes
  in the kernel and the tools often go hand in hand. The tools are
  contained in the package net-tools, the location and version number
@@ -20,9 +23,6 @@ config NET
  recommended to read the NET-HOWTO, available from
  .
 
-menu "Networking options"
-   depends on NET
-
 config PACKET
tristate "Packet socket"
---help---
@@ -81,6 +81,25 @@ config NET_KEY
 
  Say Y unless you know what you are doing.
 
+config NETPOLL
+   def_bool NETCONSOLE
+
+config NETPOLL_RX
+   bool "Netpoll support for trapping incoming packets"
+   default n
+   depends on NETPOLL
+
+config NETPOLL_TRAP
+   bool "Netpoll traffic trapping"
+   default n
+   depends on NETPOLL
+
+config NET_POLL_CONTROLLER
+   def_bool NETPOLL
+
+menu "Networking protocols"
+   depends on NET
+
 config INET
bool "TCP/IP networking"
---help---
@@ -127,100 +146,6 @@ config IPV6
 
 source "net/ipv6/Kconfig"
 
-menuconfig NETFILTER
-   bool "Network packet filtering (replaces ipchains)"
-   ---help---
- Netfilter is a framework for filtering and mangling network packets
- that pass through your Linux box.
-
- The most common use of packet filtering is to run your Linux box as
- a firewall protecting a local network from the Internet. The type of
- firewall provided by this kernel support is called a "packet
- filter", which means that it can reject individual network packets
- based on type, source, destination etc. The other kind of firewall,
- a "proxy-based" one, is more secure but more intrusive and more
- bothersome to set up; it inspects the network traffic much more
-