3 ms·
> Tbf when I talk of using BSD tools, I'm talking about using MacOS tools - I don't have any BSD installations, I just recognize that MacOS includes mostly (?)
by toast0 4y ago
> Tbf when I talk of using BSD tools, I'm talking about using MacOS tools - I don't have any BSD installations, I just recognize that MacOS includes mostly (?) BSD tools by default.
It's not inaccurate, but somewhat unfair to use MacOS tools and call them BSD tools. They are ports of BSD tools, but Apple rarely refreshes them from the original sources, so it's kind of a time capsule to 2000. If you dropped 2000 era Linux userland on someone today, there would be a lot of complaints and concerns. On some tools, command flags added in GNU coreutils do get added to FreeBSD, although I did not check your list of specifics.
- cpeterso 4y agoIIRC, Apple periodically merges some kernel bits from FreeBSD and user space utilities from NetBSD. (Though I can’t find a source mentioning NetBSD, atm.) I don’t know why Apple would choose NetBSD utilities instead of FreeBSD if they are also using FreeBSD kernel bits. I understand why Apple doesn’t bother to contribute to upstream FreeBSD or NetBSD, but I’m curious why they aren’t eager to merge updates from them more frequently.
- toast0 4y ago> I’m curious why they aren’t eager to merge updates from them more frequently. I suspect it's because the merge isn't easy to do; which is partially a self-fulfilling property of how infrequent it's done, but likely also has a lot to do with the pretty large differences in system design. A lot of the kernel bits are old as heck too; last I checked, at least the Darwin open source kernel doesn't have any protection against syn floods, which FreeBSD first addressed in kernel 4.5 (released January 29, 2002)