3 ms·
Like I said, the userland applications (ping, tracert, etc.) were ports from BSD, probably nearly 1:1 copies. The TCP & IP stacks were written by Microsoft in
by nullindividual 2y ago
Like I said, the userland applications (ping, tracert, etc.) were ports from BSD, probably nearly 1:1 copies.
The TCP & IP stacks were written by Microsoft in NT 3.5.
What Spider Software used (again, used by Microsoft in NT 3.1 due to time pressures) may have originated from BSD, but we don't know.
You can browse the NT4 source code TCP/IP stack. Just search GitHub.
- teleforce 2y ago>What Spider Software used (again, used by Microsoft in NT 3.1 due to time pressures) may have originated from BSD In all likelihood it's from BSD don't you think?
- nullindividual 2y agoThat's an assumption that neither of us are qualified to make. BSD wasn't the only TCP/IP stack on the market[0]. [0] https://en.wikipedia.org/wiki/Internet_protocol_suite#Adoption https://en.wikipedia.org/wiki/Internet_protocol_suite#Adopti...
- teleforce 2y agoIf Spider engineers didn't even bothered to change any of the BSD userspace utilities what is the chance that they built the entire TCP/IP stack perfectly compatible with the outside world inside the kernel from scratch?
- nullindividual 2y agoThe Spider engineers weren't the ones to port BSD utilities. That was Microsoft.
- teleforce 2y agoPerhaps you misunderstood my statement I am not talking about NT there, Spider Systems has had their network user spaces utilities and tools but almost all of them were BSD not developed by them. If their tools originally BSD then what were the chances they developed their very own TCP/IP stacks from scratch with good compatibility with the outside world? This remind me a particular incident happened to Brendan Gregg of the eBPF initiatives, when a company performed a demo of their alleged game changing kernel tracing tools to him and as it turned out the tools were actually Brendan very own developed tools.