Skip to main content

Review: Mora self comparison

Mora is my fixed blade company of choice for what I need; which is basic camping and bushcraft. As for surviving the great Zombie Apocalypse - that's something I do not know or want to think about.

And so I have developed a collection of Mora knives.

Top: Pathfinder
Left-Right: Robust HQ Carbon, Black Carbon, Companion Carbon, light my fire Stainless, Companion Stainless

Each of these knives is very sharp although the Companion Stainless seemed to be the sharpest from the factory and they are all very pointy. But there are a few things that you might not know so here are some things to note:

  • The pathfinder, Black and light my fire have 90 degree spines for use with fero rods. For the others you'll need to grind the spine, use the blade edge or get a striker.
  • The pathfinder is 8" and the rest are 4". There is some variation in the 4" blades
  • The carbon blades are thicker. Most are 3mm; light my fire is the thinnest and the companion stainless is the median.
  • The blade finish varies across blade type. black, plain or clear coated
The sheaths are quirky. 
  • The robust has a knob so you can biggyback a second knife
  • The black black's belt loop comes with a removable option and will attach without the loop
  • The rest can clip on the robust but they will hang a little lower
  • It's possible to neck carry but I'd recommend a length lanyard
The knives and sheaths are available in a variety of colors, lengths, blade type, materials and lengths. I've decided that I'm not hiding so my knives need to be visible. (poor Joe dropped his invisible camo colored fero rod).

I have not tried the serrated blades and there are a few new blades this year that I hope to evaluate. Of course you ca get the exact specs from the Mora company website as soon as it's updated. The new website is incomplete.

Popular posts from this blog

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…

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.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…