OpenBeOS Network Kit: Build & installation instructions

["Niels Reedijk" <n.reedijk@xxxxxxxxx>]

Hi all,

Included is the email you sent with build instructions, but now with a
nice mark-up. Philippe, should I commit this one to CVS (yes, I have
write access!). Still working on an installation script.

Niels Sascha Reedijk

Title: OpenBeOS Network Kit

OpenBeOS Network Kit: Build & installation instructions

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 :

a) First, go to team web page.

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?

b) Get the build tools suite.

You'll need CVS, JAM, the fixed LD linker

c) Then, you should checkout (anonymously) the full OBOS CVS.

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.

d) Open a Terminal, cd to your all new local CVS current directory.

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.

e) Installation

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:

• open your current/distro/x86.R1/beos/system/add-ons/kernel/drivers/bin
  
• copy the net_stack_driver and net_server_driver into your /boot/home/config/add-ons/kernel/drivers/bin
  
• create in your /boot/home/config/add-ons/kernel/drivers/dev/net two symlinks "net_stack_driver" and "net_server_driver", targetting the ones in ../../bin/net_{stack|server}_driver (create this 'dev/net' directory if needed)
  
• copy the whole current/distro/x86.R1/beos/system/add-ons/kernel/
  network folder to your /boot/home/config/add-ons/kernel
  
• copy the libnet.so and libnetapi.so libraries from current/distro/ x86.R1/beos/system/lib into your /boot/home/config/lib
  
• copy the command line net apps from current/distro/x86.R1/beos/bin
  into your /boot/home/config/bin (or another folder of your choice)

f) Test the stack

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.

This document is written by Philippe Houdoin and edited by Niels Reedijk. Last updated on June 15th, 2003