Re: BSD net stack

Quoting Nathan Whitehorn:

> FreeBSD is definitely the way to go. Dragonfly BSD's threading model
> prohibits process migration, etc. We had decided, I believe, that we
> were interested in porting the FreeBSD stack, possibly using the
> netgraph system as the first poster noted.

Hum, I'm was agreeing on the classic monolithic stack in fact.
Plain and stupid port. Just for R1.
To get quickly both stability and compatibility.

Not that I'm against netgraph, but that not our current issue for R1.
And, as you noted:
> That said, most net team developers have no time, so if you're
> interested...
> -Nathan

That why I'm for the shortest port.

I've to read how to create a branch locally, as until the port is completed we
can't dump the current src/add-ons/kernel/network/* code. But the prot will
replace most of it.
Anyone used to "svn copy" usage?

Or maybe we should just do it under src/tests/kits/net/freebsdstack?

- Philippe


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click