9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio.dere@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Posix implementation of Plan 9 cpu(1) (Was: [9fans] Command to set samterm label)
Date: Mon, 19 Jul 2021 06:52:18 +0200	[thread overview]
Message-ID: <CAJQ9t7jOo_ugriE87iLRt+abVygxkOmqxUwakOJt_AGj_pDRsg@mail.gmail.com> (raw)

On 7/19/21, adr via 9fans <9fans@9fans.net> wrote:
> [ ...].  Running samterm locally is way more efficient than
> using X forwarding.
>
I have adopted on my Linux (Mint) workstations - plural - the paradigm:

    ssh -fX remote acme -l lib/task.acme # for different tasks

and it works even remotely pretty adequately. The remotes tend to be
pretty slick Debian servers, but even locally that is a  boon (NetBSD
rules the Posix roost in my office).

What I can't do is to do the same from the Plan 9 workstation that I
still prefer for development. I was bemoaning this in some notes to
myself just before reading the exchange.

Now, it is very common, even after all these years of Plan 9 use, for
me to miss the wood for the trees. I think, not very deeply, that P9P
"cpu" running on the remote Posix server might be what I need - Plan 9
SSH and I seem to be sworn enemies and X-fdorwarding is not even a
twinkle in SSH's eye - and here I note that Steve Simon's cpu server
for Windows has not been included in P9P (I heard Steve bring that up,
but I have never explored it as I don't own a Windows platform).

In short, is it out of the question to cpu into a Posix server to
initiate an acme session, rather than using SSH to forward X?

Lucio.

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T09fcdec9c87bfde4-M980f0728c312f6f6ca5623f2
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

             reply	other threads:[~2021-07-19  4:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19  4:52 Lucio De Re [this message]
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
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=CAJQ9t7jOo_ugriE87iLRt+abVygxkOmqxUwakOJt_AGj_pDRsg@mail.gmail.com \
    --to=lucio.dere@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).