great, there is a remount=rw or =ro
and theres a fatal errors one there somewhere to which remounts it based on
the remount /c:202124102229
ps: anyone else having probelms with eht permission on p.m. with the dodgy
non
kernel fuse blk (and is it going to be moved (back?) into the kernel ) --
gaping
> Should this be expected to work? Or is mmap not supported over v9fs?
OK, found the answer: adding 'cache=mmap' to the mount options
makes it work beautifully! I suppose there's a good reason this
isn't the default ... (?)
--
9fans: 9fans
Permalink:
http
I'm trying to cross-compile go for plan9-386 using go-linux-amd64
(on a linux laptop) with the source tree mounted from a plan 9 server
via v9fs (mount -t 9p).
All goes well up to a point, then this happens:
/mnt/sys/lib/go1.17/pkg/tool/linux_amd64/link: mapping output file failed:
invalid argum
