79a2b22 · urbit.org · git.iko.soy

content/docs/azimuth/ecliptic.md+1−1

compare with master

unifiedsplit

@@ -101,7 +101,7 @@ Corresponds to the layer 2 `%spawn` action.

101

102Transfer `_point` to `_target`, clearing all permissions data and keys if

103`_reset` is true. `_reset` set to makes this transaction a

104−[breach](/using/id/guide-to-breaches), and thus this action increments the

104+[breach](/using/id/guide-to-resets), and thus this action increments the

105[`continuityNumber`](/docs/azimuth/azimuth-eth#points) of `_point`, and usually

106the `keyRevisionNumber` as well (see [Life and

107Rift](/docs/azimuth/life-and-rift)).

content/docs/azimuth/life-and-rift.md+1−1

@@ -7,7 +7,7 @@ template = "doc.html"

7Associated to every Azimuth point are two non-negative integers known as _life_

8and _rift_. This numbering system partition messages according to the quantity

9of networking key changes and quantity of

10−[breaches](/using/id/guide-to-breaches), respectively. This is explained in

10+[breaches](/using/id/guide-to-resets), respectively. This is explained in

11more detail below. These values are utilized by [Ames](/docs/arvo/ames/ames)

12and [Jael](/docs/arvo/jael/jael-api) to ensure that communication between

13ships is always done with the most recent set of networking keys, and that

content/docs/glossary/ames.md+3−2

@@ -11,9 +11,10 @@ Your ship upgrades itself with [OTA updates](/docs/glossary/ota-updates) via com

11

12Network continuity occasionally needs to be broken, either at an individual

13level to fix networking issues or at a network-wide level to update Arvo beyond

14−what OTA updates are capable of doing. These events are called [breaches](/docs/glossary/breach).

14+what OTA updates are capable of doing. These events are called [factory resets](/docs/glossary/reset).

15### Further Reading

16

17- [The Ames tutorial](/docs/arvo/ames/ames): An in-depth technical guide to the Ames protocol.

18−- [A Guide to Breaches](/using/id/guide-to-breaches): Instructions on handling continuity breaches (resets) on the Ames network.

18+- [A Guide to Factory Reset](/using/id/guide-to-resets): Instructions on

19+ perfming factory resets.

19- [Ship Troubleshooting](/using/os/ship-troubleshooting): General instructions on getting your ship to work, which includes network connectivity issues.

20- [Ship Troubleshooting](/using/os/ship-troubleshooting): General instructions on getting your ship to work, which includes network connectivity issues.

content/docs/glossary/breach.mddeleted−28

@@ -1,28 +0,0 @@

1−+++

2−title = "Breach"

3−template = "doc.html"

4−[extra]

5−category = "arvo"

6−+++

7−

8−Continuity on the [Ames](/docs/glossary/ames) network occasionally needs to be broken

9−(though with increasing rarity) in order to correct a networking error. These

10−infrequent events are known as **breaches**, which cause an individual ship to

11−forget its network message history.

12−

13−Breaches are always initiated by the user, frequently in response to a

14−connectivity error. The easiest way to do this is with [Bridge](/docs/glossary/bridge).

15−There are two types of personal breaches: changing networking keys, and changing

16−the Urbit ID ownership address.

17−

18−Historically, there were also "network breaches", which happened when a major

19−Arvo revision that could not be implemented via an [OTA update](/docs/glossary/ota-updates)

20−occured. Network breaches were effectively breaching every ship on the network

21−at once. The most recent network breach occurred in December 2020, and we expect

22−it to be the final one.

23−

24−### Further Reading

25−

26−- [Guide to breaches](/using/id/guide-to-breaches): A more in-depth

27− explanation of breaches, including how to perform a personal breach.

28−- [Ship Troubleshooting](/using/os/ship-troubleshooting): General instructions on getting your ship to work, which includes network connectivity issues.

content/docs/glossary/jael.md+4−1

@@ -5,4 +5,7 @@ template = "doc.html"

5category = "arvo"

6+++

7

8+**Jael** is the [vane](/docs/glossary/vane) that keeps track of

9+[Azimuth](/docs/glossary/azimuth) related information. For each

8−**Jael** is the [vane](/docs/glossary/vane) that keeps track of [Azimuth](/docs/glossary/azimuth) related information. For each [ship](/docs/glossary/ship), this consists of its networking keys, its revision number (or _life_), its breach number, and who the sponsor of the ship is.

10+[ship](/docs/glossary/ship), this consists of its networking keys, its revision

11+number (or _life_), its factory reset number (or _rift_), and who the sponsor of the ship is.

content/docs/glossary/pier.md+14−4

@@ -5,14 +5,24 @@ template = "doc.html"

5category = "arvo"

6+++

7

8+A **pier** is the directory which contains the state of an Urbit

8−A **pier** is the directory which contains the state of an Urbit [ship](/docs/glossary/ship). It is automatically created in the current directory when booting a ship for the first time.

9+[ship](/docs/glossary/ship). It is automatically created in the current

10+directory when booting a ship for the first time.

9

11

10−Your pier should be kept safe - if it's deleted, you will need to perform a [breach](/docs/glossary/breach) in order to advise the rest of the network that your ship's state has been lost.

12+Your pier should be kept safe - if it's deleted, you will need to perform a

13+[factory reset](/docs/glossary/reset) in order to inform the rest of the network

14+that your ship's state has been lost.

11

15

12−Note that a backup should usually _not_ be taken of your pier as a means of keeping it safe - once the ship is run on the network, the backup will be outdated and running from it will necessitate a breach. A running ship automatically backs up its own state within the pier directory for recovery purposes, so as long as the pier is preserved, recovery from most problems is possible.

16+Note that a backup should usually _not_ be taken of your pier as a means of

17+keeping it safe - once the ship is run on the network, the backup will be

18+outdated and running from it will necessitate a factory reset. A running ship

19+automatically backs up its own state within the pier directory for recovery

20+purposes, so as long as the pier is preserved, recovery from most problems is

21+possible.

13

22

14### Further Reading

23### Further Reading

15

24

16- [Event Log](/docs/glossary/eventlog): The main important content of the pier directory.

25- [Event Log](/docs/glossary/eventlog): The main important content of the pier directory.

17−- [A Guide to Breaches](/using/id/guide-to-breaches): Instructions on handling continuity breaches (resets) on the Ames network.

26+- [Guide to Factory Resets](/using/id/guide-to-resets): Instructions on

27+ performing a factory reset.

18- [Ship Troubleshooting](/using/os/ship-troubleshooting): General instructions on getting your ship to work, which includes network connectivity issues.

28- [Ship Troubleshooting](/using/os/ship-troubleshooting): General instructions on getting your ship to work, which includes network connectivity issues.

content/docs/glossary/reset.mdnew file+32

@@ -0,0 +1,32 @@

1++++

2+title = "Factory Reset"

3+template = "doc.html"

4+[extra]

5+category = "arvo"

6++++

7+

8+Continuity on the [Ames](/docs/glossary/ames) network occasionally needs to be

9+broken in order to correct a networking error. These infrequent events are known

10+as **factory resets**, which causes an individual ship to forget its network

11+message history and restores it to the state in which you booted it for the

12+first time.

13+

14+Factory resets are always initiated by the user, frequently in response to a

15+connectivity error. The easiest way to do this is with [Bridge](/docs/glossary/bridge).

16+There are two types of factory resets: changing networking keys, and changing

17+the Urbit ID ownership address.

18+

19+Historically, there were also "network resets", which happened when a major

20+Arvo revision that could not be implemented via an [OTA update](/docs/glossary/ota-updates)

21+occured. Network resets were effectively factory resetting every ship on the network

22+at once. The most recent network reset occurred in December 2020, and we expect

23+it to be the final one.

24+

25+Factory resets used to be called "breaches", and you may still see this language

26+used in some places. The notion is identical, only the name differs.

27+

28+### Further Reading

29+

30+- [Guide to Factory Resets](/using/id/guide-to-resets): A more in-depth

31+ explanation of factory resets, including how to perform one.

32+- [Ship Troubleshooting](/using/os/ship-troubleshooting): General instructions on getting your ship to work, which includes network connectivity issues.

content/using/id/_index.md+1−1

@@ -38,7 +38,7 @@ How to resolve common issues in Bridge.

38If you own a star, invite pools allow your friends to invite others onto the

39network.

40

41−### [Guide to Breaches](/using/id/guide-to-breaches)

41+### [Guide to Resets](/using/id/guide-to-resets)

42

43What to do when things go very wrong and you need to start over.

44

content/using/id/guide-to-breaches.md → content/using/id/guide-to-resets.mdrenamed+48−36

@@ -1,16 +1,19 @@

1+++

2−title = "Guide to Breaches"

2+title = "Guide to Factory Resets"

3weight = 40

4template = "doc.html"

5+++

6

7−An important concept on the [Ames](/docs/arvo/ames/ames) 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.

7+An important concept on the [Ames](/docs/arvo/ames/ames) network is that of

8+continuity. Continuity refers to how ships remember the order of their own

9+network messages and the network messages of others -- these messages are

10+numbered, starting from zero. A _factory reset_ is when ships on the network agree to

11+forget about this sequence and treat one or more ships like they are brand new.

8

12

9−There are two kinds of breaches: (personal) **breaches** and **network breaches**.

13+## Factory Resets

10

14

11−## Breaches

12−

13−Ships on the Ames network sometimes need to reset their continuity. A breach is

15+Ships on the Ames network sometimes need to reset their continuity. A factory

16+reset (hereafter just called a _reset_) is

14when an individual ship announces to the network: "I forgot who I am, let's

17when an individual ship announces to the network: "I forgot who I am, let's

15start over from scratch." That is, it clears its own event log and sends an

18start over from scratch." That is, it clears its own event log and sends an

16announcement to the network, asking all ships that have communicated with it to

19announcement to the network, asking all ships that have communicated with it to

@@ -18,36 +21,40 @@ reset its networking information in their state. This makes it as though the

18ship was just started for the first time again, since everyone on the network

21ship was just started for the first time again, since everyone on the network

19has forgotten about it.

22has forgotten about it.

20

23

21−Breaches often fix connectivity issues, but should only be used as a last

24+Resets often fix connectivity issues, but should only be used as a last

22−resort. Before performing a breach, look at alternative fixes in the [Ship

25+resort. Before performing a reset, look at alternative fixes in the [Ship

23−Troubleshooting](/using/os/ship-troubleshooting) guide. Also reach out for help in the

26+Troubleshooting](/using/os/ship-troubleshooting) guide. Also reach out for help

27+in the Help channel in the Urbit Community group

24−Help channel in the Urbit Community group `~bitbet-bolbel/urbit-community` to see if there is another option.

28+`~bitbet-bolbel/urbit-community` to see if there is another option. Connectivity

25−Connectivity issues are typically related to a bug, and you may be able to help

29+issues are typically related to a bug, and you may be able to help us fix it by

26−us fix it by emailing us at `support@urbit.org`.

30+emailing us at `support@urbit.org`.

27

31

28−There are two separate sequences of actions you need to take in order to breach.

32+There are two separate sequences of actions you need to take in order to reset.

29One flow is for when you wish to keep Ethereum ownership address of the ship the

33One flow is for when you wish to keep Ethereum ownership address of the ship the

30same, and the other is for when you are transferring the ship to a new Ethereum

34same, and the other is for when you are transferring the ship to a new Ethereum

31ownership address. We make the emphasis about the Ethereum _ownership_ address

35ownership address. We make the emphasis about the Ethereum _ownership_ address

32−as changing your [proxies](/docs/glossary/proxies) does not require a

36+as changing your [proxies](/docs/glossary/proxies) does not require a reset.

33−breach.

34

37

35If you will be keeping your ship at the same Ethereum ownership address and

38If you will be keeping your ship at the same Ethereum ownership address and

36−would like to perform a breach, follow the steps below.

39+would like to perform a reset, follow the steps below.

37

40

38- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.

41- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.

39−- Click on `OS: Urbit OS Settings` at the bottom, then click `Reset Networking Keys`.

42+- Click on `OS: Urbit OS Settings` at the bottom, then click `Reset Networking

43+ Keys`.

40−- Check the `Breach Continuity` box. Click `Reset Networking Keys`, and then click `Send Transaction` and wait for the progress bar to appear.

44+- Check the `Breach Continuity` box. Click `Reset Networking Keys`, and then

45+ click `Send Transaction` and wait for the progress bar to appear.

41- Download your new keyfile following these instructions: [Generate your

46- Download your new keyfile following these instructions: [Generate your

42 keyfile](/using/id/using-bridge#generate-your-keyfile).

47 keyfile](/using/id/using-bridge#generate-your-keyfile).

43- Delete or archive your old [pier](/docs/glossary/pier).

48- Delete or archive your old [pier](/docs/glossary/pier).

44−- Proceed to [boot your ship](/getting-started/cli#boot-your-planet) with the new keyfile.

49+- Proceed to [boot your ship](/getting-started/cli#boot-your-planet) with the

50+ new keyfile.

45- Delete your keyfile after successfully booting.

51- Delete your keyfile after successfully booting.

46- Rejoin your favorite chat channels and subscriptions.

52- Rejoin your favorite chat channels and subscriptions.

47

53

48−If you are transferring a ship to a new Ethereum ownership address you will have the

54+If you are transferring a ship to a new Ethereum ownership address you will have

49−choice as to whether or not you want to breach. This is to cover the case when

55+the choice as to whether or not you want to reset. This is to cover the case

50−you are transferring to another address you own. The process here is slightly different.

56+when you are transferring to another address you own. The process here is

57+slightly different.

51

58

52- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.

59- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.

53- Click on `ID: Identity and security settings` at the bottom, then click

60- Click on `ID: Identity and security settings` at the bottom, then click

@@ -58,25 +65,30 @@ you are transferring to another address you own. The process here is slightly di

58- Logout of your current session in Bridge by clicking `Logout` at the top, and

65- Logout of your current session in Bridge by clicking `Logout` at the top, and

59 then login to your new ownership address.

66 then login to your new ownership address.

60- From here, following the directions on how to [Accept your

67- From here, following the directions on how to [Accept your

61− transfer](/using/id/using-bridge#accept-your-transfer), [Set your

68+ transfer](/using/id/using-bridge#accept-your-transfer), [Set your networking

62− networking keys](/using/id/using-bridge#set-your-networking-keys),

69+ keys](/using/id/using-bridge#set-your-networking-keys), and [Generate your

63− and [Generate your

64− keyfile](/using/id/using-bridge#generate-your-keyfile). The option

70+ keyfile](/using/id/using-bridge#generate-your-keyfile). The option whether or

65− whether or not to breach is in the Accept your Transfer step.

71+ not to reset is in the Accept your Transfer step.

66- Delete or archive your old [pier](/docs/glossary/pier).

72- Delete or archive your old [pier](/docs/glossary/pier).

67−- Proceed to [boot your ship](/getting-started/cli#boot-your-planet) with the new keyfile.

73+- Proceed to [boot your ship](/getting-started/cli#boot-your-planet) with the

74+ new keyfile.

68- Delete your keyfile after successfully booting.

75- Delete your keyfile after successfully booting.

69- Rejoin your favorite chat channels and subscriptions.

76- Rejoin your favorite chat channels and subscriptions.

70

77

71−## Network Breaches

78+## Network Resets

72

79

73−Network breaches were events where all ships on the network were required to

80+Network resets were events where all ships on the network were required to

74−update to a new continuity era. Network breaches happened when an Arvo update

81+update to a new continuity era. Network resets happened when an Arvo update

75was released that could not be implemented via an [OTA

82was released that could not be implemented via an [OTA

76−update](/docs/glossary/ota-updates). The continuity era is given by an

83+update](/docs/glossary/ota-updates). The continuity era is given by an integer

77−integer in Ames that is incremented when the network breaches. Only ships with

84+in Ames that is incremented when the network resets. Only ships with the same

78−the same such value are able to communicate with one another. The most recent

85+such value are able to communicate with one another. The most recent network

79−network breach occurred in December 2020, and we expect it to have been the final one.

86+reset occurred in December 2020, and we expect it to have been the final one.

80

87

81−If another network breach does occur, we will provide accompanying documentation

88+If another network reset does occur, we will provide accompanying documentation

82on what to do to transfer your ship and all of its data to the new era.

89on what to do to transfer your ship and all of its data to the new era.

90+

91+## Breaches

92+

93+Factory resets used to be called _breaches_, and you may find this terminology

94+still used in some places. This is an identical concept - only the name differs.

content/using/id/proxies.md+1−1

@@ -25,7 +25,7 @@ address to be the management proxy.

25- **Management proxy**

26

27 Can configure or set Arvo networking keys,

28− [breach](/docs/using/id/guide-to-breaches), and conduct sponsorship related

28+ [factory reset](/docs/using/id/guide-to-resets), and conduct sponsorship related

29 operations. Planets, stars, and galaxies may all set a management proxy.

30

31- **Spawn proxy**

content/using/id/using-bridge.md+2−2

@@ -44,9 +44,9 @@ After you access your Ethereum address, if a point was sent to that address, you

44

45Now you'll be on the management page of your point. The transfer isn't completed

46yet, so click `Accept incoming transfer`. If you are transferring to yourself

47−and do not wish to [breach](/docs/glossary/breach), check the box labeled

47+and do not wish to [factory reset](/docs/glossary/resets), check the box labeled

48`Retain proxies and key configuration, in case of transferring to self`.

49−Otherwise leave the box unchecked, ensuring that your ship will be breached upon

49+Otherwise leave the box unchecked, ensuring that your ship will be factory reset upon

50transfer and thus no Azimuth data from the previous owner (namely proxies and

51networking keys) will be retained. Then press the `Generate and Sign

52Transaction` button, followed by the `Send Transaction` button.

content/using/os/basics.md+2−2

@@ -164,13 +164,13 @@ $ ./urbit -w <moon-name> -k <key-file> -c <pier-name>

164

165Note the `<moon-name>` excludes the leading `~`. The `-c <piername>` argument is not required, but it is recommended; otherwise, the resulting directory is a rather unwieldy moon name. Moons are automatically synced to their parent `%kids` desk, and can control applications on their parent planet using `|link`.

166

167−To breach a moon -- that is, to reset its presence on the network so that it's treated as a freshly spawned ship by others -- run from the parent ship:

167+To factory reset a moon -- that is, to reset its presence on the network so that it's treated as a freshly spawned ship by others -- run from the parent ship:

168

169```

170|moon-breach ~faswep-navred-sampel-palnet

171```

172

173−To cycle the keys of a moon without breaching, run:

173+To cycle the keys of a moon without a factory reset, run:

174

175```

176|moon-cycle-keys ~faswep-navred-sampel-palnet

content/using/os/ship-troubleshooting.md+24−12

@@ -26,11 +26,15 @@ An ounce of prevention is worth a pound of cure, so let's first go over some bes

26

27Once your ship has been initialized (with the `-w` variation of the `./urbit` command), you should never do so a second time. If you do initialize it anew without special measures, you will experience trouble communicating with ships on the network you had talked to before.

28

29−If you accidentally did this a second time, or want to intentionally start fresh, you need to perform a [personal breach](#personal-breach), which is explained in the next section.

29+If you accidentally did this a second time, or want to intentionally start

30+fresh, you need to perform a [factory reset](#factory-reset), which is explained in the next section.

30

31

31### Do not delete your pier

32### Do not delete your pier

32

33

33−Urbit is stateful, meaning that it needs to hold onto all your data. If you delete your pier and start your ship again, you won't be able to talk to any ship you've talked to before. The only solution to this is performing a [personal breach](#personal-breach).

34+Urbit is stateful, meaning that it needs to hold onto all your data. If you

35+delete your pier and start your ship again, you won't be able to talk to any

36+ship you've talked to before. The only solution to this is performing a [factory

37+reset](#factory-reset).

34

38

35### Keep track of the directory that you put your ship in

39### Keep track of the directory that you put your ship in

36

40

@@ -64,13 +68,13 @@ The command takes two arguments, and comes in the form of `|knob %error-tag %lev

64

68

65So for example, to silence all Ames packet-related errors, try `|knob %hole %hush`.

69So for example, to silence all Ames packet-related errors, try `|knob %hole %hush`.

66

70

67−### Perform a personal breach. {#personal-breach}

71+### Perform a factory reset. {#factory-reset}

68

72

69−A personal breach is when a ship tells the rest of the network to treat it as though the ship was just started for the first time again. Any ongoing or outstanding communication is forgotten and connections are reestablished from scratch.

73+A factory reset is when a ship tells the rest of the network to treat it as though the ship was just started for the first time again. Any ongoing or outstanding communication is forgotten and connections are reestablished from scratch.

70

74

71−Personal breaches often fix connectivity issues, but should only be used as a

75+Factory resets often fix connectivity issues, but should only be used as a

72−last resort. To find out how to perform a personal breach, check out our [Guide

76+last resort. To find out how to perform a factory reset, check out our [Guide

73−to Breaches](/using/id/guide-to-breaches). Before taking such a drastic measure, try

77+to Factory Resets](/using/id/guide-to-resets). Before taking such a drastic measure, try

74other methods in this guide. You can also ask for help on

78other methods in this guide. You can also ask for help on

75in the Help channel in the Urbit Community group at `~bitbet-bolbel/urbit-community`.

79in the Help channel in the Urbit Community group at `~bitbet-bolbel/urbit-community`.

76

80

@@ -104,7 +108,8 @@ Since version `0.8.0`, changes no longer automatically sync between the Unix sid

104

108

105### I can't communicate with anyone

109### I can't communicate with anyone

106

110

107−Maybe you booted your ship twice, or ran it using old files. If this is the case, you must perform a [personal breach](#personal-breach).

111+Maybe you booted your ship twice, or ran it using old files. If this is the

112+case, you must perform a [factory reset](#factory-reset).

108

113

109### I don't have the latest OTA

114### I don't have the latest OTA

110

115

@@ -119,7 +124,10 @@ own with patience. Otherwise, try the procedure outlined [here](https://github.c

119

124

120You may see a message like this one: `/~zod/home/~2019.7.22..18.55.46..83a3/sys/vane/ames:<[line column].[line column]>`. This is a clay path to a Hoon file, pointing to the line and column where an expression crashed. This kind of error might be accompanied by a `crud` message.

125You may see a message like this one: `/~zod/home/~2019.7.22..18.55.46..83a3/sys/vane/ames:<[line column].[line column]>`. This is a clay path to a Hoon file, pointing to the line and column where an expression crashed. This kind of error might be accompanied by a `crud` message.

121

126

127+This means that another ship is sending invalid packets to you. This could be

128+because one of the ships has not updated the other ship's "rift number", which

122−This means that another ship is sending invalid packets to you. This could be because one of the ships has not updated the other ship's "life number", which is the number that starts at one and increments every time that ship performs a personal breach.

129+is the number that starts at one and increments every time that ship performs a

130+factory reset.

123

131

124This can happen if they have the wrong keys of yours, or if you have the wrong keys of theirs. You can figure out who has the wrong keys by running this scry command in your dojo: `.^(* %j /=life=/shipname)`, where shipname is the other ship's name. Save that information. Then, go to the [Azimuth contract on Etherscan](https://etherscan.io/address/0x223c067f8cf28ae173ee5cafea60ca44c335fecb#readContract), scroll down to `32. points`, and put in the hexadecimal representation of the other ship's `@p`. You can find the hexadecimal representation by running ...

132This can happen if they have the wrong keys of yours, or if you have the wrong keys of theirs. You can figure out who has the wrong keys by running this scry command in your dojo: `.^(* %j /=life=/shipname)`, where shipname is the other ship's name. Save that information. Then, go to the [Azimuth contract on Etherscan](https://etherscan.io/address/0x223c067f8cf28ae173ee5cafea60ca44c335fecb#readContract), scroll down to `32. points`, and put in the hexadecimal representation of the other ship's `@p`. You can find the hexadecimal representation by running ...

125

133

@@ -145,7 +153,8 @@ The above commands work if you have the wrong keys of other ships. If other ship

145

153

146### I can talk to some ships, but I can't talk to my sponsor and some other ships

154### I can talk to some ships, but I can't talk to my sponsor and some other ships

147

155

148−This is the result of deleting your pier and starting your ship again. To fix this, you must perform a [personal breach](#personal-breach).

156+This is usually the result of deleting your pier and starting your ship again. To fix

157+this, you must perform a [factory reset](#factory-reset).

149

158

150## Booting Issues {#booting-issues}

159## Booting Issues {#booting-issues}

151

160

@@ -163,7 +172,10 @@ This means that you gave your development ship an invalid `@p`. So, you will get

163

172

164Try bringing it back up; it will often start working just fine again.

173Try bringing it back up; it will often start working just fine again.

165

174

175+However, if you get a `bail` error again, this is a serious issue and should be

176+reported (see below). It's advised to keep the old files around to assist issue

166−However, if you get a `bail` error again, this is a serious issue and should be reported (see below). It's advised to keep the old files around to assist issue research. If you want to get back on the network immediately, you might want to perform a [personal breach](#personal-breach).

177+research. If you want to get back on the network immediately, you might want to

178+perform a [factory reset](#factory-reset).

167

179

168#### Making a GitHub issue out of your `bail`

180#### Making a GitHub issue out of your `bail`

169

181

@@ -200,7 +212,7 @@ This means that your ship ran out of memory.

200

212

2014. If the above succeeds, but you still get `bail: meme` immediately, or after running for a little while, please [file an issue](https://github.com/urbit/urbit/issues). If you can, run `|mass` and share its output.

2134. If the above succeeds, but you still get `bail: meme` immediately, or after running for a little while, please [file an issue](https://github.com/urbit/urbit/issues). If you can, run `|mass` and share its output.

202

214

203−5. As a last resort, you may perform a [personal breach](#personal-breach).

215+5. As a last resort, you may perform a [factory reset](#factory-reset).

204

216

205### My ship crashed with a `bail: oops` error

217### My ship crashed with a `bail: oops` error

206

218

content/using/os/stars-and-galaxies.md−8

@@ -25,14 +25,6 @@ You can distribute planets from your star via [Bridge](https://bridge.urbit.org/

25

26By default, your star accepts software updates from its galaxy and routes them to its planets. You can use this mechanism to push custom software to your planets. Keep in mind that planets expect functional, non-breaking software updates, and generally want to be able to communicate with planets that are sponsored by other stars.

27

28−#### Breaches

29−

30−To ensure new planets can connect to your ship, users are expected to participate in network-wide breaches by [updating to the latest Urbit version](/getting-started/), deleting (or archiving) your pier, and then booting your ship using the new binary. If you don’t participate, you won’t be able to communicate with anyone on the network who has updated to the new era.

31−

32−Network-wide breaches are distinct from personal breaches, wherein an individual ship cycles its personal network keys using Bridge, and then follows the same steps outlined above.

33−

34−See our [Guide to Breaches](https://urbit.org/docs/tutorials/guide-to-breaches) for more information and for instructions on breaching.

35−

36### Star-owner etiquette

28### Star-owner etiquette

37

29

38- If you distribute planets, boot and run your star on the Arvo network, or the

30- If you distribute planets, boot and run your star on the Arvo network, or the

content/using/running/hosting.md+4−1

@@ -104,7 +104,10 @@ Continuing to follow the DO docs we're going to configure the ufw firewall.

104

105## Installing Urbit

106Finally we're ready to install Urbit on your very own server. This part is actually pretty easy, if you haven't installed Urbit locally then the instructions are the exact same as the ones in the Urbit [install doc](/getting-started/). If you have a local ship already, we're going to install Urbit on the server and then send your local ship up.

107+ - **WARNING**: Since Urbit is p2p you don't want to ever run two copies of your

108+ ship simultaneously. This is because other nodes that interact with each of

109+ your copies will be confused by which one is the most up to date. If you end

107− - **WARN**: Since Urbit is p2p you don't want to ever run two copies of your ship simultaneously. This is because other nodes that interact with each of your copies will be confused by which one is the most up to date. If you end up accidentally doing this you'll have to do a 'personal breach' described in the [guide to breaches](/using/id/guide-to-breaches) to fix things.

110+ up accidentally doing this you'll have to do a 'factory reset' described in the [guide to resets](/using/id/guide-to-resets) to fix things.

108 - The first thing you're going to want to do is shut down your local ship, either with control-d or `|exit` in dojo.

111 - The first thing you're going to want to do is shut down your local ship, either with control-d or `|exit` in dojo.

109 - Next we're going to install Urbit on the server and permit it to bind to the web ports:

112 - Next we're going to install Urbit on the server and permit it to bind to the web ports:

110 ```

113 ```

content/using/running/port.md+2−2

@@ -41,7 +41,7 @@ home screen and ready to explore Urbit.

41## Boot another ship

42

43**Important: This is for booting a ship for the first time, or for booting a

44−ship which has just undergone a [breach](/docs/glossary/breach). A ship should

44+ship which has just undergone a [factory reset](/docs/glossary/resets). A ship should

45only be booted from its keyfile in its current

46[rift](/docs/azimuth/life-and-rift#rift) once. If your ship has already been

47booted elsewhere, see the [Import pier](#import-pier) section instead.**

@@ -148,7 +148,7 @@ see the [Import pier](#import-pier) section for details of importing it.

148

149**Warning: Deleting a pier is irreversible, and all data will be lost. If the

150ship is a comet, the comet name will be unusable again. If the ship is a planet

151−or star, you will need to perform a [breach](/docs/glossary/breach) via Bridge

151+or star, you will need to perform a [factory reset](/docs/glossary/reset) via Bridge

152to be able to use it again (and all of its data will still be lost).**

153

154To completely delete the pier of a ship managed by Port, go to the home screen

vercel.json+2−2

@@ -149,8 +149,8 @@

149 "permanent": true

150 },

151 {

152− "source": "/docs/tutorials/guide-to-breaches/",

152+ "source": "/docs/tutorials/guide-to-resets/",

153− "destination": "/using/id/guide-to-breaches",

153+ "destination": "/using/id/guide-to-resets",

154 "permanent": true

155 },

156 {