
|
[openbeosnetteam] Directions [was RE: IRC meeting]
- From: "Emmanuel Jacobs" <emmanuel.jacobs@xxxxxxxxxxxx>
- To: <openbeosnetteam@xxxxxxxxxxxxx>
- Date: Fri, 18 Jan 2002 15:00:49 +0100
For my part this is what I would like:
- developping network stack with NewOS
- developping replacement component for BeOS R5, firstly Network Kit. For
the BONE thing, I think we will have something new to redesign when first
version of OpenBeOS will come out, forking from NewOS.
I know this can be seen as a splitted effort, but ok, at the same time going
top to bottom and bottom to top for later merging the results seems to me a
good thing...
Manu
----- Original Message -----
From: "David Reid" <dreid@xxxxxxxxxxxx>
To: <openbeosnetteam@xxxxxxxxxxxxx>
Sent: Friday, January 18, 2002 2:43 PM
Subject: [openbeosnetteam] Re: IRC meeting.
>
> Also, it's worth noting that there is a plan to have a compatibility
libray
> so people can still use net_server calls...
>
> The fact of the matter is that unless we move forward we may as well not
> bother! This way we move forward but give a nod to the past, which is
> probably the best of both worlds.
>
> david
>
> >
> > From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
> >
> > > > I think there's space on the openbeos site for the netkit. I'm not
> > > > sure who maintains this. I'll cc michael phipps on this, maybe
he'll
> > let us
> > > > know. :)
> > >
> > > So we are going to reimplement BONE instead of the net=5Fserver=3F
> > > While I am okay with this, shouldn't discuss this in the OpenBeOS
> > > mailing list=3F
> >
> > Well, this is a moot point, as Travis will be implementing a kernel-land
> > stack for NewOS with or without our help. So I guess the kernel-land one
> is
> > the way o go.
> >
> > -Bruno
> >
> >
> >
> >
>
Other related posts:[openbeosnetteam] Directions [was RE: IRC meeting] [openbeosnetteam] Re: Directions [was RE: IRC meeting]
|

|

|
[ Home |
Signup |
Help |
Login |
Archives |
Lists
]
All trademarks and copyrights within the FreeLists archives are owned
by their respective owners. Everything else ©2008 Avenir Technologies, LLC.
|

|
|