Re: High latency shell environment
From: Icarus Sparry (usenet_at_icarus.freeuk.com)
Date: 12/30/03
- Next message: Kevin Collins: "Re: High latency shell environment"
- Previous message: Barry Margolin: "Re: Newbie needs help with sed command"
- In reply to: Randal L. Schwartz: "Re: High latency shell environment"
- Next in thread: Kevin Collins: "Re: High latency shell environment"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 30 Dec 2003 21:21:39 GMT
Randal L. Schwartz wrote:
>>>>>> "Funky" == Funky Trilobyte <funky_trilobyte@hotmail.com> writes:
>
> Funky> The folks in alt.satellite.starband are so far saying that
> interactive Funky> shells will be unbearable due to near-1000ms latencies.
>
> I've been doing just fine using ssh over 1000ms latency connections
> from cruise ships (www.geekcruises.com). However, I started in the
> early days of the net where slow modems were the norm, and my brain
> just has flashbacks to those days. :)
>
> Perhaps I tolerate it because I know it'll only be for a dozen hours
> during the week I'm aboard ship, however.
>
> I'd suggest looking into "remoting" as many things as you can. Learn
> to use a local mail client with IMAP, and edit local files, keeping
> them sync'ed up with rsync and CVS, and so on.
>
> Just another Unix hacker,
>
Other things which might help are
1) turning off command line editing in bash, and using something like 'ile'
as a front end to your 'ssh'. This means that editing the command line is
done on your local machine. Of course you don't have filename completion.
2) Look at '9term'. This is a little like xterm, but you have infinite
scrolback, so you don't need to repeat commands like 'ls' just because it
has left the buffer. Again you can edit commands before you submit them.
Some definitions of a Unix Guru include someone who can write a device
driver using 'cat'. With 9term this is easy, but it is a little different
from the normal xterm way of working. This is closest to your description
of what you want to do.
3) Do make sure you can use tools like 'ed', and not have to use emacs/vi.
If you have to have a full screen editor, then for small files transfer
them to your local machine, edit them, and copy them back. For big files
you might consider learning 'sam', an editor split into a remote display
part and an editor. (I am assuming that latency is the entire problem, and
that bandwidth is not too much of a problem).
Icarus
- Next message: Kevin Collins: "Re: High latency shell environment"
- Previous message: Barry Margolin: "Re: Newbie needs help with sed command"
- In reply to: Randal L. Schwartz: "Re: High latency shell environment"
- Next in thread: Kevin Collins: "Re: High latency shell environment"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|