The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: imp@bsdimp.com (M. Warner Losh)
Subject: [TUHS] Modern BSD system?
Date: Sat, 30 May 2009 11:01:47 -0600 (MDT)	[thread overview]
Message-ID: <20090530.110147.84361927.imp@bsdimp.com> (raw)
In-Reply-To: <20090530050137.GE58587@dereel.lemis.com>

In message: <20090530050137.GE58587 at dereel.lemis.com>
            "Greg 'groggy' Lehey" <grog at lemis.com> writes:
: On Friday, 29 May 2009 at 14:08:19 +0100, Tim Bradshaw wrote:
: > If you want to know what a *modern* System V or BSD is like then,
: > sure, look at Solaris or OS X.
: 
: I won't argue the Solaris comparison, though I'm sure people could,
: but certainly Mac OS X is not a good example of modern BSD.  The
: kernel has very little BSD in it.  Look at FreeBSD, NetBSD or OpenBSD
: for that.

There's more BSD in the Mac OS X kernel than you might think, at least
judging from the stream of patches that come back into FreeBSD.  They
use BSD networking, and FreeBSD's 802.11 stack, for example.  Some of
the file system code is also from BSD.  Darwin is a classic example of
what one can do when one doesn't care where one gets one's code from.
This has both pluses and minuses...

Warner



      parent reply	other threads:[~2009-05-30 17:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29 12:12 [TUHS] How good a representative of System V is Solaris A P Garcia
2009-05-29 13:08 ` Tim Bradshaw
2009-05-29 13:32   ` Brantley Coile
2009-05-30  0:20     ` Michael Kerpan
2009-05-30  1:51       ` Jason Stevens
2009-05-30  9:10         ` Wesley Parish
2009-05-30  2:15       ` Jason Stevens
2009-05-30  5:01   ` [TUHS] Modern BSD system? (was: How good a representative of System V is Solaris) Greg 'groggy' Lehey
2009-05-30  9:29     ` Tim Bradshaw
2009-05-30 17:01     ` M. Warner Losh [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090530.110147.84361927.imp@bsdimp.com \
    --to=imp@bsdimp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).