@@ -2,10 +2,10 @@
22navhome: /docs/
33next: true
44sort: 3
5−title: Basic operation
5+title: Administration and Operation
66---
77
8−# Basic operation
8+# Administration
99
1010<div class="row">
1111<div class="col-md-8">
@@ -36,6 +36,16 @@ To log Urbit's command line output to a file, use `script`:
3636
3737 $ script urbit.log urbit your-urbit
3838
39+## Moving your pier
40+
41+Piers are designed to be portable, but it *must* be done while the Urbit is turned off. Urbit networking is stateful, so you can't run two copies of the same Urbit in two places.
42+
43+To move a pier, simply move the contents of the directory it lives in. To keep these files as small as possible we usually use the `--sparse` option in `tar`. With a pier `your-urbit/` something like this (from inside `urbit/`) should work:
44+
45+ tar -Scvzf your-urbit.tar.gz ./your-urbit/
46+
47+# Operation
48+
3949## Console
4050
4151Your Urbit terminal is separated into two parts: the prompt (the bottom line) and the record (everything above that). The record is shared; all the output from all the apps in your command set appears in it. The prompt is multiplexed.
@@ -89,14 +99,6 @@ You can use the resulting output in the same installation flow from [install](/d
8999
90100Moons are automatically synced to their parent `%kids` desk, and can control applications on their parent planet using `|link`. You can read more about those things in the [filesystem](/docs/using/filesystem) and [console](/docs/using/shell) walkthroughs.
91101
92−## Moving your pier
93−
94−Piers are designed to be portable, but it *must* be done while the Urbit is turned off. Urbit networking is stateful, so you can't run two copies of the same Urbit in two places.
95−
96−To move a pier, simply move the contents of the directory it lives in. To keep these files as small as possible we usually use the `--sparse` option in `tar`. With a pier `your-urbit/` something like this (from inside `urbit/`) should work:
97−
98− tar -Scvzf your-urbit.tar.gz ./your-urbit/
99−
100102## Continuity breaches
101103
102104While the Urbit network is in this alpha state we sometimes have to reboot the whole network. This happens either when major changes need to be shipped or we hit a bug that can't be fixed over the air.