Can you believe it?¡! 3 is a multiple of ⑨ !!!!!!!!!!
Art by me.
#plan9 #9front #art

Very cool, audio playback using drawterm "just works" (and zuke is nice)

#9front #plan9

Japan diary, day151

I restore my old old laptop, Lenovo S21e, NetBSD + i3 + drawterm.
I couldn't install 9front to emmc of this.
There might be better ways to do this, but for now, I can use an old machine like a 9front terminal (^_^).

#netbsd
#i3
#drawterm
#9front

Managed to FINALLY mount an u9fs share from #OpenBSD in #9front, albeit I haven't yet managed to tackle authentication from 9 to BSD, I only managed it with -a none thus far. This isn't ideal. However, here is what I learned so far:

  • You really do need to go the inetd route as outlined in the manual, it is really finicky to run u9fs in any other way
  • However OpenBSD doesn't have 9pfs in /etc/services, but you can recycle the relevant parts from FreeBSD sauces
  • Order of parameters matters, u9fs fails if it isn't in the right order
  • Good idea to specify your own user to run it as using -u YOURBSDUSERNAME
  • u9fs logging basically doesn't exist, not even the verbose mode with -D produces anything useful usually

Amyhow I'll be interested to see if I can listen to music in 9Front over drawterm from my OpenBSD media collection.

Also please someone tell me how to do auth for u9fs.

OK, u9fs for media sharing from unix to #9front is kicking my butt. I am using the "stock" binary from ports on #OpenBSD.

Cpu server / drawterm access are working on #plan9 Glenda has a password and keys and all. I deliberately chose p9sk1 for the keys in factotum to enable legacy protocols since, as far as I can tell, u9fs only knows that.

Added this to /etc/services (from FreeBSD's equivalent):

9pfs 564/tcp #plan 9 file service
9pfs 564/udp #plan 9 file service

Added this to /etc/inetd.conf:

9pfs stream tcp nowait root /usr/local/sbin/u9fs -D -a p9any -l /var/log/u9fs /media

I opened TCP/564 in pf.conf for good measure - tho I think inetd does this? Anyway,

pass out proto tcp to any port 564
pass in proto tcp to any port 564

u9fs.keys is in place on OpenBSD and it has exactly 3 lines only with password/username/host. Can confirm inetd is OK and u9fs process is running.

However, on 9front:

cpu% 9fs 192.168.1.101
post...
srv net!192.168.1.101!9fs: mount failed: unknown user
cpu%

Same result if I run it manually with srv and mount -c

Logs on OpenBSD side for u9fs don't show anything (wish "verbose logging" were actually verbose and logged something..)

What am I missing?!

#plan9 / #9front browser for the #smolweb #nex protocol:
echo $page | aux/dial tcp!^$domain^!1900

(e.g. try with domain='nightfall.city' and page='/')

Does anyone know of a walkthrough for creating u9fs network shares under #OpenBSD to mount network drives under #plan9 / #9front? I read the manpage for it but it seems a bit all over the place.

RE: https://exquisite.social/@rqm/116504044245785798

Answer: client-side, meta-F to make drawterm fullscreen.

#9front

How does one make the drawterm window extend to the full screen? Is it something I need to configure on the cpu server side or on the client side?#9front

@steeph @fedops

My understanding is that it's a central meme to the #9front community.

Largish, at the top, in italics and all caps, it says, "THE PLAN FELL OFF" on https://9front.org 😄

9FRONT.ORG THE PLAN FELL OFF