summaryrefslogtreecommitdiff
path: root/network/mosh/README
diff options
context:
space:
mode:
Diffstat (limited to 'network/mosh/README')
-rw-r--r--network/mosh/README21
1 files changed, 2 insertions, 19 deletions
diff --git a/network/mosh/README b/network/mosh/README
index f098288859..5ac44ffac3 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.