From d99c82ba776be191b8f6f95e7e718980e5d172ce Mon Sep 17 00:00:00 2001 From: Philip C Monk Date: Fri, 6 Nov 2015 18:26:39 -0500 Subject: [PATCH] continuity breach instructions --- pub/docs/user/start.mdy | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/pub/docs/user/start.mdy b/pub/docs/user/start.mdy index b858485c8..f4bd4399e 100644 --- a/pub/docs/user/start.mdy +++ b/pub/docs/user/start.mdy @@ -225,3 +225,19 @@ lot of other things you can do with it. But you can see a simple example in `$PIER/try/hello/hymn.hook`, accessible at http://localhost:8080/home/try/hello + +## Continuity breaches + +We occasionally perform "continuity breaches", wherein every +urbit on the network must be created from scratch. This occurs +whenever a major urbit (usually `~zod` or `~doznec`) loses state +and/or corrupts its event log. We will always send a message on +the urbit-dev mailing list when this happens. + +To get on the new network, delete your current urbits, or at +least move them out of sight. Pull the latest master from urbit +and run `make`. Then create your urbit again with `bin/urbit -c +` or `bin/urbit -w -t `. You'll have to +rejoin `/urbit-meta` and copy in any file changes you wish to +preserve. If you're having difficulty getting on the new +continuity era, send an email to urbit-dev.