diff options
| author | Ruari Oedegaard <sbo@ruari.com> | 2012-05-05 12:30:33 -0400 |
|---|---|---|
| committer | Erik Hanson <erik@slackbuilds.org> | 2012-05-07 12:18:09 -0500 |
| commit | a05734524671fe5b94b09d465f5e2a200650af4c (patch) | |
| tree | 17f1cbd065af91470ff418d0718e00441f45890e /network/mosh/README | |
| parent | 47304fe33c775caa2f38085734ca394237174765 (diff) | |
network/mosh: Updated for version 1.2.
Signed-off-by: dsomero <xgizzmo@slackbuilds.org>
Diffstat (limited to 'network/mosh/README')
| -rw-r--r-- | network/mosh/README | 21 |
1 files changed, 2 insertions, 19 deletions
diff --git a/network/mosh/README b/network/mosh/README index f098288859071..5ac44ffac34d9 100644 --- a/network/mosh/README +++ b/network/mosh/README @@ -6,24 +6,7 @@ Mosh attempts to improve on SSH by being more robust and responsive, especially over Wi-Fi, cellular, and long-distance links. Mosh requires a little tweaking after first install on Slackware. Both -the Mosh server and client applications must be run with a a UTF-8 -locale, which is not Slackware's default. - -To configure your client to work in a UTF-8 locale you should refer to -Slackware documentation. - -For the server (remotehost), Mosh gets its locale setting from the -client that is conecting to it. Slackware's SSH client and server do not -send and receive locale information in their default configuration (SSH -is used bootstrap the Mosh connection). Assuming that you have -configured the client to use a UTF-8 locale you can work around this by -connecting to the remotehost as follows: - -$ mosh remotehost --server="LANG=$LANG mosh-server" - -To avoid having to do this every time add 'SendEnv LANG LC_COLLATE' to -/etc/ssh/ssh_config (on the client) and 'AcceptEnv LANG LC_COLLATE' to -/etc/ssh/sshd_config (on the remotehost) and then restart the server's -SSH daemon. +the Mosh server and client applications must be run with a UTF-8 locale, +which is not Slackware's default. Mosh depends on protobuf and perl-IO-Tty. |