uninitialized constant Gem::GemRunner (NameError) - Ubuntu
I mentioned that I now use Ubuntu 7.10 on my Dell. After installing Ruby and RubyGems using apt-get, I got this nasty error AFTER doing ’sudo gem update –system’.
It appears that similar problems have occurred with Mac OS X as well. For one thing, you can try adding following to the gem file:
require ‘rubygems/gem_runner’
However, it was irritating me that along with this problem, I had to install irb separately and ruby sitting in /usr/bin directory.
My solution? Just install using the source. It always works for me without any problem and any subsequent stuff I add works without any issues. What I also like is that some of my scripts explicitly points to the location of ruby. Although I can correct this using env, why bother?
RailsConf 2007 Video
It’s not everything, but all the keynotes are here. Best of all, it works!!!
Good Bye Windows
As of today, I’m free of Microsoft Windows. I decided to wipe the Windows off of my Dell D620 and gave it a fresh installation of Ubuntu 7.10, Desktop Version. What I love about not running the Linux on VM is that I now can play with xdm/gdm + Compiz/Beryl. Needless to say, I’m just lovin’ wobbly windows. Other than that, it’s everything I want and need. The hardware, including the wireless, works flawlessly but I was expecting that.
I can finally see why so many people are raving about Ubuntu being the distro to compete with Windows in desktop/workstation space. I even got to play Quicktime video using mplayer. However, I have a working knowledge of Linux/Unix. I would like to find out how someone else would feel.
Now, as for installing Ruby, I just didn’t have much luck with installing from the package manager. When I updated the gem, it broke and I ended up reinstalling the entire stack from the source. I used the package manager for installing some libraries, but found that if you want to run the latest version of the stack and want the complete control over the upgrade, then this is the only way to go. I’ll post my findings in few days.
My main machines are and will always be Macs, but I’m really delighted that I can now use Linux on my desktop and wave my middle finger at Microsoft at the same time.
Advanced Rails
The one thing I really love about being a subscriber of Oreilly’s Safari is that I get to read the latest books without going broke. Naturally, I was delighted when Advance Rails by Brad Ediger.
As the title suggests, it covers the “advanced” topics. I never really understood what made a topic advanced, but as far as I’m concerned, it just means that topics haven’t been covered in other books. By my definition, this book isn’t so advanced. If you’re a regular subscriber to the forums and the mailing lists, then you’d be aware of all the topics covered by this book.
Rather than being a tutorial that spoon feeds, this book is more like a guide that gives high-level overview and directs to where you need to look. I almost forgot that I was reading a book, not a blog. It’s also not shy about assuming the fact that the readers already know Rails.
I’m not sure if I’d recommend this book if you had to pay money for it. I got this feeling that the book was rushed, but then again, that’s usually the case for computer books these days.
Sun + MySQL
I’m extremely stunned that Sun Microsystems acquired MySQL. I’m not sure what’s going to happen to MySQL, but looking at Sun’s track record with Unix, my feelings are somewhat mixed. I’m sure that Sun will do a good job of extending the features, but at the same time, afraid that they may make it too big as they did with Java. Oh, another thing, if they start rolling out with other stupid names like the “beans” or “swing”, I’ll just abandon their stuff.
By the way, I’ve begun working on Postgresql and turns out it’s really good. I plan on using Postgresql rather than MySQL. I know there are issues associated with using Rails, but I’m sure there are solutions as well. I’ll post them here as my personal note.
Rails App Not Starting After Reboot?
It’s very rare that my server goes down without my knowledge. However, there are times when it will be rebooted by my provider. I have a script that automatically starts the Rails apps. The problem is that when my server rebooted without my knowledge, I was getting messages from people that my apps are not “available”.
After viewing the script, I was somewhat shocked and embarrassed that I forgot to delete “mongrel.pid” before starting the server. This file is located in “log” directory of each individual Rails app and must not be present when Mongrel starts. If it exists, then Mongrel won’t start because it thinks that another instance of app is running.
So, there you have it, always remember to brush your teeth and delete your pid files.
Another Rubyhead
I’m very happy to announce that Bernie Kravitz, my dear friend and yet another Java & C# refugee, will be joining this blog as a contributor from time to time. He actually knows how to write well, so you’ll find his posts entertaining as well as informative.