From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] vnc-like cpu service
Date: Fri, 14 Oct 2005 22:07:47 -0400 [thread overview]
Message-ID: <ee9e417a0510141907v6d27edfagaf24862cd82f01ab@mail.gmail.com> (raw)
In-Reply-To: <451cb3010510141605x4a39217fq1c3fbaa3d5dc26f2@mail.gmail.com>
> > drawterm in to a session, then later drawterm in from somewhere
> > else and get the same rio workspace. (The first session would
> > disconnect at that point if it hadn't already.)
> i'd prefer a multiplexer, like *n*x screen(1) does.
> One can even run presentations and live tutors within.
Fine, do a multiplexer. I guess then you'd have
/mnt/term/0 /mnt/term/1 etc. The single-client
approach means you don't change the usual
meaning of /mnt/term. I'm happy to have a
mux and run it in single-guy mode.
Russ
prev parent reply other threads:[~2005-10-15 2:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 15:11 Russ Cox
2005-10-13 15:40 ` andrey mirtchovski
2005-10-13 18:52 ` rog
2005-10-14 23:05 ` McLone
2005-10-15 2:07 ` Russ Cox [this message]
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=ee9e417a0510141907v6d27edfagaf24862cd82f01ab@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/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).