Skip to main content

Which distro is the right one?

I would guess that a major part of the friction between the Linux distributions is (a) uncertainty (b) complete understanding. I'm just not sure which one seems to win the day. Back in the day I was a huge believer in FreeBSD and Slackware. The reasons were on the trivial side. FreeBSD was the baseline OS that CyberGuard and later Secure Computing selected. The people who made the decision made it because they thoroughly understood all of the moving parts. I remember later conversations when they were trying to decide whether or not to upgrade to the latest kernel design the meaningless arguments about this feature or that and the FUD the might follow. But it was a solid OS, supported a wide variety of hardware, it was reliable, the filesystem was safe, and installer was trivial.

Slackware was my go-to Linux because the installer was solid, the distro was safe, Patrick did not take any risks and always hand selected the kernel versions and patches, the libraries and 3rd party packages and apps were also highly curated. The best part was that the inner circle lacked trolls and that made it a fun and educational place to be. Sadly they stumbled a few times but nothing to do with the project.

So when I'm thinking about the Docker version of the golang in the public registry I get a little skittish. There is nothing overtly wrong with the Debian distro except that they march to their own drum. Debian is the root to a lot of other popular distros but they have the slowest release schedule. So I'm reluctant to install golang on jessie.

I have two general needs.  (a) I want a very lightweight golang docker image for building my projects. As someone put it... my Dockerfile is my Makefile. (b) I want enough tools that I can construct my IDE and not have to worry about all the extra cruft that installing a full distro suggests. I'd prefer that everything was running on scratch or maybe even the slimmest rkt container but that may be a little premature for now. 

I may try to hash shykes' Dockerfile but it's going to take a while. His file is quite old and I'm planning on working on modern code. There are a few projects out there that are just overly complicated but would make create enterprise tool.


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…