netdev
[Top] [All Lists]

net link order

To: netdev@xxxxxxxxxxx
Subject: net link order
From: Keith Owens <kaos@xxxxxxxxxx>
Date: Mon, 25 Dec 2000 12:01:48 +1100
Sender: owner-netdev@xxxxxxxxxxx
I am documenting the requirements for link order across the net
directories and need some input.  net/Makefile (2.4.0-test13-pre4)
links directories in the order below, but there is no way of telling if
this order is required or is just historical.

Assuming that everything is linked into the kernel, which init routines
depend on other init code having already run?  Ignore link order within
net directories, this is documenting inter-directory link order
requirements.  For example,

ipv4 must be linked before ipv4/netfilter because ...
foo must be linked before bar because ...

subdir-$(CONFIG_NET)            += 802 sched            sched appears twice, 
why?
subdir-$(CONFIG_INET)           += ipv4
subdir-$(CONFIG_NETFILTER)      += ipv4/netfilter
subdir-$(CONFIG_UNIX)           += unix
subdir-$(CONFIG_IPV6)           += ipv6

ifneq ($(CONFIG_IPV6),n)
ifneq ($(CONFIG_IPV6),)
subdir-$(CONFIG_NETFILTER)      += ipv6/netfilter
endif
endif

subdir-$(CONFIG_KHTTPD)         += khttpd
subdir-$(CONFIG_NETLINK)        += netlink
subdir-$(CONFIG_PACKET)         += packet
subdir-$(CONFIG_NET_SCHED)      += sched                sched appears twice, 
why?
subdir-$(CONFIG_BRIDGE)         += bridge
subdir-$(CONFIG_IPX)            += ipx
subdir-$(CONFIG_ATALK)          += appletalk
subdir-$(CONFIG_WAN_ROUTER)     += wanrouter            no init
subdir-$(CONFIG_X25)            += x25
subdir-$(CONFIG_LAPB)           += lapb
subdir-$(CONFIG_NETROM)         += netrom
subdir-$(CONFIG_ROSE)           += rose
subdir-$(CONFIG_AX25)           += ax25
subdir-$(CONFIG_IRDA)           += irda
subdir-$(CONFIG_SUNRPC)         += sunrpc               no init
subdir-$(CONFIG_ATM)            += atm
subdir-$(CONFIG_DECNET)         += decnet
subdir-$(CONFIG_ECONET)         += econet


<Prev in Thread] Current Thread [Next in Thread>