This used to be a bigger issue but now thanks to the signed drivers there’s very little more to do than download the drivers in Windows and install them:
I did my time with rsruby, rinruby and Rserve-Ruby-client. In retrospect I should have trusted the Rserve-Ruby-client readme which details the problems with rsruby and rinruby.
- rsruby – dealbreaker is that this is not stable, there are a few other downsides including complex data conversions and compilation issues but enough said.
- rinruby – slow, but more importantly fails when assigning large data making it pretty much useless. See Bug #2 and Bug #13.
Rserver can be installed on Debian/Ubuntu with:
apt-get install r-cran-rserve
Be aware that there is a bug in the Ubuntu package that requires fixing for rserve to work:
Cleaning up some systems and looking for packages that are no longer maintained.
apt-show-versions | grep 'No available version in archive'
I was amazed at some of the old packages on the systems, like libraries related to Gnome 2. This catches things that other methods like deborphan won’t.
I had to do this recently for a project. The difficult piece was sorting through the opinions of what the best tools and procedures for handling this migration was. So I tried a few until I found one that worked so well, so quickly that I decided it was worth sharing. Firs tthings I used that didn't work well and/or quickly and/or intuitively:
- mysqldump with various options and various tweaks/scripts/editing of the dump file
What did work well was py-mysql2pgsql. Once installed it was easy to set the configuration file options and run it. It worked without problem and I would use it again for this task. I can't comment as to whether it will handle all cases, this project didn't contain anything too fancy, but I would recommend it as a place to start:
I think my Dell 2005FPW is showing its age: I’m starting to get some rolling when the monitor is first powered on. It’s had a good run but I think I need to buy something or at least be prepared to buy before it becomes more problematic. I’ve resisted buying a new monitor because 1) if it’s not broken don’t fix it and 2) their has been little offered on the monitor market to encourage me to buy. There has been tremendous stagnation in the display world with regard to resolutions. I also strongly favor non-TN displays. The Dell 2005FPW uses PVA but IPS seems to have largely won out as the better display technology. Here’s the specs of my current monitor:
- Dell 2005FPW – 20″ 1680×1050 PVA 16:10 (0.258 mm pitch)
What I have found is that in that size range there has been little improvement in resolution. I suppose this is understandable since 1080 is the number of lines considered to be HD and if you are watching HD content it is nice to do so without upsampling. So what I have found is the following size/resolution pairings:
I ordered the SanDisk Extreme USB 3.0 32GB. Half the price of the Lexar JumpDrive Triton and the best random write performance on a USB drive. Some research I did included:
- 64GB Lexar JumpDrive Triton vs 64GB SanDisk Extreme USB 3.0 Comparison | Computer Hardware Upgrades
- SanDisk Extreme 64GB USB 3.0 Flash Drive Review :: TweakTown
- Lexar JumpDrive Triton 32GB USB 3.0 Flash Drive Review :: TweakTown
- SanDisk 64GB Extreme USB 3.0 Flash Drive Review – SanDisk Extreme USB 3.0 Performance – Legit Reviews
- Sandisk Extreme USB 3.0 (32GB, 64GB) Review | Everything USB
- SanDisk Extreme 64GB USB 3.0 Flash Drive – Newegg.com
I’ve come across a number of posts giving instructions on how to get debugging to work with ruby 1.9.x and they all seem to involve downloading gems and installing them. Here is what I did on my Ubuntu 12.04 workstations that was very easy though not trivial to figure out.
sudo gem install linecache19 --pre sudo gem install ruby-debug-base19 --pre -- --with-ruby-include=/usr/include/ruby-1.9.1/ruby-1.9.3-p0/ sudo gem install ruby-debug-base19x --pre sudo gem install ruby-debug-ide --pre
First install build dependencies. This list may not be complete as some necessary libraries and tools may have already been installed on my test machines. This is what I used to get the packages to build successfully:
- apt-get install build-essential python-dev gettext bin86 bcc iasl uuid-dev libncurses5-dev pkg-config libglib2.0-dev libyajl-dev git gcc-multilib texinfo fakeroot
Then download, unpack, configure, and build:
- wget http://bits.xensource.com/oss-xen/release/4.2.1/xen-4.2.1.tar.gz
- tar -zxf xen-4.2.1.tar.gz
- cd xen-4.2.1
- make deb
Afterword you’ll be left with a shiny new package:
I ran into this problem where I was getting “uninitialized constant” errors when running rake tasks. These are tasks which had been working and I verified that the proper paths were set (eager_load_paths). When searching I saw information about config.threadsafe! being a problem so I disabled it and the problems vanished. However, I wanted to use config.threadsafe!, specifically for allow_concurrency. So, how to resolve this.
I did some research and found a lot of discrepancy among recommendations for the decimal precision when doing geocoding. Some say you only need 4 digits of precision and others suggest up to 15. In my own testing the best results seemed to be with 6-digits and SQL type of PRECISION(9,6) for latitude and longitude. This should provide a resolution of less than 12cm which should be sufficient for most purposes. The storage requirements should be 5 bytes in MySQL and 9 bytes in PostgreSQL.