9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: cyspace <cyspace@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Looks like I'll be able to drop venti from my mac...
Date: Thu, 10 Aug 2006 08:29:56 +0100	[thread overview]
Message-ID: <413DE6AF-65D3-4D5A-8074-3733BC0F39AE@gmail.com> (raw)
In-Reply-To: <31863FC1-32C9-4CD4-93D7-2E0B504523FB@telus.net>

Hi, I read sometime ago about Sun's ZFS Filesystem and it has been  
described as one of the most "advanced file systems on the  
planet.."  (Plan9 notwithstanding :-)). Among its many features are a  
set of flexible, dynamic and complex snap-shotting capabilities that  
sound very much like the technology that could underly Apple  
Leopard's new back-p capabilities. This is all the more interesting  
in that ZFS was and has been vigorously discussed within Apple as a  
contender for the successor to the hybrid HFS+ OS X presently labous  
under. As Steve Jobs announced they were deliberately not going to  
announce several key Leopard technologies this could be a  
possibility.  Just speculating,

Cheers,

Cy

On 9 Aug 2006, at 22:52, Paul Lalonde wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> There are a couple of things I do expect to see in Apple's version  
> that will make life easier for me.
> I had to wrap my snapshot taking in a pile of scripts to track the  
> hash of the previous snapshots of the various trees I choose to  
> back up, or else performance went completely to hell.  As is, a  
> snapshot is way expensive - I don't do them as often as I'd like.   
> Ideally my script would be clever enough to cache file modification  
> times and only re-snap the changes, but that way lies madness and a  
> loss of the fire-and-forget advantage Venti has.  Not to mention  
> how painful it is to read my past snapshots through 9P without a  
> decent browser...
> I'm pretty sure apple's version won't need these kinds of voodoo  
> from the user - the UI is likely to be pretty and functional.
>
> On 9-Aug-06, at 2:20 PM, John Floren wrote:
>
>> On 8/9/06, Benn Newman <newmanbe@sdf.lonestar.org> wrote:
>>> Paul Lalonde said:
>>> > Essentially the same feature set.  Anyone know what the tech is
>>> > behind this?
>>> Ha! You are talking about Apple. What do you expect? ;)
>>> --
>>> Benn Newman
>>>
>> Well, Xerox never had this... hmm. I guess Apple has had to borrow
>> from other places too. Guesses on how long it will be before Windows
>> has this?
>> Cheers
>>
>> John
>> -- 
>> "The first thing we do, let's kill all the lawyers" --  
>> Shakespeare, Henry VI
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (Darwin)
>
> iD8DBQFE2lkfpJeHo/Fbu1wRAki+AJ9ddVmBqu79DbZSY9hN0iE13KH1PgCglNCe
> 6O3MHFSGxyk2VwAjSkCHnsU=
> =2zLj
> -----END PGP SIGNATURE-----



  reply	other threads:[~2006-08-10  7:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08 18:51 Paul Lalonde
2006-08-09 20:23 ` Benn Newman
2006-08-09 21:20   ` John Floren
2006-08-09 21:52     ` Paul Lalonde
2006-08-10  7:29       ` cyspace [this message]
2006-08-09 22:48     ` David Leimbach
2006-08-09 23:12       ` Corey

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=413DE6AF-65D3-4D5A-8074-3733BC0F39AE@gmail.com \
    --to=cyspace@gmail.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).