shithub: wiki.9front.org

Download patch

ref: 4290924ef68d8fedc589ad4031727960b68846d6
parent: 5c4bf075ba601ba27d0558546b7ce5b2aa52f5d9
author: kvik <kvik@a-b.xyz>
date: Fri Aug 14 14:24:42 EDT 2020

cpu-setup: fix step references

--- a/cpu-setup.md
+++ b/cpu-setup.md
@@ -42,7 +42,7 @@
    through the `plan9.ini`.
 
    First we'll need to mount the `9fat` partition. If you aren't doing
-   this from the console, i.e. you've done step 0., then you'll have
+   this from the console, i.e. you've done step 1., then you'll have
    to make sure you are mounting and modifying the target machine's
    `plan9.ini`, and not the one belonging to your terminal.  We can do
    this by binding correct devices and being explicit with the `9fs`
@@ -82,7 +82,7 @@
 
 6. Setting up hands-free booting
 
-   In step 3. we've set up the `nobootprompt=` parameter, which makes
+   In step 4. we've set up the `nobootprompt=` parameter, which makes
    sure the root file system is mounted automatically at boot.  
    In this step we'll set up hostowner credentials, the user name and
    password, so as to avoid the need for manual intervention on the
@@ -99,7 +99,7 @@
    be asked for later when creating an auth user and configuring the
    authentication server.
 
-   **NOTE 2** If you have followed the step 0. then it is best to
+   **NOTE 2** If you have followed the step 1. then it is best to
    explicitly specify the `nvram` partition that you want to write to.
    On PC some automatic process is used to find a suitable partition.
    It is very likely that this process will guess wrong.  Use the