From: tfb@tfeb.org (Tim Bradshaw)
Subject: [TUHS] Modern BSD system? (was: How good a representative of System V is Solaris)
Date: Sat, 30 May 2009 10:29:54 +0100 [thread overview]
Message-ID: <9A776ADB-D835-479C-AA18-A63BD573ECF5@tfeb.org> (raw)
In-Reply-To: <20090530050137.GE58587@dereel.lemis.com>
On 30 May 2009, at 06:01, Greg 'groggy' Lehey wrote:
>
> 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.
I was really thinking in terms of userland (I don't spend much time
poking around at kernels...). You could still argue that OS X is not
a good example of a modern BSD userland of course - I don't spend
enough time with *BSD to really know what they are like, other than
that, for the most part, everything has been replaced by GNU versions
of itself in all of these systems :-). i guess OS X is kind of like
what I would have hoped a BSD might turn into in some sense.
--tim
next prev parent reply other threads:[~2009-05-30 9:29 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 [this message]
2009-05-30 17:01 ` [TUHS] Modern BSD system? M. Warner Losh
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=9A776ADB-D835-479C-AA18-A63BD573ECF5@tfeb.org \
--to=tfb@tfeb.org \
/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).