So, to allow a linux vm to access a directory from Fedora host with virtio-9p, I'll need to run:

# semanage fcontext -a -t svirt_home_t "/some/dir"
# restorecon -vR /some/dir

Idk why sealert offers this non-working solution instead. It's really weird.:

# semanage fcontext -a -t virt_image_t 'dir'
# restorecon -v 'dir'

#fedora #linux #selinux #qemu #kvm #vm #virtualmachines #9p #virtio #fedora42 #virtmanager

#9P has DMEXCL/QTEXCL for files that may be opened by only 1 client at a time. But I feel that it would benefit from DMWEXCL for files that can have any number of readers, but opening it with write access requires it be exclusive. Like #GoLang sync.RWMutex vs sync.Mutex.

#Plan9

It would be hard to overstate how much work it took to make this 4-line commit possible https://git.lukeshu.com/sbc-harness/commit/?id=8cc87f8c1f25c9d3fec00561237891650a91b47a

#9P

Lots of things out there say that Styx was "a variant of the 9P protocol", but I haven't found anything that says what was actually different about it.

- The `typ` values that specify the message type are different (9P1 values start counting at 50, Styx starts counting at 0)
- Tcwalk/Rcwalk have been removed
- There is no authentication (so Tsession/Rsession have been removed, and Tattach/Rattach have been shortened)

There you go.

#Plan9 #9P #InfernoOS

To anyone who knows Plan9/9p, am I reading this correct that 9p does not support extended attributes?

#Plan9 #9p

I run a small #plan9 grid at home. This is my drawterm on my Linux PC connected to a Pi4 as a CPU server. It is viewing documents from my local PC, and I connected to a faster CPU in a window to play one of the NES games I wrote.

#distributedcomputing #9p #everythingisafile