@@ -101,7 +101,11 @@ Comets are disposable, free identities that can be used to quickly join the netw
101To boot a comet, go into the command line and run the following command from the urbit directory you created during Urbit installation:
101To boot a comet, go into the command line and run the following command from the urbit directory you created during Urbit installation:
104$ ./urbit-v0.10.8-darwin/urbit -c mycomet
105$ ./urbit-v0.10.8-darwin/urbit -c mycomet
108+$ ./urbit-v0.10.8-linux64/urbit -c mycomet
107This will take up to an hour, and will spin out a bunch of boot messages. It will also create a directory called `mycomet` in the Unix directory that you ran the command from (which should be your urbit directory).
111This will take up to an hour, and will spin out a bunch of boot messages. It will also create a directory called `mycomet` in the Unix directory that you ran the command from (which should be your urbit directory).
@@ -118,9 +122,16 @@ http: live (insecure, loopback) on 12321
119When your ship is finished booting, you will see either the `~sampel_commet:dojo>` or `~sampel_commet:chat-cli/` prompt. If you're seeing `:chat-cli` press `Ctrl-x` to switch into Dojo.
123When your ship is finished booting, you will see either the `~sampel_commet:dojo>` or `~sampel_commet:chat-cli/` prompt. If you're seeing `:chat-cli` press `Ctrl-x` to switch into Dojo.
121−To exit Urbit, use `Ctrl-d`.
125+To exit Urbit, use `control-d` or enter `|exit` into Dojo.
123−To start your ship up again, run `./urbit-v0.10.8-darwin/urbit mycomet` from your `urbit` directory.
127+To start your ship up again, run the following from your `urbit` directory (note the lack of `-c` argument):
130+$ ./urbit-v0.10.8-darwin/urbit mycomet
133+$ ./urbit-v0.10.8-linux64/urbit mycomet
125### The Dojo
136### The Dojo
@@ -225,30 +236,58 @@ Find the absolute path to the keyfile that you downloaded from Bridge. Copy it.
226#### Step 3: Run the boot command
237#### Step 3: Run the boot command
228−If you are not already within the directory you installed above, enter it by running `cd urbit-v0.10.8-darwin` (for Mac) or `cd urbit-v0.10.8-linux64` (for Linux) from where you ran the install commands. It contains your Urbit binary, and your ship will be installed here as well.
239+Enter your `urbit` directory.
230Once you're inside, run the command below, except with `sampel-palnet` replaced by the name of your
241Once you're inside, run the command below, except with `sampel-palnet` replaced by the name of your
231Urbit identity, and `path/to/my-planet.key` replaced with the path to your keyfile:
242Urbit identity, and `path/to/my-planet.key` replaced with the path to your keyfile:
246+./urbit-v0.10.8-darwin/urbit -w sampel-palnet -k path/to/my-planet.key
234−./urbit -w sampel-palnet -k path/to/my-planet.key
249+./urbit-v0.10.8-linux64/urbit -w sampel-palnet -k path/to/my-planet.key
237Or, if you'd prefer to copy your key in, you can run:
252Or, if you'd prefer to copy your key in, you can run:
256+./urbit-v0.10.8-darwin/urbit -w sampel-palnet -G rAnDoMkEy
240−./urbit -w sampel-palnet -G rAnDoMkEy
259+./urbit-v0.10.8-linux64/urbit -w sampel-palnet -G rAnDoMkEy
243Either command will create a directory called `sampel-palnet/` and begin building your ship. It may take a few minutes.
262Either command will create a directory called `sampel-palnet/` and begin building your ship. It may take a few minutes.
245−When your ship is finished booting, you will see either the `~sampel-palnet:dojo>` or `~sampel-palnet:chat-cli/` prompt. If you're seeing `:chat-cli` press `Ctrl-x` to switch into Dojo. At that point, you should permanently erase your keyfile from your machine.
264+When your ship is finished booting, you will see either the `~sampel-palnet:dojo>` or `~sampel-palnet:chat-cli/` prompt. If you're seeing `:chat-cli` press `Ctrl-x` to switch into Dojo.
266+To shut down your ship, use `control-d`. To start your ship up again, run the following from your `urbit` directory:
247−To shut down your ship, use `Ctrl-d`. To start your ship up again, run `./urbit sampel-palnet/` from the directory where your Urbit binary is saved. Note that in this usage, `sampel-palnet/` is the path of a folder, which by default is located in the same folder as the Urbit binary. This folder is called your ship's **pier**, and you can put it wherever you like.
268+```sh
270+./urbit-v0.10.8-darwin/urbit sampel-palnet
273+./urbit-v0.10.8-linux64/urbit sampel-palnet
276+Note that `sampel-palnet/` is the path of a folder, which we just created in your `urbit` directory. This folder is called your ship's **pier**.
249Never boot multiple instances of your ship at the same time. You can prevent this from happening on accident by only ever keeping a single copy of your pier.
278Never boot multiple instances of your ship at the same time. You can prevent this from happening on accident by only ever keeping a single copy of your pier.
251−**Important:** once a key has been used to boot a ship onto the network, it cannot be used to boot that ship again later - doing so will cause communication problems with other ships. For this reason you should **delete the keyfile from your machine once your ship has booted successfully**. (If you do use the same key twice, you'll need to conduct a [personal breach](#breaches) to restore your ship to full functionality).
280+**Important:** once a key has been used to boot a ship onto the network, it cannot be used to boot that ship again later - doing so will cause communication problems with other ships.
282+For this reason you should **delete the keyfile from your machine once your ship has booted successfully**.
284+If you do use the same key twice, you'll need to conduct a [personal breach](#breaches) to restore your ship to full functionality).
286+Delete the keyfile with the command below:
289+rm path/to/my-planet.key
253### Updating to the latest binary
292### Updating to the latest binary
@@ -256,34 +295,47 @@ Most updates to Urbit are downloaded and applied automatically as OTA (Over the
257To update to the latest binary, download and extract it to replace your existing one. Then run it as before.
296To update to the latest binary, download and extract it to replace your existing one. Then run it as before.
259−For example, if in your current `urbit` directory you have an `urbit-v0.10.7-darwin` directory along with a ship directory called `mycomet`, and a new `urbit-v0.10.8-darwin` binary was just released, then you'd run the following commands from your `urbit` directory (the example commands below use the darwin installer, but you should use the one for your OS):
298+For example, if in your current `urbit` directory you have an `urbit-v0.10.7-<OS>` directory along with a ship directory called `mycomet`, and a new `urbit-v0.10.8-<OS>` binary was just released, then you'd run the following commands from your `urbit` directory:
261First shut down your ship, by running the following in dojo (or control-d).
300First shut down your ship, by running the following in dojo (or control-d).
266−Next download and extract the most recent binary from inside your `urbit` directory:
268−curl -O https://bootstrap.urbit.org/urbit-v0.10.8-darwin.tgz
269−tar xzf urbit-v0.10.8-darwin.tgz
272Delete the old binary directory from your `urbit` directory:
305Delete the old binary directory from your `urbit` directory:
274**NOTE**: Your ship itself can be reused, only the binary needs to be changed. This is why we have the directory structure configured as an urbit directory that contains your ship and your binary. This structure makes it easy to swap in new binaries. If you have your ship *inside* the `urbit-vX.XX.X` directory, move it out before deleting that directory.
307**NOTE**: Your ship itself can be reused, only the binary needs to be changed. This is why we have the directory structure configured as an urbit directory that contains your ship and your binary. This structure makes it easy to swap in new binaries. If you have your ship *inside* the `urbit-vX.XX.X` directory, move it out before deleting that directory.
276rm -rf urbit-v0.10.7-darwin
310rm -rf urbit-v0.10.7-darwin
313+rm -rf urbit-v0.10.7-linux64
279−Start up your ship with the new binary from your `urbit` directory:
316+Next download and extract the most recent binary from inside your `urbit` directory:
319+curl -O https://bootstrap.urbit.org/urbit-v0.10.8-darwin.tgz
320+tar xzf urbit-v0.10.8-darwin.tgz
323+curl -O https://bootstrap.urbit.org/urbit-v0.10.8-linux64.tgz
324+tar xzf urbit-v0.10.8-linux64.tgz
327+Start up your ship with the new binary from your `urbit` directory:
281./urbit-v0.10.8-darwin/urbit mycomet
330./urbit-v0.10.8-darwin/urbit mycomet
333+./urbit-v0.10.8-linux64/urbit mycomet
284Then you're good to go, in the future you'll just modify the version numbers in the example above to the most recent version.
336Then you're good to go, in the future you'll just modify the version numbers in the example above to the most recent version.
286−### Breaches
338+### Breaches {#breaches}
288An important concept on the Urbit network is that of continuity. Continuity refers to how ships remember the order of their own network messages and the network messages of others -- these messages are numbered, starting from zero. A breach is when ships on the network agree to forget about this sequence and treat one or more ships like they are brand new.
340An important concept on the Urbit network is that of continuity. Continuity refers to how ships remember the order of their own network messages and the network messages of others -- these messages are numbered, starting from zero. A breach is when ships on the network agree to forget about this sequence and treat one or more ships like they are brand new.