Skip to main content

Review: Schrade ax and Morakniv ax

My motive is described here. In this review I'm not comparing the two axes but suggesting that they are complementary.

The Mora is a 17oz camping axe with a small blade and a good handle. With the shape of the blade and handle the power is delivered on target. The blade was sharp from the factory and I was able to create a featherstick out of the box and because of the handle material and the size of the tang the balance was fine. It's one ax that has multiple overlapping uses with some bushcraft knives. Not that it really matters but there is a coating on the blade and the noncutting edges are slightly smooth so there will be no sparks from here.

The Schrade Survival ax comes with a sharpening stone and a firesteel. The blade is coated, however, was able to strike the firesteel. Also the Schrade Ax is nearly 2lbs giving it some heft. The handle of the Schrade is almost 4in longer than the Mora. The steel seems to be protected in the handle. While the ax was awkward when used to strike the steel it was not impossible but it probably better as a container rather then a striker.

My latest wood processing session started with the Schrade ax and then I moved to my Mora hatchet (yes, I think it's a hatchet and not an ax). The Mora, while capable, did not handle the hardwood very well and required a lot of work to processes the wood. The Schrade, because it was heavier, handled the first step of processing much easier.

Lastly, I would also say that while the Schrade Bowie is 3in longer than the Mora hatchet the weight (23oz) is distributed where most of the Mora's weight is focused on the head. And so the Bowie is not much of a replacement for the Bowie and vice versa.

The Schrade is a buy and the Mora is a maybe. Depending on what you're carrying a second ax might not be handy and if you use a hefty bushcraft knife it might be preferred.

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…