aboutsummaryrefslogtreecommitdiff
path: root/doc/manual/src
diff options
context:
space:
mode:
authorTravis A. Everett <travis.a.everett@gmail.com>2022-06-16 09:47:15 -0500
committerTravis A. Everett <travis.a.everett@gmail.com>2022-06-30 13:31:04 -0500
commit649c9d9b4c0b2327b11c44cda7b5738efa245c08 (patch)
tree51ca0fe20db024ca3ac8bac87a4cd096aca1fde1 /doc/manual/src
parentfe76b9f4b461c6a25f49a80a2476b7d60537c455 (diff)
doc: acknowledge post-rsync reality
Before #5150 the copy-to-store phase of the install was idempotent, but the recursive cp isn't. This is probably baiting a few people into trying corrective installs that will fail.
Diffstat (limited to 'doc/manual/src')
-rw-r--r--doc/manual/src/installation/installing-binary.md13
1 files changed, 7 insertions, 6 deletions
diff --git a/doc/manual/src/installation/installing-binary.md b/doc/manual/src/installation/installing-binary.md
index 762402948..a2f284d5a 100644
--- a/doc/manual/src/installation/installing-binary.md
+++ b/doc/manual/src/installation/installing-binary.md
@@ -176,15 +176,17 @@ and `/etc/zshrc` which you may remove.
This will remove the Nix Store volume and everything that was added to the
store.
- If this command indicates that it couldn't remove the volume, your Nix Store
- volume may not be mounted. Run the following to double-check:
+ If this command indicates that it couldn't remove the volume, you should
+ make sure you don't have an _unmounted_ Nix Store volume. Look for a
+ "Nix Store" volume in the output of the following command:
```console
diskutil list
```
- If you see a Nix Store volume, re-run the diskutil deleteVolume command, but
- replace `/nix` with the volume's `diskXsY` identifier.
+ If you _do_ see a "Nix Store" volume, delete it by re-running the diskutil
+ deleteVolume command, but replace `/nix` with the store volume's `diskXsY`
+ identifier.
> **Note**
>
@@ -202,8 +204,7 @@ and `/etc/zshrc` which you may remove.
<!-- Note: anchors above to catch permalinks to old explanations -->
We believe we have ironed out how to cleanly support the read-only root
-on modern macOS. New installs will do this automatically, and you can
-also re-run a new installer to convert your existing setup.
+on modern macOS. New installs will do this automatically.
This section previously detailed the situation, options, and trade-offs,
but it now only outlines what the installer does. You don't need to know