From: Thomas Graf <tgraf@suug.ch>
To: "Randy.Dunlap" <randy.dunlap@verizon.net>
Cc: ioe-lkml@axxeo.de, matthew@wil.cx,
lkml <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com
Subject: Re: [RFC/PATCH] network configs: disconnect network options from drivers
Date: Thu, 31 Mar 2005 20:22:28 +0200 [thread overview]
Message-ID: <20050331182228.GV3086@postel.suug.ch> (raw)
In-Reply-To: <20050330234709.1868eee5.randy.dunlap@verizon.net>
* Randy.Dunlap <20050330234709.1868eee5.randy.dunlap@verizon.net> 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
<<Good title here>>
- Netfilter
- IPsec
- LVS
- Frame Diverter
- QoS & Fair Queueing
- Network testing
- WAN Router
Thoughts?
next prev parent reply other threads:[~2005-03-31 18:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 7:47 [RFC/PATCH] network configs: disconnect network options from drivers Randy.Dunlap
2005-03-31 11:04 ` jamal
2005-03-31 16:46 ` Chris Friesen
2005-03-31 18:30 ` David S. Miller
2005-03-31 18:22 ` Thomas Graf [this message]
2005-03-31 18:52 ` Sam Ravnborg
2005-03-31 20:02 ` Randy.Dunlap
2005-03-31 20:30 ` Sam Ravnborg
2005-04-04 3:30 ` [PATCH] " Randy.Dunlap
2005-04-04 19:50 ` Sam Ravnborg
2005-04-04 20:48 ` Randy.Dunlap
2005-04-04 21:55 ` Sam Ravnborg
2005-04-04 23:11 ` Randy.Dunlap
2005-04-05 15:45 ` Sam Ravnborg
2005-04-05 18:46 ` Randy.Dunlap
2005-04-05 21:11 ` [PATCH] networking: restructuring of net/ kconfig Sam Ravnborg
2005-04-05 17:42 ` [PATCH] network configs: disconnect network options from drivers Sridhar Samudrala
2005-04-05 21:04 ` Sam Ravnborg
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=20050331182228.GV3086@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=ioe-lkml@axxeo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=netdev@oss.sgi.com \
--cc=randy.dunlap@verizon.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).