[openbeosnetteam] Re: Where do I start?

Wouldn't it be a good idea to upload this to the website?

Leon Timmermans

----- Original Message ----- 
From: "Philippe Houdoin" <philippe.houdoin@xxxxxxx>
To: <openbeosnetteam@xxxxxxxxxxxxx>
Sent: Saturday, June 14, 2003 5:37 PM
Subject: [openbeosnetteam] Re: Where do I start?


> Hi Brennan,
> 
> Sorry if I can't find time to reply your first email quicker.
> 
> > I am a new list member.  I want to help with finding and fixing bugs.
> > Where should I start?  What code do I need?  How do I test it?
> 
> Hum, alas, we don't have yet an enough working stack, but 
> it should not forbid you to test it.
> You'll have to get the code, build it, install it and run it, there is 
> no 
> package ready to install available yet...
> 
> So, if you accept your mission :
> 
> a) First, go to team web page:
> http://open-beos.sourceforge.net/tms/team.php?id=7
> 
> 
> b) Get the build tools suite:
> http://open-beos.sourceforge.net/dev.php
> Give a look at stack design, to get familiar with their components:
> http://philippe.houdoin.free.fr/phil/beos/openbeos/network_kit/
> 
> You'll need CVS, JAM, the fixed LD linker
> 
> c) Then, you should checkout (anonymously) the full OBOS CVS. If you 
> don't want to fight with 'cvs' command line syntax, I recommand you 
> using CheckItOut tool:
> http://www.bebits.com/app/3407
> 
> 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:
> http://cvs.sourceforge.net/cvstarballs/open-beos-cvsroot.tar.gz
> 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. 
> Report here any compile or link errors you may encounter
> 
> e) Installation
> 
> [I should add installation procedure soon to documentation, BTW!]
> 
> Installation script or jam rule is a task uncompleted. Unassigned, too.
> 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...
> 
> I know, that should be far easier than that, and in fact if you can 
> come with a install script and a documentation on how to test the 
> current stack, 
> it'll help greatly this team !!!
> 
> Feel free to post any question there...
> 
> -Philippe
> 
> 
> 
> --
> Fortune Cookie Says:
> 
> Anyone who cannot cope with mathematics is not fully human.  At best he
> is a tolerable subhuman who has learned to wear shoes, bathe and not
> make messes in the house.
> -- Lazarus Long, "Time Enough for Love"
> 
> 
> 
>

Other related posts: