[...] > libnet.so includes the C/posix/socket stuff, while libnetapi.so > includes > the C++ classes. I would like to keep it this way, and suggest: > > /net_kit/source/libnet/* -> /current/src/kits/net/net/* > future libnetapi.so -> /current/src/kits/net/netapi/* > > OR: > > /net_kit/source/libnet/* -> /current/src/kits/net/libnet/* > future libnetapi.so -> /current/src/kits/net/libnetapi/* I favor this one. BTW, I would propose to introduce a directory for the `etc' files. I have no idea where would be the best place for it though. > > 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 > Ok > > > > > net_server/* -> /current/src/add-ons/kernel/network/core/* > Currently, BeOS does not have /add-ons/kernel/network, > but I guess this is the right location, since the network core > is a module, so it doesn't belong into drivers. There is already /current/src/add-ons/kernel/net, so unless it has a completely different meaning, this one could be used. BTW, it does contain some stuff... [...] > BTW, the layout of the CVS tree should match the long time goal of a > kernel > stack. The compiled userland stack files can be placed in their > correct > locations easily by modifying the jamfiles Yep. As soon as the sources are moved and I get a `Go!', I'll hack the Jamfiles. CU, Ingo