9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: blstuart@bellsouth.net
To: 9fans@9fans.net
Subject: Re: [9fans] Accessing Mac OS Extended drives
Date: Sun,  9 Mar 2014 22:19:34 -0400	[thread overview]
Message-ID: <63b66fddcab7a5f6d6738cd1ac0c1229@bellsouth.net> (raw)
In-Reply-To: <2294484cb1126f047aef616de74886f1@mikro.quanstro.net>

>> - Taking a snapshot is an O(1) operation
> 
> most interestingly, that is a property of #ℙ, which is not directly
> tied to θfs.  so you could, with arrangements, snapshot any other
> file system.

That's correct.  #ℙ doesn't depend on θfs at all.  θfs can be used
without #ℙ, but it does have some provisions for using #ℙ to provide a
/n/dump/yyyy/mmdd name space.  With similar provision, one could use
#ℙ to create a snapshotted kfs that was similarly efficient.

BLS




      reply	other threads:[~2014-03-10  2:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07  8:44 Rubén Berenguel
2014-03-07  8:54 ` Sergey Zhilkin
2014-03-07  9:00   ` Gorka Guardiola
2014-03-07  9:47     ` David Swasey
2014-03-07 16:49     ` erik quanstrom
2014-03-08 12:30       ` Rubén Berenguel
2014-03-08 12:35         ` erik quanstrom
2014-03-08 12:59           ` Rubén Berenguel
2014-03-08 13:03             ` erik quanstrom
2014-03-08 14:08               ` Rubén Berenguel
2014-03-08 14:18                 ` erik quanstrom
2014-03-08 15:16     ` Jeff Sickel
2014-03-08 17:53       ` Rubén Berenguel
2014-03-08 17:58         ` erik quanstrom
2014-03-08 18:11           ` Rubén Berenguel
2014-03-09 16:42             ` erik quanstrom
2014-03-08 18:27           ` Steve Simon
2014-03-09  8:39             ` Rubén Berenguel
2014-03-09 17:52               ` Jeff Sickel
2014-03-09 18:05                 ` Rubén Berenguel
2014-03-10  2:01           ` blstuart
2014-03-10  2:08             ` erik quanstrom
2014-03-10  2:19               ` blstuart [this message]

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=63b66fddcab7a5f6d6738cd1ac0c1229@bellsouth.net \
    --to=blstuart@bellsouth.net \
    --cc=9fans@9fans.net \
    /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).