[openbeosnetteam] Re: Integration Q's
- From: "David Reid" <dreid@xxxxxxxxxxxx>
- To: <openbeosnetteam@xxxxxxxxxxxxx>
- Date: Sat, 16 Feb 2002 19:20:52 -0000
> > Ah, that bit I understand then... What about ioctl as other parts of
> > the
> > kernel support them don't they?
>
> Yes, but not R5 sockets.
> We'd need to have a device that maps all calls, e.g. /dev/socket -
> every time an application calls socket(), that fake device would create
> a new sockets, but it would have a real fd then.
> We'd need port communication between the device and the net_server,
> then.
OK. That makes sense I guess.
So basically we'll use getsockopt and setsockopt for sockets?
Someone care to write the /dev/socket device driver?
> > > When we are going towards OpenBeOS, we should really change this.
> > > This will either be fixed more or less automatically, by moving it
> > > into
> > > the kernel, or we'd have to change the kernel, so that it can
> > > provide
> > > user-level access to fds (with regard to creating, removing,
> > > handling).
> > Is changing the kernel really an option prior to using newos?
>
> Have I caused that impression?
No, it was a question :) So we're basically creating a stand-alone "app"
that is run as a daemon. I can relate to that.
david
Other related posts:
