Skip to main content

Review: Victorinox Farmer

Victorinox, aka S.A.K., is probably one of the most recognizable knife companies out there. I do not recall when I receive my first SAK but I have received, bought, and lost many. In fact I have one in my dopp kit for when I travel and check my bags and several around the house including my office.



Recently I decided to give the SAK Farmer a try as one of the BOBs (bug out boys) I like to watch decided to leave his fixed blade at home and try an expedition with just his Farmer. He was successful, however, unless he secretly had a saw, fixed blade or secret ax I think I learned a few things from my try-stick.

  • know where you are going so you know what sort of fuel you can expect
  • know the weather conditions because wet fuel can change the profile
  • know if you are going to use a gas cooking fire or a wood cooking fire
  • know if you're going to have or make a recreational campfire
  • know if you are going to cook where you sleep (not a great idea)
After considering this I came to the conclusion that using a SAK Farmer is a trade-off between time and weight. The blade and saw are so small that your wood is likely dead-fall and dry or very dry. The saw blade will become ineffective as the green material sticks. And the small blade does not baton very well. Adding a cobra type paracord lanyard as a grip was somewhat helpful but much less than perfect. Practicing a tight grip the part of the knife body used to connect the lanyard ring protrudes from the knife body and is irritating to a tight squeeze.

 
I like the position of the awl as a striker for my fero rod. Having the awl, blade and saw are good tools for making a bow-drill or pump fire drill. The can opener and bottle opener are always handy, however, I think Robinson, Torx and/or Phillips have long overtaken the "regular" screw.

PS the spring action is pretty tight. I could have lost a finger.

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…