Skip to main content

"Now that's a knife"

My new Mora knifes arrived. The 746 Allround and the Allround Multi-purpose (I'll refer to it as the MP).

top to bottom: Companion, 748MG, Pathfinder, Multipurpose
It's easy to see the blade length and once you've handled a SCHF37 you'll know just how special Mora knives are. In practical terms I went directly to my pile of processed word and started making feathersticks. These knives are the sharpest yet.

Given the 8.1 inch length of the MP I was surprised how light it is. The thing about the short blades is that your stroke to make a feather is shorter and with the long blade the stroke is longer. That means that more of the blade will tear at your skin until your nerves report any sort of pain to your brain. I have the cuts to prove it.

I do have one complaint. The sheathes.

The MG and MP sheathes are made from the same plastic, however, the lops are either leather, pleather or some other synthetic that is not webbing. Also missing is some kind of piggyback that many of the shorter knifes have. I'm also not sure if I'd neck carry on of these.

I think the best option would be one of those multi setups that Mora has for the Konsol or Garberg.

PS: after watching a family camping video from Joe Robinet where in he chipped his razor sharp ax on something that was embedded in the end of the wood segment he was processing I'm not sure what my position is on things.

I have seem more than one demo by professionals where the presenter was in harms way while swinging an ax. While I've cut my fingers processing wood this could have been easily prevented by wearing gloves. But the ax can do much more than just break the skin. Using the saw and baton might take longer but it's safer. Not to mention that even if you had a dedicated heavy batoning knife it will probably be lighter than the ax.

I have a Mora hatchet and I'm not sure how that figures in yet. Again the risks are similar to the ax. There is a lot of energy moving in the blade where the baton does not have a blade and the force of the blade is moving in one direction meaning that the blade is not going to jump and cut your foot off.
The MG is just a little shorter than the pathfinder
Big and Tall belt carry. Depending on how big and tall you might be you gotta be careful. Sheathing a knife and not taking care you might give yourself a severe laceration. So make sure you do not have too much overhang if you know what I mean.

Popular posts from this blog

Prometheus vs Bosun

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

TL;DR;

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…