<div dir="ltr"><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large">NFS v4 provides idmapping between client uids/gids and their server equivalents using a config file.</div><div class="gmail_default" style="font-family:times new roman,serif;font-size:large"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 16, 2024 at 9:46 AM Dan Cross <<a href="mailto:crossd@gmail.com">crossd@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, May 16, 2024 at 7:51 AM John Cowan <<a href="mailto:cowan@ccil.org" target="_blank">cowan@ccil.org</a>> wrote:<br>
> [snip]<br>
> This appears to be a VHS vs. Betamax battle: NFS was not transparent, but Sun had far more marketing clout. However, the Manchester Connection required a single uid space (as far as I can tell), which may also have been a (perceived) institutional barrier.<br>
<br>
So did NFS, for that matter.<br>
<br>
This is one of those areas where Unix appears creaky in comparison to<br>
Plan 9. `ssh` is all about remote access to resources, whereas plan 9<br>
was all about resource sharing: you'd set up a namespace with all of<br>
the resources (exposed as files from wherever they ultimately came<br>
from) you cared about, and then operate on those "locally"; the<br>
resources were shared with you and access was transparent, via a<br>
consistent, file-based interface. You want to `diff` two remote files?<br>
Import the filesystems they're both on, mount those somewhere, and<br>
`diff /n/host1/file /n/host2/file`.<br>
<br>
I think the `sshfs`+FUSE model that Doug mentioned is about the<br>
closest you're going to get these days.<br>
<br>
- Dan C.<br>
<br>
<br>
- Dan C.<br>
</blockquote></div>