If it feels a bit too much I suggest you look a few commits back before I added write support, it was still simpler then. Eventually I'll have both the lite and full versions, with generous comments.
There's also /sys/src/lib9p/ramfs.c but its usage of 9pfile(2) obstructs a lot of important stuff.
@glenda By the way, sorry for the very late reply. I'm not particulary active around here. :)
@glenda Sounds good to me. We already have some articles on programming with 9 on the old wiki. I'll migrate them soon and make a new section.
Just send me an email with the text and I can commit. I can also add you to the editors if you wish.
@royniang I know right?
I don't think upas(/fs) currently supports moving messages around, so the save thing only works for bare mdirs where you can just copy in the actual mail file. You could still use that I imagine, but you'd have to open the 'sent' mdir separately with upas/fs. And it'd only be local to the machine.
@royniang Bcc yourself :P
@royniang I'm moderately sure Sigrid wrote one.
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.
"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