Skip to main content

almost car camping - things learned

I went camping with my kids this past weekend and I decided to take the opportunity to test some gear that I knew I was going to depend on when hiking in the everglades. One particular concern was the temperature swings. As such we were expecting the temps to be 80F during the day and 50F during the night. And it was.

And so we discovered a few things:

  • princess sleeping bags are not rated for 50F
  • My Stansport sleeping bag with a 50F rating is not
  • Sea to Summit Reactor sleeping bag liner is of no use outside a sleeping bag
  • doubling and tripling sleeping bag liners does not help
  • Sleeping bag liner sheets do not help
  • Fleece sleeping blankets are great
  • remember wool socks next time
  • coleman self inflating sleeping pad is OK for car camping but that's it
  • Klymit pads are no fun to pack away when trying to break camp quickly
  • there is something to be said about leaving stuff sacks at home
  • my Klymit inflatable was not that comfortable and it moved a lot as I tried to position myself
  • the Sea to Summit coolmax is treated with insect shield but what's the point if it's only good as a liner
  • I learned from one youtube video that I should have brought my schemog and wrapped my pillow for extra comfort
  • While I had 2 "emergency" blankets I reminded myself of the many difficult times in the book "living with a seal" and pushed through... although I still had a plan.
  • Later in the day I setup my hammock and took an awesome 15 minute nap; I should hve set it up earlier
  • Had I slept in the hammock the I would have experienced a colder night and while I have a proper bivy on order I might have to consider an underquilt or convertable sleeping bag
  • I should have closed the window; and I did on the second night
  • The sea to summit liners are also useless because they are top entry only. One of my kids needed to go to the bathroom and I nearly killed myself trying to get out and back into my bed (side entry would have been better)
various sheets

50F my a$$

useless


Finally, given the variation in the temperature and what it means to be SUL (super ultralight) I just do not think it's possible without spending a lot more money or will to be so much more uncomfortable.

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…