dtinth/Journal.md

## Journal.md

      
    Raw
  

              Journal.md
            
          
    Installing Ruby 2.0.0 on Kindle

So I've just jailbroken my Kindle, and want to run Ruby on it.
This is what I have right now on my Kindle:

KUAL, the Kindle Unified Applications Launcher
KTERM with tmux

Make sure you've also enabled usbnetwork so that you can SSH to your kindle via USB.
For Building, I use Vagrant. See the Vagrantfile below.
After configuring your Vagrant box, update and install the cross-compiler:
sudo apt-get update && sudo apt-get install gcc-4.6-arm-linux-gnueabi
sudo apt-get install build-essential

Installing Ruby

Download and extract Ruby sources:
wget 'http://cache.ruby-lang.org/pub/ruby/2.0/ruby-2.0.0-p353.tar.gz'
tar xvj < ruby-2.0.0-p353.tar.gz

Compile and install normally first.
./configure && make && sudo make install

Compile for ARM linux. Thanks to these blog posts:

http://zenmachine.wordpress.com/cross-compiling-ruby-to-arm-processors-the-not-so-zen-way/
http://k0st.wordpress.com/2011/12/18/ruby-on-amazon-kindle/

So, create a shell script: ruby_compile.sh
export CC=/usr/bin/arm-linux-gnueabi-gcc-4.6
export LD=/usr/bin/arm-linux-gnueabi-ld
export AR=/usr/bin/arm-linux-gnueabi-ar
export RANLIB=/usr/bin/arm-linux-gnueabi-ranlib

export ac_cv_func_getpgrp_void=yes
export ac_cv_func_setpgrp_void=yes

exec ./configure --target=arm-linux --host=arm-linux --prefix=/mnt/us/ruby-2.0.0-p353 --with-static-linked-ext --disable-shared --disable-install-doc
And then,
bash ruby_compile.sh && make && sudo make install

This will install into /mnt/us/ruby-2.0.0-p353.
Now we can copy it to Kindle.
cd /mnt/us
tar cvz ruby-2.0.0-p353/ > /vagrant/ruby-2.0.0-p353-kindle.tar.gz

Then copy the tarball and extract it on your Kindle.
Finally, put this on your profile:
export PATH=/mnt/us/ruby-2.0.0-p353/bin:$PATH


## Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  # All Vagrant configuration is done here. The most common configuration
  # options are documented and commented below. For a complete reference,
  # please see the online documentation at vagrantup.com.

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "precise32"

  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.
  # config.vm.box_url = "http://domain.com/path/to/above.box"

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # config.vm.network :forwarded_port, guest: 80, host: 8080

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network :private_network, ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network :public_network

  # If true, then any SSH connections made will enable agent forwarding.
  # Default value: false
  # config.ssh.forward_agent = true

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider :virtualbox do |vb|
  #   # Don't boot with headless mode
  #   vb.gui = true
  #
  #   # Use VBoxManage to customize the VM. For example to change memory:
  #   vb.customize ["modifyvm", :id, "--memory", "1024"]
  # end
  #
  # View the documentation for the provider you're using for more
  # information on available options.

  # Enable provisioning with Puppet stand alone.  Puppet manifests
  # are contained in a directory path relative to this Vagrantfile.
  # You will need to create the manifests directory and a manifest in
  # the file base.pp in the manifests_path directory.
  #
  # An example Puppet manifest to provision the message of the day:
  #
  # # group { "puppet":
  # #   ensure => "present",
  # # }
  # #
  # # File { owner => 0, group => 0, mode => 0644 }
  # #
  # # file { '/etc/motd':
  # #   content => "Welcome to your Vagrant-built virtual machine!
  # #               Managed by Puppet.\n"
  # # }
  #
  # config.vm.provision :puppet do |puppet|
  #   puppet.manifests_path = "manifests"
  #   puppet.manifest_file  = "site.pp"
  # end

  # Enable provisioning with chef solo, specifying a cookbooks path, roles
  # path, and data_bags path (all relative to this Vagrantfile), and adding
  # some recipes and/or roles.
  #
  # config.vm.provision :chef_solo do |chef|
  #   chef.cookbooks_path = "../my-recipes/cookbooks"
  #   chef.roles_path = "../my-recipes/roles"
  #   chef.data_bags_path = "../my-recipes/data_bags"
  #   chef.add_recipe "mysql"
  #   chef.add_role "web"
  #
  #   # You may also specify custom JSON attributes:
  #   chef.json = { :mysql_password => "foo" }
  # end

  # Enable provisioning with chef server, specifying the chef server URL,
  # and the path to the validation key (relative to this Vagrantfile).
  #
  # The Opscode Platform uses HTTPS. Substitute your organization for
  # ORGNAME in the URL and validation key.
  #
  # If you have your own Chef Server, use the appropriate URL, which may be
  # HTTP instead of HTTPS depending on your configuration. Also change the
  # validation key to validation.pem.
  #
  # config.vm.provision :chef_client do |chef|
  #   chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
  #   chef.validation_key_path = "ORGNAME-validator.pem"
  # end
  #
  # If you're using the Opscode platform, your validator client is
  # ORGNAME-validator, replacing ORGNAME with your organization name.
  #
  # If you have your own Chef Server, the default validation client name is
  # chef-validator, unless you changed the configuration.
  #
  #   chef.validation_client_name = "ORGNAME-validator"
end
	# -- mode: ruby --
	# vi: set ft=ruby :

	# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
	VAGRANTFILE_API_VERSION = "2"

	Vagrant.configure(VAGRANTFILE_API_VERSION) do \|config\|
	# All Vagrant configuration is done here. The most common configuration
	# options are documented and commented below. For a complete reference,
	# please see the online documentation at vagrantup.com.

	# Every Vagrant virtual environment requires a box to build off of.
	config.vm.box = "precise32"

	# The url from where the 'config.vm.box' box will be fetched if it
	# doesn't already exist on the user's system.
	# config.vm.box_url = "http://domain.com/path/to/above.box"

	# Create a forwarded port mapping which allows access to a specific port
	# within the machine from a port on the host machine. In the example below,
	# accessing "localhost:8080" will access port 80 on the guest machine.
	# config.vm.network :forwarded_port, guest: 80, host: 8080

	# Create a private network, which allows host-only access to the machine
	# using a specific IP.
	# config.vm.network :private_network, ip: "192.168.33.10"

	# Create a public network, which generally matched to bridged network.
	# Bridged networks make the machine appear as another physical device on
	# your network.
	# config.vm.network :public_network

	# If true, then any SSH connections made will enable agent forwarding.
	# Default value: false
	# config.ssh.forward_agent = true

	# Share an additional folder to the guest VM. The first argument is
	# the path on the host to the actual folder. The second argument is
	# the path on the guest to mount the folder. And the optional third
	# argument is a set of non-required options.
	# config.vm.synced_folder "../data", "/vagrant_data"

	# Provider-specific configuration so you can fine-tune various
	# backing providers for Vagrant. These expose provider-specific options.
	# Example for VirtualBox:
	#
	# config.vm.provider :virtualbox do \|vb\|
	# # Don't boot with headless mode
	# vb.gui = true
	#
	# # Use VBoxManage to customize the VM. For example to change memory:
	# vb.customize ["modifyvm", :id, "--memory", "1024"]
	# end
	#
	# View the documentation for the provider you're using for more
	# information on available options.

	# Enable provisioning with Puppet stand alone. Puppet manifests
	# are contained in a directory path relative to this Vagrantfile.
	# You will need to create the manifests directory and a manifest in
	# the file base.pp in the manifests_path directory.
	#
	# An example Puppet manifest to provision the message of the day:
	#
	# # group { "puppet":
	# # ensure => "present",
	# # }
	# #
	# # File { owner => 0, group => 0, mode => 0644 }
	# #
	# # file { '/etc/motd':
	# # content => "Welcome to your Vagrant-built virtual machine!
	# # Managed by Puppet.\n"
	# # }
	#
	# config.vm.provision :puppet do \|puppet\|
	# puppet.manifests_path = "manifests"
	# puppet.manifest_file = "site.pp"
	# end

	# Enable provisioning with chef solo, specifying a cookbooks path, roles
	# path, and data_bags path (all relative to this Vagrantfile), and adding
	# some recipes and/or roles.
	#
	# config.vm.provision :chef_solo do \|chef\|
	# chef.cookbooks_path = "../my-recipes/cookbooks"
	# chef.roles_path = "../my-recipes/roles"
	# chef.data_bags_path = "../my-recipes/data_bags"
	# chef.add_recipe "mysql"
	# chef.add_role "web"
	#
	# # You may also specify custom JSON attributes:
	# chef.json = { :mysql_password => "foo" }
	# end

	# Enable provisioning with chef server, specifying the chef server URL,
	# and the path to the validation key (relative to this Vagrantfile).
	#
	# The Opscode Platform uses HTTPS. Substitute your organization for
	# ORGNAME in the URL and validation key.
	#
	# If you have your own Chef Server, use the appropriate URL, which may be
	# HTTP instead of HTTPS depending on your configuration. Also change the
	# validation key to validation.pem.
	#
	# config.vm.provision :chef_client do \|chef\|
	# chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
	# chef.validation_key_path = "ORGNAME-validator.pem"
	# end
	#
	# If you're using the Opscode platform, your validator client is
	# ORGNAME-validator, replacing ORGNAME with your organization name.
	#
	# If you have your own Chef Server, the default validation client name is
	# chef-validator, unless you changed the configuration.
	#
	# chef.validation_client_name = "ORGNAME-validator"
	end