Skip to main content

feather sticks

Bushcraft and survival experts have spent considerable time telling me about product and less time about skill. I'm still having a hard time sharpening my blades. And along came feathersticks. Most of the time knife demos include:
  • jam the knife into a tree and stand on the blade
  • striking a firesteel
  • chopping
  • cutting paper
  • ease of sharpening
  • and my favorite the featherstick
The problem with featherstick examples is that most bushcrafters make feather sticks in their sleep. Recently I reviewed a number of different knives and I did the featherstick challenge only to fail. Just a few minutes ago I tried to use mu HK folder with serrated blade and failed. Then tried my Ganso folder with a straight edge and after 3 attempts I finally reasonably good for the amount of time.

There are a number of factors that play into a novice featherstick:
  • blade shape and thickness
  • blade edge
  • grip
  • balance
Feathersticks seem to come in many varieties.
  • 90, 180, 360 degree
  • thin and tight, thick and loose, or a combination
  • type hardness of the wood
  • sharp knives are better
  • care for your knife before and after use
Here is what I've learned about technique so far
  • Always push the knife away from your body and avoid the triangle of death
  • the material needs to be straight with a straight grain (it's just easier)
  • while you do not have to start in the edges it can be easier with a light touch there is less friction
  • the draw of the knife can be 90 degrees to the material or at an an angle with the pommel leading the way. The angle increases the surface area of the cut and increases the friction although the initial cut is set by the entry point of the blade
  • when drawing the blade do not simple push the same edge down the wood. Use a cutting like action so that you're using more of the blade on not just one localized area
  • each successive draw should either be just short of the previous draw or just under the previous draw.
  • and repeat; rotating each draw as you create flat spots and edges
Folders are not any better than fixed blade they are just a little safer. Locking folders are likely to be more safe than non-locking folders. Just remember that a sharp knife is the safest because you're not likely to put too much energy into the cut that might backfire.

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…