9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /n/sources/contrib/
Date: Mon, 19 Nov 2007 12:38:34 -0500	[thread overview]
Message-ID: <f7430358c6da5a4a19e15043c372bbdc@quanstro.net> (raw)
In-Reply-To: <20071119021515.D29241E8C4D@holo.morphisms.net>

> it's not necessarily hard -- you just write the code -- but it's
> more fragile to do this kind of exact mirroring, because you
> can't make any local modifications without breaking the 
> mirroring.  if you decide you don't want to keep some huge
> subtree, for example, or you want to add a few locally
> maintained files.

on the other hand, a mirror doesn't really operate at the
level of the filesystem.  a mirror needs to avoid the normal
permission checking. my experience has been that filesystem-level
copies tend to have errors in them and the errors increase over
time.  and the muid is wrong.  that's a big deal for us.

maybe plan 9 needs dump.

i could be out of step here.  my basic assumption is that unless
a mirror is exact, it's not a mirror.  you know, might be missing
some files.  owners might be different.  muid broke. you know, ymmv.
if i set up mirrors like that, ever time anyone had a problem
with a file, they'd blame me first.

> the file system is a good interface -- witness all of plan 9 --
> and if you're going to start working at a lower level i just
> think you need a much more compelling reason.

the file interface has nothing to do with this problem.
it's the arenas that need copying.  if you do that, the files will
take care of themselves.

venti itself doesn't even use 9p.

> if your goal is to have a live backup of a system, then some
> disk-level thing might be exactly right.  but for having a 
> local mirror of sources, the lsr file and a simple script to
> run the cp commands is simple and more flexible.

by the way, if the datestamp in the lsr file is not the current
day (you know, cp -x), you'll miss the file with the lsr file.

- erik


  reply	other threads:[~2007-11-19 17:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-17  5:35 lucio
2007-11-17 18:05 ` andrey mirtchovski
2007-11-17 18:55   ` lucio
2007-11-17 18:56   ` lucio
2007-11-17 22:00   ` erik quanstrom
2007-11-18  4:39     ` lucio
2007-11-18  5:08       ` erik quanstrom
2007-11-18  5:30         ` lucio
2007-11-18 10:25           ` johnny
2007-11-18 11:04             ` lucio
2007-11-18 11:33     ` roger peppe
2007-11-18 13:24       ` lucio
2007-11-18 14:18       ` erik quanstrom
2007-11-18 18:17       ` johnny
2007-11-19 16:29         ` roger peppe
2007-11-18 21:23       ` johnny
2007-11-17 18:13 ` Uriel
2007-11-17 18:58   ` lucio
2007-11-18 15:17 ` Russ Cox
2007-11-18 15:29   ` erik quanstrom
2007-11-18 18:26     ` Francisco J Ballesteros
2007-11-19  2:15     ` Russ Cox
2007-11-19 17:38       ` erik quanstrom [this message]
2007-11-19 17:53         ` Russ Cox
2014-05-23  7:20 David Hoskin

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