ref: 66046e63c1e3e7e370787a2695b8672788fac891
parent: 166cfad04f0d4754ca7143700bb428640b33ce38
author: sl <sl@9front>
date: Thu Jul 6 21:50:56 EDT 2023
*.ms: update for DON'T TOUCH THE ARTWORK release
--- a/appendixz.ms
+++ b/appendixz.ms
@@ -54,6 +54,8 @@
http://n-gate.com
.ihtml a
+Finally: Turn off your machine and get a life.
+
.html - <hr />
.html - <a href="fqa.html">FQA INDEX</a> |
.html - <a href="appendixj.html">FQA Appendix L - Languages</a>
--- a/fqa.ms
+++ b/fqa.ms
@@ -1191,6 +1191,10 @@
8.2.6 - Keyboard Shortcuts
.ihtml a
+.ihtml a <a href="fqa8.html#8.2.6.1">
+8.2.6.1 - No, really, keyboard shortcuts
+.ihtml a
+
.ihtml a <a href="fqa8.html#8.2.7">
8.2.7 - Color scheme
.ihtml a
--- a/fqa3.ms
+++ b/fqa3.ms
@@ -821,7 +821,9 @@
.B
Note:
.R
-Some WiFi hardware requires a corresponding firmware blob to exist under `/lib/firmware/`. Contents of this directory get included into the kernel paqfs when the kernel is rebuilt, so make sure you don't have so much firmware in there that your kernel gets too large for your machine to boot. This, of course, varies from machine to machine.
+Some WiFi hardware requires a corresponding firmware blob to exist under
+.CW /lib/firmware/.
+Contents of this directory get included into the kernel paqfs when the kernel is rebuilt, so make sure you don't have so much firmware in there that your kernel gets too large for your machine to boot. This, of course, varies from machine to machine.
Read:
.ihtml a <a href="http://man.9front.org/8/wpa">
@@ -831,7 +833,7 @@
.ihtml a <a href="http://man.9front.org/8/plan9.ini">
.CW plan9.ini (8)
.ihtml a
-
+.bp
.html - <a name="3.2.3.2.1" />
.ihtml h5 <h5>
.SH
@@ -927,18 +929,29 @@
.ihtml a <a href="http://firmware.openbsd.org/firmware/">
http://firmware.openbsd.org/firmware/*/iwn-firmware*.tgz
.ihtml a
-to be present on attach in `/lib/firmware` or `/boot.`
-To limit the selected APs the options `essid=` and
-`bssid=` may be set at boot or in the ether interface
+to be present on attach in
+.CW /lib/firmware
+or
+.CW /boot.
+To limit the selected APs the options
+.CW essid=
+and
+.CW bssid=
+may be set at boot or in the ether interface
clone file using a space as the separator between
option and value, e.g.
-`echo essid left-armpit >/net/ether1/clone`
+.CW
+echo essid left-armpit >/net/ether1/clone
+.R
Scan results appear in the ifstats file and can be
read out like:
-`cat /net/ether1/ifstats`
+.CW
+cat /net/ether1/ifstats
+.R
Ad-hoc mode or WEP encryption is currently not suppported.
-Example configuration for `plan9.ini`:
+Example configuration for
+.CW plan9.ini:
.P1
ether0=type=iwl\ essid=YOUR_AP
wpapsk=PASSWORD
@@ -1094,10 +1107,16 @@
.ihtml a <a href="http://firmware.openbsd.org/firmware/">
http://firmware.openbsd.org/firmware/*/wpi-firmware*.tgz
.ihtml a
-to be present on attach in `/lib/firmware` or `/boot.`
-See `iwl` section above for configuration details.
+to be present on attach in
+.CW /lib/firmware
+or
+.CW /boot.
+See the
+.CW iwl
+section above for configuration details.
-Example configuration for `plan9.ini`:
+Example configuration for
+.CW plan9.ini:
.P1
ether0=type=wpi\ essid=YOUR_AP
wpapsk=PASSWORD
@@ -1126,8 +1145,12 @@
.ihtml a <a href="http://firmware.openbsd.org/firmware/">
http://firmware.openbsd.org/firmware/*/ral-firmware*.tgz
.ihtml a
-to be present on attach in `/lib/firmware` or `/boot.`
-See `iwl` section above for configuration details.
+to be present on attach in
+.CW /lib/firmware
+or
+.CW /boot.
+See the
+.CW iwl section above for configuration details.
.SH
Ralink RT3090
@@ -1270,6 +1293,12 @@
Treated as a mouse.
+.SH
+Wacom (from ThinkPad X1 Yoga 3rd Gen, model unknown)
+.R
+
+Treated as a mouse.
+
.html - <a name="3.2.4.2.2" />
.ihtml h5 <h5>
.SH
@@ -1292,7 +1321,7 @@
.html - <br />
.FG rugged png
-The ever-expanding list of supported desktop and laptop systems has been redacted from this book and moved exclusivly online.
+The ever\-expanding list of supported desktop and laptop systems has been redacted from this book and moved exclusivly online.
Access it here:
.ihtml a <a href="http://plan9.stanleylieber.com/hardware/">
.CW
@@ -1299,7 +1328,7 @@
http://plan9.stanleylieber.com/hardware/
.R
.ihtml a
-
+.bp
.FG desktops png
.html - <a name="3.3" />
@@ -1451,9 +1480,6 @@
.B Note:
Read over this first. Be careful not to clobber any system settings you may already have configured. If you don't understand something, read the relevant man pages until you do. Feel free to substitute arbitrary network values below.
-
-[Continued on next page]
-
.P1
# as root
pkg_add bzip2 plan9port qemu ssvnc wget
@@ -1501,6 +1527,7 @@
\.
w
q
+
rcctl enable unbound
rcctl start unbound
echo \'permit setenv { -ENV PS1=$DOAS_PS1 SSH_AUTH_SOCK } :wheel\' \e@@ -1510,6 +1537,8 @@
mkdir -p $HOME/9 $HOME/bin
cd $HOME/9
qemu-img -f qcow2 9front.qcow2.img 30G
+.P2
+.P1
# adjust url for current iso
wget http://9front.org/iso/9front-5561.df1dc1ff2475.iso.bz2
bunzip2 9front-5561.df1dc1ff2475.iso.bz2
--- a/fqa4.ms
+++ b/fqa4.ms
@@ -660,6 +660,7 @@
4.3.6.1 - cwfs no-dump configuration
.R
.ihtml h3
+
A cheap VPS or an SD card lack the storage capacity for running a usable
default
.ihtml a <a href="http://man.9front.org/4/cwfs">
@@ -678,25 +679,37 @@
use a dedicated WORM partition and doesn't do daily dumps by default.
However, it has several performance problems and is not as well tested.
-The `cwfs` file system can be configured in lots of ways beyond the
+The
+.CW cwfs
+file system can be configured in lots of ways beyond the
default cache-worm + other configuration supported by the 9front
installer.
-The desired configuration we're going to cover is a single `main`
+The desired configuration we're going to cover is a single
+.CW main
file server tree backed by a simple disk file system - the same type
-used by the `other` tree in the default setup.
+used by the
+.CW other
+tree in the default setup.
To do this we're going to partition the disk appropriately and override
-the `mountcwfs` stage of the 9front installer with a replacement script
+the
+.CW mountcwfs
+stage of the 9front installer with a replacement script
.ihtml a <a href="http://plan9.stanleylieber.com/rc/mountcwfs">
http://plan9.stanleylieber.com/rc/mountcwfs
.ihtml a
-that will configure `cwfs`
+that will configure
+.CW cwfs
appropriately. The rest of the installation and most of the
subsequent system operation remain unaffected.
Start by booting from the installation media. Configure networking
-with `ip/ipconfig(8)` and fetch the replacement `mountcwfs` script,
+with
+.CW ip/ipconfig(8)
+and fetch the replacement
+.CW mountcwfs
+script,
or put the script on a flash drive:
.P1
% webfs
@@ -704,13 +717,24 @@
% hget http://plan9.stanleylieber.com/rc/mountcwfs >/tmp/mountcwfs
% chmod +x /tmp/mountcwfs
.P2
-Override the `mountcwfs` stage using `bind(1)`:
+Override the
+.CW mountcwfs
+stage using
+.CW bind(1):
.P1
bind /tmp/mountcwfs /bin/inst/mountcwfs
.P2
-Run `inst/start` and complete the stages up to `preppart` as you would
-normally. At `preppart`, delete the default partitions and create one
-named `fsmain` with a desired size:
+Run
+.CW inst/start
+and complete the stages up to
+.CW preppart
+as you would
+normally. At
+.CW preppart,
+delete the default partitions and create one
+named
+.CW fsmain
+with a desired size:
.P1
d other
d fscache
@@ -783,11 +807,16 @@
Plan 9 partition to subdivide (/dev/sdC0/plan9)[/dev/sdC0/plan9]:
.P2
-Use the Plan 9 partition created in the previous step. Hit `enter` to select the default.
+Use the Plan 9 partition created in the previous step. Hit
+.CW enter
+to select the default.
.P1
This is disk/prep; use it to subdivide the Plan 9 partition.
If it is not yet subdivided, a sensible layout will be suggested;
-you can probably just type 'w' and then 'q'.
+you can probably just type
+.CW w
+and then
+.CW q.
no plan9 partition table found
9fat 204800
@@ -872,7 +901,9 @@
We are installing from local media, so,
.CW local .
-Hit `enter` to accept the default.
+Hit
+.CW enter
+to accept the default.
.B Note:
The
@@ -879,6 +910,8 @@
.CW net
option attempts to download the ISO from the Internet and install it directly to disk. Since the installer is most likely already running from an ISO image, this option may prove to be of limited utility. The option is somewhat experimental, and may work. Attempt it at your own risk.
+[Continued on next page]
+.bp
.html - <a name="4.3.11" />
.ihtml h3 <h3>
.SH
@@ -1003,8 +1036,6 @@
processing /sys/lib/sysconfig/proto/allproto
.P2
-.FG bar gif
-
.B ACHTUNG!
Currently, there is no progress meter. For systems without DMA, the
.CW copydist
@@ -1014,8 +1045,6 @@
.ihtml a
window.
-.FG bar gif
-
Eventually, you should see the following:
.P1
file system made
@@ -1131,8 +1160,6 @@
Congratulations, you've just installed a 9front system!
-[Continued on next page]
-.bp
Now your cat goes to sleep on the keyboard.
.FG cinapcatdrawing png
--- a/fqa8.ms
+++ b/fqa8.ms
@@ -432,6 +432,35 @@
.CW shift
and pressing the up or down arrow.
+.html - <a name="8.2.6.1" />
+.ihtml h3 <h3>
+.B
+8.2.6.1 - No, really, keyboard shortcuts
+.R
+.ihtml h3
+
+Part of 9front's bold initiative for modernizing Plan 9's interface (demo day!) while still retaining all of the bits that really annoy people is to implement a keyboard\-controller overlay that provides configurable keyboard shortcuts without actually altering
+.CW rio
+itself, representing a negotiated ceasefire somewhere on the spectrum between touching the artwork, Joker\-style, and creating a brand new GUI from scratch. One of the features provided by
+.CW riow
+is virtual desktops + the ability to navigate through them using only the keyboard, which, to my mind, goes some way towards satisfying the bounty for a
+.CW dwm/i3/sway
+-like
+.CW rio
+replacement.
+
+Read:
+.ihtml a <a href="http://9front.org/1/riow">
+.CW
+rio(1),
+.R
+.ihtml a
+.I
+Appendix B: Bounties
+.R
+
+[Continued on next page]
+.bp
.html - <a name="8.2.7" />
.ihtml h3 <h3>
.SH
@@ -444,15 +473,17 @@
.FG rio-bell-labs png
-[Continued on next page]
-.bp
\f(CWrio\fR's color scheme may be modified by editing the .c configuration files and re-compiling:
.FG rio-custom png
.B Note:
-Someone will mock you for doing this.
+Someone will mock you for doing this.
+You can also elect to modify
+.CW rio
+to support wallpapers, themes, etc. This has been tried various times in different ways and by different people. YMMV.
+
See:
.ihtml a <a href="http://plan9.stanleylieber.com/rio">
http://plan9.stanleylieber.com/rio,
@@ -1542,8 +1573,6 @@
.CW http://swtch.com/drawterm
.ihtml a
-[Continued on next page]
-
.FG embraceextendextinguish png
There also exists a fork of Russ Cox's drawterm that incorporates features from 9front, most importantly DP9IK authentication support (see
@@ -1819,9 +1848,19 @@
.B Note:
.CW linuxemu
-can only be run on a Plan 9 system booted with a
+is ancient history and can only be run on a Plan 9 system booted with a
.CW 386
-kernel and binaries.
+kernel and binaries. This section should really probably be removed, as you almost certainly want
+.ihtml a <a href="http://man.9front.org/1/vmx">
+.CW
+vmx(1)
+.R
+.ihtml a
+instead. Still,
+.CW vmx(1)
+only works on beefy amd64 systems, and I used to run
+.CW linuxemu
+on a ThinkPad T42 with decent results. Sometimes old and decrepit is worth keeping around.
BOOTSTRAP
@@ -2733,7 +2772,8 @@
.R
.ihtml h3
-Once connected, you can search for your camera device in `/dev/usb/ctl`:
+Once connected, you can search for your camera device in
+.CW /dev/usb/ctl:
.P1
nusb/cam /dev/usb/epXX.X
camv /dev/camXX.X