> Excuse my ignorance on the matter, but a few queries.... > How does integration into kernelspace affect the way users have > control > over > the networking modules? > What I mean to say is, if there is a problem, is it still possible to > simply 'restart' > the net_server? And how about stability... is it wise to move things > into kernel > space when they're still untested... even when they are tested? > As much as we might like to think otherwise, there are plenty of > situations > when things break, and killing the kernel team is probably not a > NiceThing[tm] As far as I know you will be able to restart the module. BeOS can do dynamic kernel loading/unloading, so this isn't a problem, and you won't have to restart every five minutes ala' old-Windows. I think the issue you seem to be describing is when the stack receives a malformed packet that it can't handle, and then treads over kernel memory that it shouldn't have access too - that will/could be an issue, but as far as I know David has used a very stable and secure OpenBSD stack as the base for his work, and he knows what he is doing, so I will trust it! Thanks Andrew Edward McCall OpenBeOS Preferences & Applications Team Leader mccall@xxxxxxxxxxxxxxxxxxxxx -- OpenBeOS - Join The Revolution Now! http://www.openbeos.org/