9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] hgfs?
Date: Fri, 27 May 2011 08:21:14 -0400	[thread overview]
Message-ID: <6e074b83a55da47bb35cafb80845edc2@ladd.quanstro.net> (raw)
In-Reply-To: <20110527081252.CA6F2B827@mail.bitblocks.com>

> > if i'm missing why this is an interesting idea, i'd love to know what
> > i don't see.
>
> I partially agree with you; hence the suggestion about editor
> integration. But I am wondering just how far this model can be
> pushed or extended seamlessly.
>
> Features such as atomic commits, changesets, branches, push,
> pull, merge etc. can be useful in multiple contexts so it
> would be nice if they can integrated smoothly in an FS.
>
> Example uses:
> - A backup is nothing but a previous commit. A nightly
>   backup cron job to do "echo `{date} > .commit"
> - Initial system install is like a clone.

the problem here is that no scm that i know of has storage
capabilities.  you'd still need a file system underneath.  it
sounds like you're proposing something completely different
than hg, even if it's compatable on some level.

> - An OS upgrade is like a pull.

is like, but they're different.  you can't take every file from
the base.  one of the problems with replica is that it's hard
to work out the local differences.  hg doesn't make this any
easier.

> - Installing a package is like a pull (or if you built it
>   locally, a commit)
> - Uinstall is reverting the change.
> - Each machine's config can be in its own branch.
> - You can use clone to create sandboxes.
> - A commit makes your private temp view permanent and
>   potentially visible to others.

this is interesting, but what you're talking about sounds a
lot more like user-controlled snapshotting than scm to me.

do you propose being able to do this at any level in the fs
heirarchy, or just at the root?  if not just at the root, how
is a namespace constructed?

i'm not sure why one would want each machine's config in
its own branch.  remerging default could be a real administrative
pain.  in fact, i wonder how one would keep things sane.
how would build some cannonical rules, like we have for
the namespace (namespace(4))?

> - Conversely old commits can be spilled to a backup
>   media (current SCMs want the entire history online).

backup media?  what's that?  ;-)

i'd be against any scheme that moves data from its original
location.  the worm property is just great.  i've reconstructed
full worms from partial worms a few times.  russ posted an
interesting story about recovering a venti this way.

- erik

http://www.quanstro.net/magic/man2html/4/namespace



  reply	other threads:[~2011-05-27 12:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26  3:27 [9fans] 9vx bootimage build instructions? EBo
2011-05-26  3:37 ` erik quanstrom
2011-05-26  3:58   ` EBo
2011-05-26  4:05     ` EBo
2011-05-26  4:18       ` Devon H. O'Dell
2011-05-26  4:24       ` Bakul Shah
2011-05-26  7:40   ` yy
2011-05-26 14:06     ` [9fans] 9vx patches [was: 9vx bootimage build instructions?] EBo
2011-05-26 14:26       ` Devon H. O'Dell
2011-05-26 16:39         ` [9fans] hgfs? Bakul Shah
2011-05-26 22:12           ` simon softnet
2011-05-26 23:24           ` Iruatã Souza
2011-05-27  0:16             ` erik quanstrom
2011-05-27  8:12               ` Bakul Shah
2011-05-27 12:21                 ` erik quanstrom [this message]
2011-05-27 14:45                   ` Lucio De Re
2011-05-27 17:18                   ` Bakul Shah
2011-05-27 17:30                     ` erik quanstrom
2011-05-26 15:34       ` [9fans] 9vx patches [was: 9vx bootimage build instructions?] erik quanstrom
2011-05-26 18:17         ` EBo
2011-05-26 18:58           ` erik quanstrom
2011-05-26 19:17             ` EBo

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=6e074b83a55da47bb35cafb80845edc2@ladd.quanstro.net \
    --to=quanstro@quanstro.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).