FreeLists / openbeosnetteam / [openbeosnetteam] Re: Directory Structure...

["David Reid" <dreid@xxxxxxxxxxxx>]

Did Jean say you were looking at how net_server talks to the network cards?
That's really the first thing we need before we can go anywhere real...

I think once we have that piece of information this is what we should do...

o build a simple net_server that can talk to the cards, get input, send
output
o write the ethernet module
o write a very simple arp module that just prints it's findings
o write a very simple wrapper for ip that again just prints it's findings
o statically link all these together and hard code the links between them
o make sure it's all working

Viola! We now have our test bed for doing the module/linking/loading etc
stuff. At least this way we start from a know basis with actual code to work
with.  Spending too much time on how we link the modules etc together before
that is interesting, but not very practical.

BTW, I estimate the above will take about 2-3 hours :)

david

----- Original Message -----
From: "Emmanuel Jacobs" <emmanuel.jacobs@xxxxxxxxxxxx>
To: <openbeosnetteam@xxxxxxxxxxxxx>
Sent: Friday, February 08, 2002 2:34 PM
Subject: [openbeosnetteam] Re: Directory Structure...


>
> Fine for me :-)
>
>     Emmanuel
>
> ----- Original Message -----
> From: "David Reid" <dreid@xxxxxxxxxxxx>
> >
> > As we want to have all "parts" as modules are we happy with this...
> >
> > server/
> >             /net - basic net_server module
> >             /arp
> >             /ethernet
> >             /include
> >             /ipv4
> >             /ppp
> >             /tcp
> >             /udp
> >
> > Include files should stay with their module as closely as possible, with
> > anything that's global being in include.
> >
> > The main / directory is used to store all sorts of silly general things
at
> > present, so maybe we move all those to a seperate "util" directory?
> >
> > david
> >
>
>
>