From: John Weaver <jweaver@ehzed.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Terminal possibliities...
Date: Fri, 30 Sep 2016 13:36:19 -0700 [thread overview]
Message-ID: <alpine.DEB.2.02.1609301322330.3013@nitrogen.ehzed.com> (raw)
In-Reply-To: <74EC26F7-B6A1-4002-90DA-F232F867ACE1@yahoo.ca>
It's not the bandwidth, it's the latency. I have been playing around with
this for a few weeks now. I have it working on T60 that has the kernel,
9fat and a cfs partition locally with the root on a vps 80ms away. There
are pros and cons vs drawterm to the same machine. Things that I have not
explored yet are 1) running a local build and binding $home from the vps
or using the vps as a cpu server.
--
john weaver -- jweaver@ehzed.com
On Fri, 30 Sep 2016, Chris McGee wrote:
> It would be interesting to hear how this works out in practice. The bandwidth requirement is probably so low compared to typical traffic from a hotel, compared even to smart phones.
>
>> On Sep 30, 2016, at 3:49 PM, James A. Robinson <jim.robinson@gmail.com> wrote:
>>
>> Is anyone here using Plan 9 as a terminal to connect to remote CPU / File servers over the internet to get work done?
>>
>> If I set up a small Plan 9 cluster at home, I'm thinking it'd be pretty neat to be able to connect to the network at home over the internet.
>>
>> While I have a laptop and could put 9front on it, I also really like the thought of carrying around a little Raspberry Pi and portable keyboard/mouse as an alternative. Sitting here in a cheap motel room, I realized that all the hotel rooms I've been in over the past few years have a decent flat screen television that takes an HDMI input and has had decent, if not amazing, WiFi to the internet.
>>
>> Jim
>>
>
>
next prev parent reply other threads:[~2016-09-30 20:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 19:49 James A. Robinson
2016-09-30 20:20 ` Chris McGee
2016-09-30 20:33 ` James A. Robinson
2016-09-30 20:36 ` John Weaver [this message]
2016-09-30 22:54 ` hiro
2016-09-30 23:56 ` Erik Quanstrom
2016-10-01 6:32 ` James A. Robinson
2016-10-01 8:06 ` hiro
2016-10-01 8:17 ` James A. Robinson
2016-10-01 11:57 ` Chris McGee
2016-10-01 13:40 ` James A. Robinson
2016-10-01 13:58 ` Chris McGee
2016-09-30 20:40 ` Steve Simon
2016-09-30 22:57 ` hiro
2016-10-01 22:40 ` Skip Tavakkolian
2016-10-01 23:04 ` hiro
2016-10-02 9:10 ` Richard Miller
2016-10-02 15:03 ` James A. Robinson
2016-10-03 2:07 ` Chris McGee
2016-10-03 2:28 ` sl
2016-10-03 2:35 ` Chris McGee
2016-10-03 2:47 ` sl
2016-10-03 3:57 ` James A. Robinson
2016-10-03 2:39 ` Alex Musolino
[not found] <1631101077.3767158.1475340735977.ref@mail.yahoo.com>
2016-10-01 16:52 ` Brian L. Stuart
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=alpine.DEB.2.02.1609301322330.3013@nitrogen.ehzed.com \
--to=jweaver@ehzed.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).