Cruisemaniac Dad, Husband, Geek, Cyclist!

And then we rode...

Day one - Tour of Karnataka .

What a day! I couldn’t be happier! 150 km covered in just over 7 hours of riding…

The usual knee pain, but in all an amazing ride.

Idli and vada did not help once again… And I had to resort to energy bars to push to lunch point at 119km.

The heat almost killed me post lunch.. Hassan should be renamed HAS-ONLY-SUN. Chennai would lose hands down in heat wave comparisons.

A few things to note and a few learnings from what went wrong:

  1. Your pace matters. Not your comrades… If you have a match, awesome, else, ride solo…
  2. Random speed changes don’t work… There’s a reason “Cadence” is the undertone for cycling.
  3. Water, Aqua, hydrate the fuck out of your body… No water is dangerous. You have energy you cannot spend and you start sweating which is step 1 to bonking.

One thing that I noticed was my body overheating and complaining - basically revolting to pedal… Head -> water -> dunk.

Thanks to Chethan Ram for the amazing act he’s put together in the name of TOK!

If someone who picked up a cycle after 16 years 2 months ago managed 150km in 7 hours, a huge chunk of credit goes to the team…

It does work if you have a good leader….

More pain, more updates, tomorrow…

I will however leave you with a thought:

To overcome pain, you need to learn to enjoy it…

That’s like saying you want front row seats to a showdown between your butt and your seat refreed by a sponge wearing Spandex.

Cycling and the Tour of Karnataka

I moved to Bangalore in July this year and the first thing I realised that there was no way I was prepared to share my paychecks with Uber. There was no way I was going to stay stuck in traffic for 2 hours in each direction either.

The only option left, that I’d put on the back burner was Cycling. So I went ahead, spoke to a few friends, met the inspiring Mr. Chethan Ram, and bought myself a Marin.

The first ride from the shop till home made me question myself - Why did I plop such a huge chunk of my savings on a piece of metal that doesnt have a fuel tank OR an engine? I’ve trekked, I’ve gone swimming… But nothing drained me like this blue piece of aluminium.

And then the morning rides started.. First it was an attempt to better the 10km with a 20… Then came the 20km rides every other day. And then 40km mark.

One bright sunny day, the commute to work happened… 20kms, peak bangalore traffic, 1 hour. Note this - ONE HOUR via Bannergatta road all the way into Indiranagar!

When some guys said that cycling is contagious, I thought they were kidding and it was for only the guys in the prime of their fitness, not for a middle-aged geek like me. I couldnt be further from the truth!

Fast forward to today, I’ve put in over a 1000kms on the bike AND have signed up for the longest bike ride I’ve yet had my signts on - 600kms from Bangalore to Udipi across 4 days - The Tour of Karnataka, starting Nov 16.

Cycling, I’ve come to learn, is an individual thing…

The breeze on your face, the sweat in pushing for that extra mile, the conscious self-checks to ensure you dont bonk, the muscles crying in agony, gritting your teeth to push and better your last run - its a goodie bag of everything.

The folks cycling with Cadence90 have been nothing sort of stellar, I’m in the tour more for the company, the dialogues, the culture, more so than the cycling and the distance itself..

Yes, there’s bound to be amazing food, great views, the mere challenge of climbing the western ghats and coming out the other side, those are just free add-ons…

Cycling is my new signature!

Follow me on strava here.

Git vulnerability announced! Upgrade your git client

Git just announced a new release (ver 2.2.1) of the git client that fixes a vulnerability affecting all git users on Windows and Mac OSX operating systems. Github says this:

The vulnerability concerns Git and Git-compatible clients that access Git repositories in a case-insensitive or case-normalizing filesystem. An attacker can craft a malicious Git tree that will cause Git to overwrite its own .git/config file when cloning or checking out a repository, leading to arbitrary command execution in the client machine. Git clients running on OS X (HFS+) or any version of Microsoft Windows (NTFS, FAT) are exploitable through this vulnerability. Linux clients are not affected if they run in a case-sensitive filesystem.

We strongly encourage all users of GitHub and GitHub Enterprise to update their Git clients as soon as possible, and to be particularly careful when cloning or accessing Git repositories hosted on unsafe or untrusted hosts.

If you’re using homebrew, the process is very very simple:

brew doctor

brew update

brew upgrade git

You can download the latest clients for windows and OSX from the links provided. They have been patched for the vulnerability already.

Git for Ages 4 and Up

Its a long video at a little over 1.5 hours but there is no better resource on the internet that can explain Git like how this video does!


Totally worth it.

Get Vagrant running with berkshelf on Mavericks

So, here I was trying to setup Vagrant on my Mac. Everything went fine till the vagrant up command and boom:

myfirstvagrantproject $ vagrant up
Bringing machine 'projectname' up with 'virtualbox' provider...
==> projectname: The cookbook path '/Users/cruisemaniac/.berkshelf/projectname/vagrant/berkshelf-20140909-37664-1gf5t34-projectname' doesn't exist. Ignoring...
Updating Vagrant's berkshelf: '/Users/cruisemaniac/.berkshelf/projectname/vagrant/berkshelf-20140909-37664-1gf5t34-projectname'
RuntimeError: Couldn't determine Berks version: #<Buff::ShellOut::Response:0x00000101040360 @exitstatus=1, @stdout="", @stderr="/Users/cruisemaniac/.rbenv/versions/2.1.2/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find 'berkshelf' (>= 0) among 56 total gem(s) (Gem::LoadError)\n\tfrom /Users/cruisemaniac/.rbenv/versions/2.1.2/lib/ruby/2.1.0/rubygems/dependency.rb:309:in `to_spec'\n\tfrom /Users/cruisemaniac/.rbenv/versions/2.1.2/lib/ruby/2.1.0/rubygems/core_ext/kernel_gem.rb:53:in `gem'\n\tfrom /Users/cruisemaniac/.rbenv/versions/2.1.2/bin/berks:22:in `<main>'\n">

I knew vagrant liked chef_solo and berkshelf to assist in the scripts that handle provisioning the VM. So I went ahead and installed the gems before starting out with the vagrant install.

What I could not understand was how berkshelf which was installed under my rbenv (via homebrew) was not found while the gem was being picked up right! « I know, shitty!

My local setup gave me this:

myfirstvagrantproject $ vagrant version
Installed Version: 1.6.5
Latest Version: 1.6.5
You're running an up-to-date version of Vagrant!

myfirstvagrantproject $ berks --version
3.1.5
myfirstvagrantproject $ which berks
/Users/cruisemaniac/.rbenv/shims/berks

All is well right? Well, No!

Apparently, the berkshelf gem used by vagrant requries chefdk, the chef development kit and wont work hanky panky without that.

Remove any berkshelf AND chef gems from your ruby installationbefore you start off with the chefdk installation.

Install chefdk into your /opt folder - again a requirement. Add this to the .bash_profile before your gems are loaded.

export PATH=/opt/chefdk/bin

Reload your .bash_profile and you must be good to go.

The other option is that you dont use berkshelf with chef OR you use puppet.

If you dont want to use berkshelf, open the Vagrantfile and set the following to false:

Vagrant.configure("2") do |config|
  config.berkshelf.enabled = false
  ...
  # other configuration code

You would also have to remove the Berkshelf file sitting in your vagrant directory to prevent Vagrant from complaining about an existing Berkshelf file that its not using!

Hope this helps.