ShareAfter installing Windows 7 on my MacBook Pro, I quickly discovered that I had shortchanged the Bootcamp partition when assigning disk space (only 32GB).
A quick search on the web revealed numerous methods for resizing, the most common procedure being to:
- Using Winclone on the Mac, create an image of the Bootcamp partition;
- Run the Bootcamp Assistant to delete the partition;
- Run Bootcamp Assistant again to create a new, larger partition; and finally
- Restore the Windows installation from the Winclone image.
Ahem! Easier said than done… After deleting the Bootcamp partition, I had a horrible sinking feeling. Bootcamp Assistant kept telling me that it could not create a new partition because some files could not be moved. Following suggestions in various forums, I ran Disk Repair, Repair Permissions, defrag’d with Drive Genius, etc. all to no avail. After a few attempts, the message displayed by Bootcamp Assistant had also changed to “Please reinstall your system“!!!
I spent an evening backing up my system with Carbon Copy Cloner, booted from the Snow Leopard DVD, reformatted my MacBook hard drive and then restored my Mac partition (5 hours).
Now, when I ran the Bootcamp Assistant, it told me, “Boot Camp Assistant cannot be used. You must update your system software before using this setup assistant.” Oh Geez. I ran Software Update, repaired permissions and disk repair again without success.
Then I happened across a forum posting that stated that Bootcamp Assistant would not work if journaling was turned off for the mac partition. Funny, The Snow Leopard DVD has formatted my hard disk with journaling off by default. Somehow, that seems very wrong.
It was a simple matter to open up disk utility and activate journaling for my primary drive. I didn’t even have to reboot. And I was (happily) able to recreate a larger (80GB) partition for my Windows 7 installation. Winclone restored the system without incident and I am up and running again, but only after having spent a good 6-8 hours in total watching progress bars and beachballs.
ShareWe chose Linux as the platform for Sakai. The main reason was cost — no licenses for the server OS and the availability of low cost server hardware. We opted for CentOS 5 as the flavour of Linux. It is basically Red Hat Enterprise and has proven to be robust in the past.
CentOS is easy to install. I began with a virtual machine running in VMWare Fusion on my iMac. This allowed me to walk through the install process as a dry run, test out tools and steps, and to roll back if anything broke.
I opted for a 64-bit build of CentOS, so that we could take advantage of large amounts of memory later on if needed.
After installing CentOS using the GUI, the next step was to prepare the system for installing Sakai from source.
To install Sakai 2.5.x from source, we need several things (with caveats):
- Java JDK/JRE 5.0 Update 18 (Java 6 will NOT work)
- Apache Tomcat 5.5.26 or greater (Tomcat 6 is NOT compatible with Sakai)
- Maven 2.0.6 or better (for building Sakai source code)
- MySQL 4.1 or 5.0.x
Out of the box, CentOS has both Java 1.4 and Java 6 installed. Java JDK/JRE 5.0 needs to be downloaded from Sun and installed (Note that Sun Microsystems is withdrawing Java 5.0 as of September 2009, so if you want it, download and archive a copy now).
Installing a new version of Java involved unpacking the distribution in a local directory (e.g. /opt or /usr/local) and the using the “alternatives –install” command to make the system aware of the version and to select it as the default Java version. Use “java -version” to confirm that the correct java version is selected.
Next: Installing Tomcat 5.5
Powered by ScribeFire.
ShareThe next few posts will chronicle the process of creating a fresh install of the Sakai portal/course management system and then importing content from an existing installation.
The organization that I went through this process for had a Sakai instance that had been installed by a vendor/consultant as a binary distribution. We relied on the vendor for troubleshooting, upgrades and tool/portlet installations. We decided a few months back to develop the expertise “in-house” to install, configure and upgrade Sakai so that we would no longer be reliant on a vendor.
We wanted to go through the entire process of installing Sakai from source in order to learn how to do it, and to allow us to add tools using source code later on.
Sakai is not that difficult to install on its own, but there are a number of issues that arose during the process that I felt it was important to document.
Stay tuned!
Powered by ScribeFire.
Published on
March 26, 2009 in
E-mail.
ShareJust finished getting the site back online after my hosting provider
suffered a service outage and catastrophic data loss. While the
experience was nerve-wracking and a pain in the behind, it is probably
the kickstart that I needed to tend to this little garden again.
Spring is in the air, so some photo walks are on the horizon, as well
as bike excursions.
Watch this space for some resources related to geocaching in the
coming week… This as part of my prep for a workshop I am doing in
mid-May.
