Skip to main content

Paria 2P bugnet tent

My 2P bugner from Paria arrived yesterday. It looks a lot like the MSR model of the same kind of tent. The 2P size makes sense when using it with standard camping pads or air mattresses, however, if you have a couple of junior twins there's only room for one.

As a common theme I'm interested in reasonably lightweight gear at a price that I can afford to buy or replace on a moments notice without breaking the bank. I hate to think this gear needs to survive a single camping trip or season but at least a year. But I'm looking at quality and workmanship too. And maybe the little things too.

This is the corner tieout. This is where the webbing attaches to the corner of the tub. Not pictured here is a few inches of cordage so you're not staking directly to the webbing. I suppose they could have saved a few bucks by skipping that step except that this means if you rolled to the side you might not poke yourself as the stakes are slightly farther out.

If the door is north position then this seam runs from east to west and is seam taped.

The first problem I noticed is that there is a thread that extends out from under the tape. Water will definitely enter here even though it's just the diameter of a thread. Also this thread may catch and rip the tape.

Second, I noticed that while the tape was mostly uniform by the time it got to the door the overlap with the thread was only about 1mm. This will not last very long.

One of the surprising features was the zipper stop. The little patch of silver material covering the zipper to prevent it from getting stuck in the end and derailing. It also meant the manufacturer could use a bulk zipper. But it's smooth.

The peak of the tent has a webbing loop and a lineloc. The lineloc is ok and works in this configuration because there is modest tension on the cordage. Linelocs typically face down so that the main and working end are parallel. In this configuration the lineloc faces up at a 45 degree angle so that the main is above the ridgeline and the working end dresses down. Depending on your setup you might need a knot.

The tent fits nicely in the bag with plenty of spare room.  The tent should be folded in quarters so that one roll will get it in the bag. The more precise the 1/4 fold the nicer it looks.  I recall an email I had with Yukon Outfitters when we were talking about their rainfly and packing it away. The challenge was that the fly did not fit unless it was folded and yet the advice was not to fold it so that the fly would not age and develop cracks in the coating. That probably applies here too but I'm not thinking about that.

Overall it met the basic criteria of availability, cost, pack volume. The few manufacturing defects were a surprise but nothing I cannot fix. I wonder if the one design flaw could have been fixed with a single grommet and trekking pole at a 45 degree angle.

UPDATE as a reminder there is a lifetime warranty on manufacturing defects.... even better.


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…