it's still equivalent, obviously you can start drawterm in the background or in some persistent virtual terminal emulator.
and yes, both drawterm and ssh will use TCP below, the only difference in the stack for the actual data would be that instead of SSH you would have TLS for encryption. On 7/21/21, Dan Cross <cro...@gmail.com> wrote: > On Wed, Jul 21, 2021 at 1:32 PM Xiao-Yong Jin <meta....@gmail.com> wrote: > >> > On Jul 21, 2021, at 12:16 PM, Dan Cross <cro...@gmail.com> wrote: >> > >> > Nothing prevents you from invoking u9fs over an SSH connection; one >> needn't run it from inetd, and I doubt anyone has in 20 years. >> >> You are right. In that case, the only difference is just that, >> citing hiro, >> >> 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. > > > It's unclear what that's supposed to mean. There's obviously still a > transport involved; in one case, that's over (I presume) TLS over a TCP > connection owned by drawterm, in the other, it's a bitstream running over > the SSH protocol over TCP. In the former case, if the drawterm process on > the Linux side dies for whatever reason, your imported resources disappear. > In the latter, if the sshd or u9fs die, same. > > Overall, this seems like abusing drawterm to do what u9fs (or other, > similar userspace 9P servers) was (were) intended to do. > > - Dan C. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T09fcdec9c87bfde4-Me7a96cf8efb8514500af667a Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
