Re:What to expect in NetBSD 7
by justincormack on Wednesday April 15, 2015 @04:02AM
(#9379484)
No it is not entirely accurate, but the Linux situation is very frustrating, with some functions not being supported in different architectures, random different header differences (ugh, mips) etc.
Agreed -- and people are proud (NetBSD) or defensive (Linux) of the characterization I made -- and while of course every single line isn't re-written, and presumably Linux kernal devs will talk to ea. other, or perhaps one person maintains multiple architectures and therefore gets automatic code/idea sharing, NetBSD goes through pains to make sure all the supported platforms' origin is the one, single repository that is NetBSD.
That's really not how it is. For example, here the one single implementation of the madvise() syscall in Linux:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.g...
This entire file is compiled on all architectures with MMUs (madvise() is pointless on architectures without MMUs and hence without virtual memory). Everything architecture-specific in this file is abstracted away by macros like PAGE_SIZE and PAGE_SHIFT.
That is not really an accurate way to characterise how the different Linux target architectures are supported in the source. As you would expect, the vast majority of the code is in fact shared.