Skip to main content

doing more with less or just doing with less

Reading the book "Living with a SEAL" I took away the notion of doing with less. It was an indirect observation as the SEAL did a lot with a lot less. And as I transitioned from wannabe bushcrafter/Survivalist to wannabe backpacker to wannabe hiker and now lightweight or ultralight hiker I see that there is something to be said for going light as a metaphor for life.
I'm not going all new age; it's just as I look around my desk I see no less than 10 WiFi routers that are so inferior I will never use them again even if the current router completely malfunctions. And I should throw them away as soon as possible... I will feel better for it.
getting back on track; just this morning I was setting up my Luna Solo for the first time. It went as expected and I almost got things going the way I wanted. I had packed up and was putting the tent and accessories back in my pack when I tried to stuff my Tyvek footprint in the sleeve reserved for a hydration system and which was being repurposed with a thermarest Z-Seat to give the pack some structure.

when I purchased the pad I thought it was just a few panels from the sleeping mattress. But it's not. It's too small to be anything other than a butt warmer.
As I struggled to get the footprint in the slot I realized I was going to have two pieces of kit for the same function. I was already planning to have some reflectix in the tent and use the same thing to put my pack on when transitioning, to sit on while eating or resting and to sleep on since my torso mattress does not extend to my feel.

While the Z-Seat is light it has volume. And so I am lightening my load for an overnight.

  • pack
  • tent, mattress, pillow, liner, reflectix, cordage
  • hiking poles
  • the close on my back including hat, schmog, rain jacket
  • cook kit and spoon
  • first aid kit with hand sanitizer, mosquito spray, liquid soap
  • water and water filtration
  • lighter, fero rod, fatwood, cotton or lint
  • 2 days of food
  • small knife and extra cordage
  • headlamp, compass, whistle
  • second pair of socks for bed and the following day
  • camp shoes (optional)
If it's cold I might bring a sweater but I doubt it. For a similar reason I would bring a wool cap to keep warm or keep the bugs out or my ears.

Since this first overnight is in a campground that does not permit hanging things from trees I have to hope for a bear box and there isn't any way I can erect a tarp/rainfly. The other optional piece of kit might be a bushcraft knife if the campsite provides firewood for a campfire. (gotta have TV).

** I'm not counting my phone or camera.

Six Moon Designs Luna Solo - setup wrong

Popular posts from this blog

Prometheus vs Bosun

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


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…