FreeLists / openbeosnetteam / [openbeosnetteam] Re: PPP, libnet, and why inside the kernel?

["David Reid" <dreid@xxxxxxxxxxxx>]

Yeah, small point. :)

libroot is supposed to be the equivalent of libc on unix boxes isn't it?
That's where it should live IMHO.

Anyway, not that it matters... I (personally) think libnet should only
handle stuff like the resolving and address manipulation.

However, no doubt this will play itself out a few more times...

Oh, and to be truly accurate...

socket
open
kernel_open
device open
ioctl
kernel_ioctl
stack_ioctl


david

----- Original Message -----
From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
To: <openbeosnetteam@xxxxxxxxxxxxx>
Sent: Sunday, May 05, 2002 2:38 AM
Subject: [openbeosnetteam] Re: PPP, libnet, and why inside the kernel?


> > > What besides select()? I hope things like socket() stay in libnet;
> > > that
> > > is an appropriate place for them. I still don't see what advantage
> > > there is to being copmiled into the kernel.
> >
> > Oh come on get a grip. libnet is a userland lib. Things like socket
> > belong
> > in kernel. Why? What does socket do? It opens a window into the
> > kernel and
> > the i/o routines that live there. Instead of calling
> >
> > socket
> > open
> > ioctl
> >
> > in kernel we simply call
> >
> > socket
>
> It don't have to be in libroot.so for that; you can call kernel
> functions from everywhere it doesn't have to be libroot.
> And it's always
> socket
> kernel_socket
>
> Adios...
>    Axel.
>
>
>
>