There were some peculiarities with setting up 9front on the Raspberry Pi, which were not covered in the (otherwise great) 9front FQAs, so I wrote up my notes in setting up on a Pi 3 B+.
Let me know if there are any mistakes or misconceptions there, I'm still feeling my way around here.
@nf Nice. A lot of people snag on exactly these things, esp. the cmdline.txt. A few comments:
It's important to mention that cmdline.txt requires all parameters on the same line -- unlike the plan9.ini.
For boot time DHCP you simply omit any IP(v6) configuration from the NDB. The cpurc (termrc) script first tries pulling the config out of NDB, then falls back to DHCP. Simply have a sys= ether= entry for the machine.
@nf It looks as though I'm about a session ahead of you in setting up an rpi albeit with vanilla plan 9. All the same gotchas though. Great job with the notes. I guess your next step, is setting up a CPU server. Plenty to get wrong there, as I've just found. Again, some pi peculiarities, I think.
I converted my 9front term install into cpu+auth. I made many random changes that I now don't recollect all of them to note it down.
Also, the sshfs that was working in the terminal is no longer working. Auth "says no key matches". I had added it into $home/lib/sshthumbs (probably 9front specific file). Going to read a bit about auth tonight.
@abortretryfail @nf there is a man page available for gpio(3) as part of a 9legacy patch: http://9legacy.org/9legacy/patch/bcm-brian-man.diff
"I appreciate SDF but it's a general-purpose server and the name doesn't make it obvious that it's about art." - Eugen Rochko