[openbeosnetteam] Moving stuffs to a new place: where to put things?
- From: "Philippe Houdoin" <philippe.houdoin@xxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Sat, 24 Aug 2002 14:00:53 +0200 (added by postmaster@wanadoo.fr)
Hi all,
Here my suggestion for the new place of net_kit stuffs in the /current
tree.
Please give it a look, at least for planed directories names and
places, as
you all know how it's hard to get rid of bad named/placed directories
in a
CVS repository.
Some part of /net_kit was already moved to /current, BTW.
Another point ins this move is our current Makefiles are hugely
dependant on
relative source tree, so we need to write Jamfiles to replace them
anyway
with the move (why waste time to fix current Makefiles !?)
a) /net_kit/docs/
* -> /current/dpcs/develop/net/*
Already made since 6 weeks now.
b) /net_kit/source/apps/
arp/* -> /current/src/apps/arp/*
ifconfig/* -> /current/src/apps/ifconfig/*
ping/* -> /current/src/apps/ping/*
route/* -> /current/src/apps/route/*
traceroute/* -> /current/src/apps/traceroute/*
ppp/* -> /current/src/apps/pppconfig/*
I suggest we rename into "pppconfig" to escape possible
confusion with the "ppp" protocol module below...
* -> /current/src/tests/kits/net/*
With the exception of "ppp" directory, these moves was already made
since 6 weeks now.
c) /net_kit/source/driver/
net_stack_driver.c ->
/current/src/add-ons/kernel/drivers/net/stack/net_stack_driver.c
net_userstack_driver.c ->
/current/src/add-ons/kernel/drivers/net/stack/
net_userstack_driver.c
Makefile -> /current/src/add-ons/kernel/drivers/net/stack/Makefile
net_stack_driver.h -> /current/headers/private/net/net_stack_driver.h
d) /net_kit/source/libnet/
* -> /current/src/kits/net/*
Or do we need to have one sub-directory for libnet.so, one for
our future libnetapi.so implementation, etc ? I'm not sure
(please anyone correct me!) but can't we build all (even BNet*
classes) in one single libnet.so and "fake" libnetapi.so by a
symlink targetting libnet.so?
The image loader of both BeOS and OBOS traverse paths,
but what the ELF library resolver? Did it check the loaded
library name against the one in the ELF table?
I'll like having a single libnet.so, it's more BeOS old time-way
of doing (one kit, one library).
e) /net_kit/source/server/ (misnamed directory now)
userland_ipc.c -> /current/src/servers/net/userland_ipc.c
userland_server.c -> /current/src/servers/net/userland_server.c
net_server/* -> /current/src/add-ons/kernel/network/core/*
arp/* -> /current/src/add-ons/kernel/network/protocols/arp/*
icmp/* -> /current/src/add-ons/kernel/network/protocols/icmp/*
ipv4/* -> /current/src/add-ons/kernel/network/protocols/ipv4/*
raw/* -> /current/src/add-ons/kernel/network/protocols/raw/*
route/* -> /current/src/add-ons/kernel/network/protocols/route/*
tcp/* -> /current/src/add-ons/kernel/network/protocols/tcp/*
udp/* -> /current/src/add-ons/kernel/network/protocols/udp/*
ethernet/* -> /current/src/add-ons/kernel/network/interfaces/
ethernet/*
loop/* -> /current/src/add-ons/kernel/network/interfaces/loopback/*
For PPP modules, I'm not sure to have a good overview of what ppp sub
-module
do what so it's difficult. However, based on what I've understand so
far :
ppp/* -> /current/src/add-ons/kernel/network/protocols/ppp/*
ppp/serial_ppp/* -> /current/src/add-ons/kernel/network/interfaces/
serial_ppp/*
test/* -> /current/src/tests/kits/net/* ?
Obsoleted:
net_srv.c by userland_*.c I guess
bin/* by userland_*.c, too
serial_ppp/* by ppp/serial_ppp/*
/net_kit/source/server/include/* :
Include files was already moved (but some needs to be updated
however) in
/current/headers/private/net/ or /current/headers/posix/.
We may should in the future reconsider how to dispatch them between
"private", "os" and "posix" kind, but I guess we can say we don't
care yet about this.
I suggest this because I'm a little lost between posix'ish ones and
specifics (but private?)
ones.
So, what do you think?
-Philippe
--
Fortune Cookie Says:
If you sit down at a poker game and don't see a sucker, get up. You're
the sucker.
Other related posts:
