From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] ZFS?
Date: Tue, 2 May 2006 00:48:24 -0500 [thread overview]
Message-ID: <1E8F173A-13EB-42B2-A0C6-45DEBF2121A7@corpus-callosum.com> (raw)
In-Reply-To: <445651F3.4040208@andrew.cmu.edu>
On May 1, 2006, at 1:22 PM, Chad Dougherty wrote:
>
> (I dive into foxhole, cover ears...)
>
Now now, no need to dive into a hole and cover your ears...
After reading and seeing the 'flash' demo on ZFS, I just can't forget
a little experience at a w3c conference years ago with a Sun employee
(at the time, he left shortly to form a company named after a drum):
"Java is 100% buzz-word compliant."
Too bad Guido didn't get more attention at that conference... the
Python presentations ran circles around the Java options at the time.
But that dates me.
Alas, I just want universal (true multi-platform) archival services
at a decent price that doesn't make the workflow more cumbersome.
jas
next prev parent reply other threads:[~2006-05-02 5:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 18:22 Chad Dougherty
2006-05-02 5:48 ` Jeff Sickel [this message]
2006-05-02 12:37 ` ems
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=1E8F173A-13EB-42B2-A0C6-45DEBF2121A7@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@cse.psu.edu \
/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).