Building the whole Networking Kit stuffs was made easy by Jam rules.
-When you have downloaded/updated your local code tree, simply run these commands from
-a Terminal:
| $ cd /path/to/your/local/openbeos/current -$ jam NetworkingKit - |
-
Although the stack isn't quite finished, you can already test some basics. + You'll have to get the code, build it, install it and run it. There isn't yet + an easier way of getting the network stack, we're far from ready to release + a binary package.
+So, if you accept your mission :
+++Have a look around and see the current status of the stack. Have a glance + over the jobs, perhaps there's something that interests you?
+
++You'll need CVS, JAM, the fixed LD linker
+
++SourceForge has some information + on CVS. If you don't want to fight with 'cvs' command line syntax, I recommand + you using CheckItOut tool.
+Enter these values:
+
+ Projet Name: open-beos
+ Location: /path/to/where/you/want/to/store/OBOS/cvs/tree/locally
+ Module Name: current
+ Only check "Open Tracker once Completed" option, if you + want.
+ There, click "Go". Patience, it take time (and bandwidth!)Other solution: download and unzip the current CVS snapshot + tarball from: Expect around 13MB.
+
++Then:
++ $ ./configure + $ jam NetworkingKit+It should build all networking kit stuffs. If you encount any compile or + link errors, report it to the network team mailing list.
+
++Installation script or jam rule is a task uncompleted. So, currently, you + have to install by hands. It sucks, I know.
+The network stuff binaries are now under your local current/distro/x86.R1/*
+To install:
+
++You should free one of your /dev/net/*/0 network card (by disable in BONEyard, + or by disabling in Network for net_server) Then, run the ifconfig tool from + Terminal to see (and start) the stack detected interface(s) Last, play with + ping, arp, traceroute, etc. Also check out the details on the stack + design.
+