Skip to main content

Osprey Levity vs Gossamer Gear

Starting at the beginning it's important to note that this is not going to be a straight volume comparison because the brands simply do not offer liter for liter packs. GG has a 40L and a 50L to Osprey's 45L.

The tail of the tape: The Osprey specs

  • The Levity 45L in the large model is actually 48L and weighs 1.9 pounds
  • load 5-20lbs
  • hipbelt with no pockets
  • load lifters
  • no shouldter strap pockets
  • costs $250
  • 3 huge stretch compartments
  • non-detachable brain
  • compression static rope with loops all over the place.
The Gossamer Gear Silverback 2017 
  • The Silverback 50 comes in at 2.5 pounds
  • load 35lbs
  • hipbelt comes in 3 sizes which I assume is the belt length and not the twin pocket size.
  • no load lifters
  • no shoulder pockets
  • 2017 model is offered at a discount $115
  • 3 huge stretch pockets
  • detachable brain
  • compression straps
  • removable sit pad
  • Not many differences between the 2017 and 2018 Gorilla 40L models except the brain. The 2018 Silverback has not been released if there is one.
  • Just to note; the 2018 Kumo added shoulder pockets which are good for a smartphone, small camera or some snacks but not good for a Smartwater 750ml bottle.
The problem with the Osprey Levity 45L/60L is that the load range is 5-20lbs/10-25lbs and so you have all that extra room but there is a tradeoff between volume and weight and in most cases when you start going UL or SUL you also need less volume.

For example the John Z. used his Palante Pack as part of an unassisted record out west. Watching his start I remember he complained about pack weight because he had 10 days of food (approx 20lbs). And then there was his gear which must have been between 5 and 10 lbs. Frankly that's not a lot of gear and given the volume and weight ratio he was at capacity.

I have a number of packs and I have yet to find my overnight sweet spot. I think a base weight of 8lbs is good enough for an overnight and probably a long weekend to maybe 5 days. The general difference between an overnight and 5 days is going to be consumables and the effect of weather conditions.


Popular posts from this blog

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.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

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…