assume there is a better and more sensible way to do everything here
-----------
scraps

echo df >>/srv/hjfs.cmd # check disk space
don't use vesa on efi

-----------
ssh key:
- auth/rsagen -t ’service=ssh’ >$home/lib/ssh/key
- auth/rsa2ssh -2 $home/lib/ssh/key >$home/lib/ssh/key.pub
- cat $home/lib/ssh/key >/mnt/factotum/ctl

-----------
sysinfo checklist:
- cd '#ec'; for(i in *){echo $i '=' `{cat $i}}
- cat '#'P/archctl
- cat '#'P/irqalloc
- cat '#'P/ioalloc
- cat '#'c/config
- cat '#'c/sysstat
- cat '#'¶/swap
- awk /^Plan 9/{p=1} /^init: starting/{exit} {if(p)print} '#'c/kmesg
- pci -v
- aux/cpuid
- aux/icanhasmsi
- aux/icanhasvmx -v
- aux/pcmcia
- cat '#'u/usb/ctl
- cat '#'S/sdctl
- cat '#'S/sdC0/ctl
- cat '#'S/sdE0/ctl
- cat '#'S/sdM0/ctl
- cat '#'l0/ether0/*
- cat '#'v/vgactl
- @{rfork n; aux/realemu; aux/vga -p}
- xd -x1 '#'r/nvram
- cat '#'A/audiostat
- cat '#'A/volume
- cat /mnt/apm/ctl

new user from host owner
- (after adding to fs)
- auth/keyfs
- auth/changeuser bobby
- auth/enable bobby
- rcpu -u bobby
- /sys/lib/newuser

-----------
wifi

device setup:
- (this assumes the driver exists)
- bound to a symbol during boot - '#l1' is a safe guess
- try `bind -a '#l1' /net`, it will tell you the firmware it wants
- find it (openbsd) and put it in /lib/firmware
- lc /net, make sure ether1 (for example) is there
- cat /net/ether1/ifstats # make sure you see some networks around

key and connecting:
- echo 'key proto=wpapsk essid=yournetwork !password=yourwpakey' > /mnt/factotum/ctl
- cat /mnt/factotum/ctl      # verify
  tkey proto=wpapsk essid=yournetwork !password?
- aux/wpa -2 /net/ether1
- echo essid yournetwork > /net/ether1/clone
- ip/ipconfig -p ether /net/ether1
- cat /net/ndb      # verify

troubleshooting some stuff
- with an incorrect password you still get 'ipconfig: no success with DHCP' (it seems?)

alt aux/wpa
- aux/wpa -2 -s yourssid -p /net/ether1

-----------
factotum/secstore
- factotum reads from secstore on startup

-----------
kernel fileservers
- cat /dev/devices