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] suicide message on vmware
Date: Fri,  6 Jun 2014 12:59:11 -0400	[thread overview]
Message-ID: <5ae0b0ece962c5704c75a0fb88f2663d@brasstown.quanstro.net> (raw)
In-Reply-To: <20140606164945.70A57B827@mail.bitblocks.com>

> What two databases?

the divergent versions of /sys/lib/dist/replica/plan9.db and its log
on the sources and 9atom.

> Replica respects local changes at the file level.  You still
> have to do a manual merge if the server version changed as
> well.

that's what i said, but this is remove vs remote, and replica is
unable to deal with this sort of issue.

> The bigger issue is that the unit of update needs to be a
> *set* of files that take a system from one consistent state to
> another. If you update only a subset of files, you may be left
> with an inconsistent system.

 it would be a great feature, but it's unrelated to this failure.

i'm part of the way there with the patch system in atom.  in theory
a few scripts could allow one to add changes as required.  unfortunately,
it's pretty easy for this to go wrong, even with tools like hg.

> For a foolproof update in case of incompatible kernel changes
> (and if you're running the same distribution as you pulled
> from), you should

if one recalls back to the beginning of the 4th edition, the
install cd would upgrade things as well as to initial installs.

- erik



  reply	other threads:[~2014-06-06 16:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06  3:15 Ramakrishnan Muthukrishnan
2014-06-06  3:21 ` erik quanstrom
2014-06-06  4:05   ` Ramakrishnan Muthukrishnan
2014-06-06  5:18     ` Ramakrishnan Muthukrishnan
2014-06-06  6:00       ` Bakul Shah
2014-06-06  7:32         ` Ramakrishnan Muthukrishnan
2014-06-06  8:00           ` Bakul Shah
2014-06-06  8:33             ` Ramakrishnan Muthukrishnan
2014-06-06 15:24 ` Bakul Shah
2014-06-06 15:35   ` erik quanstrom
2014-06-06 15:46     ` Ramakrishnan Muthukrishnan
2014-06-06 15:50       ` erik quanstrom
2014-06-06 16:49     ` Bakul Shah
2014-06-06 16:59       ` erik quanstrom [this message]
2014-06-06 15:52   ` Ramakrishnan Muthukrishnan
2014-06-06 15:55     ` erik quanstrom
2014-06-06 16:07       ` Ramakrishnan Muthukrishnan
2014-06-06 16:26         ` erik quanstrom
2014-06-06 16:38           ` Ramakrishnan Muthukrishnan
2014-06-07 11:24           ` Ramakrishnan Muthukrishnan
2014-06-07 11:29             ` Aram Hăvărneanu
2014-06-07 14:42             ` erik quanstrom
2014-06-07 17:11               ` Ramakrishnan Muthukrishnan

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=5ae0b0ece962c5704c75a0fb88f2663d@brasstown.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).