Hi,
This may sound like a really dumb question, but would
anyone have any objection if I cleaned up the menu
options for the networking?
The options don't seem to be grouped by function and
some of the 802.11 options are outside of the general
options list altogether, although I would argue they
are NOT higher level than options in lower-level menus
from that point.
There are also far too many options in the main
networking options menu, some indented and some on
other pages, with no obvious pattern or organization.
(eg: IPSec options seem to be sprinkled through like
seasoning. The classifier options at the end seem very
related to the advanced routing and the netfilter
code, yet are dependent on the classifier API in the
QoS menu which doesn't obviously relate to Quality of
Service. The TCP optimizations -do- seem to offer
"Quality of Service", but are in their own menu set.
And so on.)
The biggest problem I can see with my proposal is that
it's likely to get up the collective noses of every
single Linux network coder, particularly if I start
shuffling classifier-related code around. The second
drawback is that it would make for a lot of changes
that would have no actual code value whatsoever and
would mostly benefit those who both rolled their own
kernels AND had untreated OCD.
I'm not fond of being fed to giant rats, so I'd rather
know what the prevaling view was on the network code
layout.
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com