The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@bitmover.com (Larry McVoy)
Subject: [TUHS] TUHS Digest, Vol 31, Issue 10
Date: Sat, 20 May 2006 20:32:01 -0700	[thread overview]
Message-ID: <20060521033201.GA12282@bitmover.com> (raw)
In-Reply-To: <mailman.3.1148090400.69531.tuhs@minnie.tuhs.org>

> I couldn't be happier.  They suck.  And even SunOS sucks in some ways, it's
> way behind Linux.  I'm a file system guy, I'm the last guy who did anything
> significant to UFS (ask Kirk), and I have to admit that the Linux guys are

As Mike H pointed out, Kirk has been more busy than I remembered and has been
busy in UFS, so I retract that.

That point made, I think the general point that I was making, which is that 
the Linux guys seem to be moving faster, is still valid.  I'm very fond of 
UFS and have a lot of respect for Kirk, so it's not about that, it's just 
that the energy seems to be elsewhere.  For better or worse.
-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com



           reply	other threads:[~2006-05-21  3:32 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <mailman.3.1148090400.69531.tuhs@minnie.tuhs.org>]

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=20060521033201.GA12282@bitmover.com \
    --to=lm@bitmover.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).