3 ms·

Thanks for your explanation, now it's much clearer. It puzzles me why NeXT went through the extra effort of patching OSFMK instead of just doing like everybody

Thanks for your explanation, now it's much clearer. It puzzles me why NeXT went through the extra effort of patching OSFMK instead of just doing like everybody else was doing and just fork a monolithic BSD kernel - probably they were already too invested in Mach to pull back?

pram 5y ago
Yep, the NeXT Driver Kit relied upon Mach threads and messaging. Dumping it wasn't an option. Those all lived in user space, just like Apple DriverKit. It's the 90s all over again!