The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tfb@tfeb.org (Tim Bradshaw)
Subject: [TUHS] Illumos )
Date: Mon, 5 Jan 2015 12:02:59 +0000	[thread overview]
Message-ID: <EA114F48-926C-4729-A900-E28D645AC57D@tfeb.org> (raw)
In-Reply-To: <20141231224249.GA5833@mcvoy.com>

On 31 Dec 2014, at 22:42, Larry McVoy <lm at mcvoy.com> wrote:

> My view is Linux is pragmatic about stuff, Solaris was dogmatic about it.
> Yeah, the latter leads to better thought out stuff but the former tends
> to be useful sooner.

I think that this is exactly right. I used Solaris for pretty much my whole 
career (BSD then SunOS then Solaris) and eventually I had to give up and just admit that, for reasons I don't understand but are probably to do with culture at Sun, Solaris was making a lot of decisions which smelt like ones that an academic who didn't need to actually care about use in the real world might make, while Linux almost never did that (it had/has other problems, specifically long-term interface stability).

The case that made me finally realise that Solaris Had Lost was ZFS, and specifically ZFS consistency check.  There is (was in ~2010) *no way to check a zpool outside the kernel*, so if you had a zpool which you thought might be damaged you were supposed to check it by importing it.  So all that check code which had to deal with possibly completely random crap in the pool ran in the kernel where any kind of serious mistake involved, if you're lucky, the machine crashing, and if you're not lucky some awful data-corruption problem.  But that's OK, because the ZFS code is all perfect, and never has any problems at all, of course.


  parent reply	other threads:[~2015-01-05 12:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-31  6:22 Larry McVoy
2014-12-31  9:28 ` Wesley Parish
2014-12-31 13:13   ` John Cowan
2014-12-31 17:42     ` Diomidis Spinellis
2014-12-31 20:32       ` Clem Cole
2014-12-31 20:36         ` Larry McVoy
2014-12-31 22:19           ` Jacob Ritorto
2014-12-31 22:42             ` Larry McVoy
2014-12-31 22:50               ` Larry McVoy
2015-01-01  1:17                 ` Larry McVoy
2015-01-01  1:34                   ` Erik E. Fair
2015-01-05 12:02               ` Tim Bradshaw [this message]
2015-01-05 17:04                 ` Jacob Ritorto
2015-01-06  4:54                   ` Andy Kosela
2015-01-06 11:10                     ` Kurt H Maier
2015-01-06 15:37                   ` Tim Bradshaw
2015-01-09  9:23                     ` Jose R. Valverde
2015-01-06 21:58                   ` Clem Cole
2015-01-06 22:02                     ` [TUHS] pre-FSCK days Ronald Natalie
2015-01-07  1:53                     ` [TUHS] Illumos ) Dave Horsfall
2015-01-07 16:26                       ` Clem Cole
2015-01-07 18:32                         ` scj
2015-01-16  8:40                       ` [TUHS] sync; sync; sync; halt (was: Re: Illumos )) Tom Ivar Helbekkmo
2015-01-16 13:39                         ` random832
2015-01-16 14:14                           ` Brantley Coile
2014-12-31  9:46 ` [TUHS] Illumos ) arnold

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=EA114F48-926C-4729-A900-E28D645AC57D@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).