Installing Open Solaris "Indiana Preview" on my Mac (part 1)
By user12611852 on Nov 01, 2007
NOTE: No CD-ROM was harmed in this exercise. I shall waste no plastic before its time.
Warning: I am testing a Preview product on top of a beta product using virtulization on MacOS. You results may vary.
This is just what I could get on the blog the first day. More to come.... First I must prioritize my day job activities!
Wow! Project Indiana is available today in a developer preview. I had to have it to see if everything they told us at the recent OS Amb preview was true. My system:
- MacBook Pro 2.4 Ghz with 2 GB RAM
- VMware Fusion 1.1RC1 beta
What is Project Indiana?
It is intended to be a binary distribution of the OpenSolaris code provided by and supported by Sun. This developer preview is the first step to a released product expected in March 2008. It includes the latest technologies and will have a faster changing and shorter life cycle than Solaris 10. More detail is available at the Project Indiana FAQ.
Who should use project Indiana?
At this time it is intended for developers and testers only. When it becomes a supported product in 2008, we anticipate it will be used by a wide variety of customers inproduction who required the advanced features of OpenSolaris and can tolerate the shorter life cycle support model.
How did it go?
- Live CD format provide (yes that's CD not DVD)
- X86 version ONLY today (the liveCD uses the 32-bit kernel but will install both 32 and 64-bit capability)
- ZFS as the native root file system
- Network Automagic included
- No custom disk partitioning.
With the ISO on my Mac, I created a VM for it to live in with 1 GB of RAM and 10 GB of disk space. The ISO booted perfectly into "Live CD mode." NWAM automatically detected my network address. I wasted no time in clicking the Installer. After a few questions about time zone, root password and initial non-root user, the installation started and took about 22 minutes to complete. After installations was complete, I clicked the Reboot button and the system started up from the virtual HD. The installation experience was quite easy and fast.
At this time, VMware Fusion 1.1RC1 has a bug that causes the 64-bit kernel to "hang" for about 1-2 minutes during the early boot process. Changing the Grub menu to boot the 32-bit kernel is a workaround for this issues.
Once I logged into the new Gnome 2.20 interface, I attempted to install the Vmware tools. This is necessary for the proper screen displays and file sharing. Unfortunately, I received the error that it could not copy a file to /usr/dt/config/Xsession.d/9999.autostart-vmware.user.sh Manually creating the Xsession.d directory allowed the VMware tools to complete. Although the installation of tools complete, it caused a problem with login where my keyboard was mapped wrong. I could NOT log into Gnome because of this issue and didn't have time to workaround it.
What's different for the user?
- Default shell is bash
- Java Desktop System is not installed by default. This means that there is no "Launch" menu in the lower left. Menus are in the upper right. Panels are enabled at the top and bottom.
- /usr/gnu/bin is at the beginning of the user's path
- There is a minimal set of software loaded. The pkg command can be used to get additional components from the software repository.
- The grub menu is now in /zpl_slim/boot/grub/menu.lst rather than /boot/grub/menu.lst
The file browser lists a "Documents" in the Favorites sidebar, but clicking on it produces an error because it doesn't exist.
Dave Miner has published instructions on how to place Indiana in a USB drive.
Why should you care?