Skip to main content

SoloStove and RUCAS

I read an article where the user has put his Trangia in his SoloStove. So why not a RUCAS? After the RUCAS warmed up it's flames were about 10-12 inches from the top of the RUCAS. You can see the pink/purple bloom to the right. I practically had to drop my 450ml of water onto the stove or else I was going to burn something. Needless to say this is no way to cook a meal, just heat some water.

This was approximately 1oz and it burned off in about 4 minutes. The water was warm but not hot enough to make a cup of tea. After the alcohol burned out I put another oz in the stove and it started with a quick spark. Since the stove was already hot the jets flamed right away and I nearly burned my hand again from the stove and the hot pot.


To confirm my previous suspicions: [a] gloves [b] wooden spoon [c] better stand [d] no actual cooking. I might be able to alter these parameters if I had [a] a windscreen, [b] a different base. Let me be clear; if 3oz of alcohol is supposed to be 14 minutes of burn time by comparison that would be a lit of twigs and prep.

Lastly, if 3oz is 14min then 9oz is about 60min. By comparison an 8oz isopro is supposed to have 60min of burn time. The tradeoffs are:

  • SoloStove - preptime, care and feeding, soot, bad in damp conditions
  • alcohol stove - short warmup time, any stove will do, limited burn time, clean, 9oz=60min, liquid alcohol has risks that the others so not although there are multiple uses
  • pocketrocket - no warmup time, 8oz=60min, easy to waste fuel
  • tablets - no warmup, needs a cup or plate, soot, east to store
  • open campfires or propane stoves for more elaborate food prep, not good for hiking, and if you're on the AT or PCT you're not likely to have that kind of fresh food worth cooking

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…