9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: Posix implementation of Plan 9 cpu(1) (Was: [9fans] Command to set samterm label)
Date: Wed, 21 Jul 2021 13:57:09 -0400	[thread overview]
Message-ID: <CAEoi9W6-uiYtfsduSr5==40kEBTg44GM+Y+Ejd5d27whY+-djg@mail.gmail.com> (raw)
In-Reply-To: <F45A5497-5D2D-44E3-8EFD-99DFA4B136CC@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]

On Wed, Jul 21, 2021 at 1:32 PM Xiao-Yong Jin <meta.jxy@gmail.com> wrote:

> > On Jul 21, 2021, at 12:16 PM, Dan Cross <crossd@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-Mbefc0794ea49365431f10fc4
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 2281 bytes --]

  reply	other threads:[~2021-07-21 17:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19  4:52 Lucio De Re
2021-07-19  5:20 ` Michael Misch
2021-07-19  7:13   ` Steve Simon
2021-07-21  3:52     ` Lucio De Re
2021-07-21 14:59       ` Xiao-Yong Jin
2021-07-21 15:11         ` hiro
2021-07-21 16:08           ` Dan Cross
2021-07-21 16:16             ` Xiao-Yong Jin
2021-07-21 16:42               ` Dan Cross
2021-07-21 17:08                 ` Xiao-Yong Jin
2021-07-21 17:16                   ` Dan Cross
2021-07-21 17:31                     ` Xiao-Yong Jin
2021-07-21 17:57                       ` Dan Cross [this message]
2021-07-21 18:09                         ` hiro
2021-07-21 18:11                           ` hiro
2021-07-21 21:41                             ` Steve Simon
2021-07-21 17:41                 ` hiro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEoi9W6-uiYtfsduSr5==40kEBTg44GM+Y+Ejd5d27whY+-djg@mail.gmail.com' \
    --to=crossd@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).