[Oliver_H]

Originally Posted by drhowarddrfine

Take FreeBSD away from Apple and what did they have?

Some lousy parts of the original Mach kernel and a some bits of Gnu and NetBSD

Addendum:

http://lists.freebsd.org/pipermail/f...st/003674.html

I'd be a bit cautious about saying XNU is a Mach kernel. XNU is not a
microkernel, but it contains a lot more Mach code than FreeBSD does.
However, XNU contains massive amounts of FreeBSD code, including countless IPC
models, security parts, VFS, network stack, distributed file systems, etc.
Saying that "Mac OS X is just FreeBSD with an Apple GUI" is certainly false on
face value, but it's not correct to say that the kernel isn't in significant
part FreeBSD-derived. Here's what I find in my most recent XNU kernel source
drop from Apple:

21M of code labeled explicitly as BSD, largely from FreeBSD but heavily
modified.

16M of code labeled explicitly as Mach, largely from OSF Mach, but heavily
modified.

676K of code labeled explicitly as Security, actually the TrustedBSD MAC
Framework from FreeBSD, with modifications.

2.7M of device driver code in the IOKit tree, mostly from Apple.

2M of "libkern" -- mostly Apple code (C++ parts for IOKit) and zlib.

And then some loose ends, such as libsyscall, which is really userspace code
but stored in the kernel source tree, configuration files, GDB macros, etc.

The above is just the XNU drop, so excludes the large number of additional
loadable kernel extensions (kexts), which include a lot of device drivers
(largely Apple and vendor code), but also things like smbfs (pretty much
verbatim FreeBSD code).

> If you want to brag about FreeBSD technology used in a mainstream product,
> then by all means mention Firefox 3, because that is already quite
> impressive.

This is true, but if you measure the proportion of Firefox code that is
FreeBSD vs the proportion of XNU code that is FreeBSD, we definitely have more
of a showing in XNU, making up a significant part of the product :-). One
shouldn't underestimate Apple's work to improve our code and produce new
facilities, some of which has come back to FreeBSD, but likewise they gained a
lot by using all that FreeBSD code, not to mention hiring a lot of FreeBSD
developers to work on the product.

Robert N M Watson
Computer Laboratory
University of Cambridge