Skip to main content

Getting mosh to build, deploy and run ... on OpenBSD, Ubuntu, OSX

This was a pain in the ass but I'm glad I went through the process. In addition to my previous observations it also became apparent that Mosh is not running in userspace except on the server side depending on how it was installed on the server.

Installing Mosh on OSX using homebrew seemed to have some subtle side-effects when using fishshell so I made certain I was using bash. Also, there was boost package conflict so I had to remove and reinstall it.

About the only good news is that it installed flawlessly except that since it was installed with apt-get it was installed as root. I suppose if I had manually compiled I would have only marginally better results because the installation instructions want a "% make install" which is clearly being installed as root.

Installing Mosh on my OpenBSD 5.3 machine was by far the longest, hardest, and time consuming. The biggest flaw appears to be that the installation instructions on the Mosh site missed a number of dependencies and exposed a number of packages that needed to be removed and reinstalled. And they also left out the necessary environment configurations needed for automake and autoconf. Finally, in order to install the program I noticed that I needed to install as root; which is contrary to the docs that say the service runs in userspace.

sudo pkg_add
sudo pkg_add
sudo pkg_add
sudo pkg_add


./configure && make
sudo make install

My biggest complaint is that Mosh's own documentation recommends against UDP into production systems. (they loosened their stance on being more secure than SSH)

Uninstalling could be a whole new set of pain.

Side Note: as a system professional, part-time security analyst, and humble Mac user I constantly use the provided "terminal" application. I have also installed the 3rd party version called "iterm2".  iterm2 is awesome but I have a number of long term concerns.  The first and foremost is the likelihood that someone, someday, will insert some sort of trojan and start farming my terminal passwords and terminal sessions to some remote point on the globe. The second pain point that I am addressing by using my iPad as a terminal is that just about every application I install on my OSX machine is being installed by the root user. (there are so may complications here)


Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…