> On Jul 21, 2021, at 11:42 AM, Dan Cross <crossd@gmail.com> wrote:
>
> On Wed, Jul 21, 2021 at 12:17 PM Xiao-Yong Jin <meta.jxy@gmail.com> wrote:
> > On Jul 21, 2021, at 11:08 AM, Dan Cross <crossd@gmail.com> wrote:
> > > ssh linuxpc drawterm -c srvdev.rc
> > >
> > > yes it's a lot of back and forth, but ssh only is needed for running
> > > the process, the data afterwards can use 9p directly.
> >
> > What's the difference between that and using something like u9fs?
>
> auth?
>
> This is using ssh to attach to the Linux machine to import it's filesystem into the plan9 namespace? Wouldn't authenticating from plan9 to Linux over SSH be independent of drawterm vs u9fs?

Drawterm does the proper auth and connect to the plan9 system.
U9fs needs plan9 srv to auth and connect to it.

If you are running a plan9 system, you probably have your auth
setup.  If you have access to a posix system, you probably have ssh
setup and you have access as a normal user, and that enables you
to do ssh and drawterm back.  No additional setup required.

U9fs, on the contrary, states

          It is typically invoked on a Unix machine by
          inetd with its standard input and output connected to a net-
          work connection, typically TCP on an Ethernet.  It typically
          runs as user root and multiplexes access to multiple Plan 9
          clients over the single wire.  It assumes Plan 9 uids match
          Unix login names, and changes to the corresponding Unix
          effective uid when processing requests.

I'm not going to run this and listen on a public interface even if
it does not run as root.

There are issues with the auth method that u9fs uses, which I'm not
going to discuss here.