FreeLists / openbeosnetteam / [openbeosnetteam] Re: Kernel move...

["Philippe Houdoin" <philippe.houdoin@xxxxxxx>]

Marcus wrote:
> >Not that I would really object against you, but it has an advantage: 
> >you can easily use networking functions from kernel drivers or file 
> >systems; you can use that API from everywhere.
> 
> This is a big pro for not using a socket driver approach.
> Which kernel drivers require to create sockets and send data?
> I don't know, perhaps a http server in the kernel, or a ftp 
filesystem.
> Might be a security problem to implement such things, but why not, 
allow it!

Writing a kernel module exporting the socket API to any kernel modules 
/ drivers who need it 
would be easy: the *hack*, to use David word, we do in libnet/socket.c 
can be done 
from a "network/socket_api" kernel module...

In fact, many low level services in BeOS / newOS are not provided by 
the kernel code itselft, but by kernel modules:
- sub-(kernel) modules, first
- PCI bus
- USB bus
- SCSI bus
- ISA bus
- PCMCIA cards service
- generic MIDI port support
- etc etc etc.

So, why not a socket api?
No need to modify the kernel code for that...

-Philippe

--
Fortune Cookie Says:

Give your child mental blocks for Christmas.