Skip to main content

alcohol stove vs isobut canister stove

Pictured below are my RUCAS alcohol stove and my Olicamp ION canister stove. I started cooking with my RUCAS but quickly frustrated with the flames reaching up the side of my Stanley pot.


It's possible and even probable that my flame size is related to the way I use the stove; resting the pot directly on the stove; or maybe it's the fuel. In the intervening months I abandoned the RUCAS in favor of the canister stove.

But recently I was watching a video prepared by RevHiker and he mentioned that either his pocket rocket or his replacement had a tendency to quirt fuel when disassembling his stove. That got me to thinking about a number of things related to Survival. In recent weeks I have been rejecting "survival" as an offshoot of bushcraft a real thing. My hypothesis remains, not much will happen in 3-4 days on the AT or FT if your food get's eaten by a critter or your stove malfunctions.

Now that I have one spare canister and 3 on the way I find myself concerned about malfunctions. Realistically you never hear anyone complain about serious canister malfunctions. This biggest risk is likely the 4th season and it's effect on the gaskets but since this is Florida and I'm not planning to hike in the winter that should not be a problem.

Out of curiosity I checked the pricing of the Toaks Stove kit. The discount price is nice although they are sold out and they are not offered on Amazon. It's important to note that the same rules still apply. Alcohol stoves do not have an off switch, they can spill and start a fire, and are simply not allowed in some high risk parks.

So like everything else in my pack... it's all about well organized planning.

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…