You are currently viewing all posts in the general category.

I spent the equinox in the Glacier Peak Wilderness.

A few days. Me and a pack and some mountains.

Goodbye summer, hello fall.

Ruck

Currently reading: Journey to the Centre of the Earth by Richard and Nicholas Crane.

If you’re at all interested in bikes, lightweight backpacking, or a combination thereof, you must read this book.

In 1986, Dick and Nick rode lightweight, steel race bikes from the Bay of Bengal across Bangladesh, up and over the Himalaya, across the Tibetan Plateau, and through the Gobi desert to the point of the earth furthest from the sea. They were sawing their toothbrushes in half and cutting extraneous buckles off of their panniers before “bikepacking” (or “ultralight backpacking”) was a thing. The appendix includes a complete gear list and relevant discussion.

A snowy night in Tibet

The book is currently out of print, but used copies can be found. A PDF version is available here.

I've long been an 8-speed man on my bikes.

More gears seem unnecessary, but the market has other ideas. I wanted to upgrade my brifters. There were practically no options, so last week I made the jump to 9-speed. Now I’m running an 11-32 9-speed cassette and a 30/42/52 triple chainring.

9 Speed

Tarsnapper: Managing Tarsnap Backups

Tarsnap bills itself as “online backups for the truly paranoid”. I began using the service last January. It fast became my preferred way to backup to the cloud. It stores data on Amazon S3 and costs $0.30 per GB per month for storage and $0.30 per GB for bandwidth. Those prices are higher than just using Amazon S3 directly, but Tarsnap implements some impressive data de-duplication and compression that results in the service costing very little. For example, I currently have 67 different archives stored in Tarsnap from my laptop. They total 46GB in size. De-duplicated that comes out to 1.9GB. After compression, I only pay to store 1.4GB. Peanuts.

Of course, the primary requirement for any online backup service is encryption. Tarsnap delivers. And, most importantly, the Tarsnap client is open-source, so the claims of encryption can actually be verified by the user. The majority of for-profit, online backup services out there fail on this critical point.

So Tarsnap is amazing and you should use it. The client follows the Unix philosophy: “do one thing and do it well”. It’s basically like tar. It can create archives, read the contents of an archive, extract archives, and delete archives. For someone coming from an application like Duplicity, the disadvantage to the Tarsnap client is that it doesn’t include any way to automatically manage backups. You can’t tell Tarsnap how many copies of a backup you wish to keep, or how long backups should be allowed to age before deletion.

Thanks to the de-duplication and compression, there’s not a great economic incentive to not keep old backups around. It likely won’t cost you that much extra. But I like to keep things clean and minimal. If I haven’t used an online backup in 4 weeks, I generally consider it stale and have no further use for it.

To manage my Tarsnap backups, I wrote a Python script called Tarsnapper. The primary intent was to create a script that would automatically delete old archives. It does this by accepting a maximum age from the user. Whenever Tarsnapper runs, it gets a list of all Tarsnap archives. The timestamp is parsed out from the list and any archive that has a timestamp greater than the maximum allowed age is deleted. This is seamless, and means I never need to manually intervene to clean my archives.

Tarsnapper also provides some help for creating Tarsnap archives. It allows the user to define any number of named archives and the directories that those archives should contain. On my laptop I have four different directories that I backup with Tarsnap, three of them in one archive and the last in another archive. Tarsnapper knows about this, so whenever I want to backup to Tarsnap I just call a single command.

Tarsnapper also can automatically add a suffix to the end of each archive name. This makes it easier to know which archive is which when you are looking at a list. By default, the suffix is the current date and time.

Configuring Tarsnapper can be done either directly by changing the variables at the top of the script, or by creating a configuration file named tarsnapper.conf in your home directory. The config file on my laptop looks like this:

1
2
3
4
5
6
[Settings]
tarsnap: /usr/bin/tarsnap

[Archives]
nous-cloud: /home/pigmonkey/work /home/pigmonkey/documents /home/pigmonkey/vault/
nous-config: /home/pigmonkey/.config

There is also support for command-line arguments to specify the location of the configuration file to use, to delete old archives and exit without creating new archives, and to execute only a single named-archive rather than all of those that you may have defined.

$ tarsnapper.py --help
usage: tarsnapper.py [-h] [-c CONFIG] [-a ARCHIVE] [-r]

A Python script to manage Tarsnap archives.

optional arguments:
  -h, --help            show this help message and exit
  -c CONFIG, --config CONFIG
                        Specify the configuration file to use.
  -a ARCHIVE, --archive ARCHIVE
                        Specify a named archive to execute.
  -r, --remove          Remove archives old archives and exit.

It makes using a great service very simple. My backups can all be executed simply by a single call to Tarsnapper. Stale archives are deleted, saving me precious picodollars. I use this system on my laptop, as well as multiple servers. If you’re interested in it, Tarsnapper can be downloaded directly from GitHub. You can clone my entire backups repository if you’re also interested in the other scripts I’ve written to manage different aspects of backing up data.

It's better when you break things completely.

When things are only partly broken your inbox gets flooded with error messages…

Mark Two

Hi there. It’s been a while.

I took a year off from blogging. That wasn’t intentional. I just didn’t have anything to say for a while. Then I did have something to say, but I was tired of how the website looked. If the design doesn’t excite me I tend not to want to blog. (Call me vain, but I want my words to look good.) And redesigning the website – well, that requires an entirely different set of motivations to tackle. It took me some time to get that motivation, and then before I knew it we were here: 10 days short of a year.

During the development process I referred to this design as “mark two”, as it was the second idea I tried out.

The website still runs on Django. The blog is still powered by Vellum, my personal blog application. I’ve been hacking in it for over a year now (even when this website was inactive) and it is much improved since the last time I mentioned it. In the past six months I’ve seen the light of CSS preprocessors. All of the styling for this design is written in SASS and uses the excellent Compass framework. The responsive layout is built with Susy.

If you’re interested in these technical details, you will also be interested to know that the entire website is now open-source. You can find it on GitHub. Fork it, hack it, or borrow some of my CSS for your website.

The other big news is that I have begun to categorize blog posts. Yeah, it’s 2012 and I’m a little late to the party on that one. You may recall that I only began to tag posts in 2008. As it stands right now, all posts are just placed in the great big ameba of a category called “General”. Eventually, they will all have more meaningful categories – I hope. But it will be a while.

Things ought to be more active around here for the foreseeable future.

Sanyo Eneloop Rechargeable Batteries

I go through batteries at a fairly high rate. Electronic devices for the wilderness, such as my headlamp and GPS, see regular use. At home, things like my wireless mouse need power. The biggest drain are my lights – particular in the winter, when they are used to light my regular commute.

This last spring I decided to invest in a set of rechargeable batteries. Although some of my devices run on CR123 batteries, most use AA or AAAs. To start with, I was concerned only with being able to recharge the AA and AAA batteries. Years ago I had a set of rechargeable batteries, but I think the technology was not very developed back then. They seemed to drain quickly and not hold many charges. Today, the market is different. Some brief research showed that there were many options out there, with positive reviews for most of them.

What most reviews seemed to suggest was that the majority of the offerings were all of equal quality, with most differences unlikely to be noticed outside of a laboratory. The most popular, though, seemed to be the Sanyo Eneloop and Maha Powerex batteries. I found some claims that, between the two, the Eneloops held a charge longer while on the shelf.

I decided to try the Eneloop batteries, and purchased a package that included a charger, 8 AAs and 4 AAAs. The charger can charge up to four batteries at once, either AAA or AA, but it must be done in pairs. It cannot charge one battery at a time, or three. This has turned out to be an occasional inconvenience. I have some devices that use three batteries, and some that need just one. To charge the batteries for those devices I always have to give the charger an extra battery.

Sanyo Eneloop Charger

The charger takes around five hours to bring a dead battery up to a full charge. I have read that the Maha Powerex MH-C9000 charger can charge the batteries in a shorter period of time. It also gives the user more control over the charge, which has the potential of increasing the life of the batteries.

The batteries themselves I have been very happy with. I don’t have the knowledge to provide any objective information on their chemistry or electronics. Suffice it to say that they work. They seem to last longer in the same devices than their non-rechargeable counterparts did. I have not noticed any degradation in those batteries that I have recharged. That is not surprising. Sanyo claims the Eneloop batteries can be recharged 1,500 times – a number I have not come anywhere near to approaching.

Electronics Powered by Eneloops

Since the initial purchase, I have bought two more packs of AA and AAA Eneloops. All of my electronics now run on rechargeable batteries, save for those few that require CR123 batteries. The batteries themselves are an expensive investment, but they have payed off. Now that I have a good number of both AA and AAA sizes, and am happy with the Eneloop brand, I would like to purchase a more specialized charger, such as the aforementioned C9000.

If you use any non-rechargeable AA or AAA batteries in your electronics, I recommend giving Eneloops a try. The financial savings alone is enough of a benefit to justify their use.

Learning Morse Code

Although it’s no longer required for the amateur radio Technician license, I have decided to learn Morse code. Despite it’s age, Morse remains one of the most effective ways to transmit information over long distances using minimal infrastructure and power.

Learning Morse Code

To begin, I have printed and laminated the code chart from learnmorsecode.com. This makes encoded and decoding Morse a simple (although not fast) task. I’ve also put a variety of audio files consisting of slow Morse transmission on my media player. With a notebook and pen, I can practice decoding the messages wherever I am.

I’m aiming for 10 minutes of practice per day.