The standard disclaimer applies. The document is provided on an "as is" basis. The author provides no warranty whatsoever, either express or implied, regarding the work, including warranties with respect to its merchantability or fitness for any particular purpose. You can easily ruin your hard disk when trying to do something similar to what I am reporting here.
This is a kind of a field report about my (Bernhard Treutwein) experiences with installing a multiboot Solaris 9 on an Intel deskside PC (Fujitsu-Siemens Scenic, P-III 900 MHz, FSC motherboard D1219 with onboard intel 815 graphics and 256 MB main memory) using Grub as a boot manager.
This time I first deleted two partitions from within Solaris 9 fdisk, but it creates an out-of sequence partition table, so I deleted this awful partition table and recreated the layout from Linux fdisk (booting from a Knoppix CD, since the boot manager was overwritten by Solaris fdisk, yet another beware). I had made backups of the boot records and I was able to restore the main partition table from my MBR backup. After fiddling around several times with the partition table, I decided to go the save way and add another hard disk, dedicated entirely to Solaris. An old 8GB disk was around and I added it as primary slave. The Solaris 9 8/03 installer refused to use this disk, when the primary master was visible in the BIOS, so I set the primary master to none, but kept the slave active. Alas, Solaris 9 accepted to be installed on this disk. I went through the complete installation, Solaris was also able to see the primary master although it was disabled in the BIOS.
Sorrily, maybe temporal coincidence, maybe due to incorrect usage of the ISO9660 patch for GNU Grub, I ruined the 8GB disk, so I had to reinstall Solaris. I disabled the first IDE disk in the BIOS (Phoenix BIOS allows setting to auto, none, user defined, and ZIP, LS120 or similar) and then I started the installation from the DVD. When asked for rebooting, I reenabled the first IDE disk again, which already contained GNU Grub and chainloaded to the bootsector installed by Solaris on the second harddisk (see entry #3 in the example menu.lst below). And alas, Solaris booted up and continued with its installation.
Here is my current grub configuration file (menu.lst)
And alas, Solaris booted up and continued with its installation. fallback 0
title 1. German Layout
title 2. Knoppix from (hd0,5) <-> /dev/hda6
savedefault root (hd0,5)
savedefault kernel /boot/vmlinuz root=/dev/hda6 ro apm=power-off hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi nomce initrd=initrd.gz
title 3. Solaris 9 - 08/03 --- UFS (hd1,0) chainload to disk /dev/hdb
title 4. Restart from (hd0)
title 5. Reboot from floppy
title 6. Reboot
title 6. Solaris 9 - 12/02 --- UFS (hd0,0) <-> /dev/hda1 (chainload to saved mbr)
MicroSoft Windows DHCP/DNS server alows a client to update DNS with the DHCP client's hostname. To get this working with a Solaris client, I had to do the following (maybe some of it is not essentially necessary, but it worked for me only after having done all steps):
For setting the own hostname and getting DHCP working correctly, it was necessary to refer to the following tip and the script contrary to what is said on the tip page, I added my hostname in hostname.iprb0 prefixed by inet. In /etc/default/dhcpagent I uncommented/changed the line containing REQUEST_HOSTNAME=yes. I have no idea, why registering a hostname in DNS via DHCP is called request a host name, but ...
An ext2fs driver for Solaris 9 can be found at the bottom of
software page. It is (thanks Paul) ready compiled; after
unpacking the archive, simply say ./getext2fs (as root) and
then you are able to read-only mount an ext2fs partition. with
mount -r -F ext2fs "device" "mountpoint". My third primary
partition on the primary master disk is mounted by
mount -r -F ext2fs /dev/dsk/c0d0p3 /linux
Linux can read Solaris slices in Linux partitions. I found the Solaris slices by grepping dmesg for the string "solaris" yields a list of the Solaris slices and the corresponding partition numbers in Linux, i.e.
# dmesg | grep solariswhich can be read as the following correspondence table (given these partitions are on /dev/hda):
p2: <solaris: [s0] p5 [s1] p6 [s2] p7 [s6] p8 [s7] p9 >
slice partitionAnd with a mount -t ufs /dev/hda5 /mnt/sol/root the root file system of Solaris is available under the mount point /mnt/sol/root. Analogue mount for the other slices work also, if the slices aren't swap and hav a valid UFS filesystem on it.