shithub: docs.9front.org

Download patch

ref: 5c4bf075ba601ba27d0558546b7ce5b2aa52f5d9
parent: b9b2ce4592015b0dc049661059ed2af4a9696f54
author: kvik <[email protected]>
date: Fri Aug 14 14:21:31 EDT 2020

cpu-setup: fix list numbering

--- a/cpu-setup.md
+++ b/cpu-setup.md
@@ -1,6 +1,6 @@
 # Setting up a networked 9front machine
 
-0. First off, we'll make our life bearable by setting up a
+1. First off, we'll make our life bearable by setting up a
    temporary cpu service listener. This will let us access the
    new system with `rcpu(1)` or `drawterm(1)`, instead of having
    to suffer some terrible VNC console or similar.
@@ -10,13 +10,13 @@
 	echo 'key proto=dp9ik dom=9front user='$user' !password=BADBADDIE' >/mnt/factotum/ctl
 	aux/listen1 -t 'tcp!*!rcpu' /rc/bin/service/tcp17019
 
-1. Complete the standard installation using inst/start, then reboot
+2. Complete the standard installation using inst/start, then reboot
    into a newly installed system.
 
    The following steps assume the cwfs(4) was selected as the
    file server, and that the basic networking works.
 
-2. Start with adding your own user to the file server, also add
+3. Start with adding your own user to the file server, also add
    it to some standard groups:
 
 	; con -C /srv/cwfs.cmd
@@ -32,7 +32,7 @@
 
    This will set up your home directory.
 
-3. Setting up the FS listener
+4. Setting up the FS listener
 
    This step is OPTIONAL.  If you don't plan to set up
    TCP/TLS or PXE booting it is fine to skip it for now.
@@ -73,7 +73,7 @@
 	noauth
 	auth enabled
 
-4. Setting up the CPU listener
+5. Setting up the CPU listener
 
    For CPU listener to get started at boot time it is enough to set
    the `service=` parameter in `plan9.ini`:
@@ -80,7 +80,7 @@
 
 	service=cpu
 
-5. Setting up hands-free booting
+6. Setting up hands-free booting
 
    In step 3. we've set up the `nobootprompt=` parameter, which makes
    sure the root file system is mounted automatically at boot.  
@@ -114,7 +114,7 @@
 	secstore key: <press enter to skip>
 	password: <type your password>
 
-6. Setting up the AUTH server
+7. Setting up the AUTH server
 
    We are almost done and ready to reboot, but almost nothing set
    up above will work before an authentication server is running.
@@ -171,7 +171,7 @@
 	hostid=kvik
 		uid=!sys uid=!adm uid=*
 
-7. Reboot
+8. Reboot
 
 	fshalt -r